Showing ideas with label Chorus: HiTL.
Show all ideas
Recently Chorus was enhanced to add a user preference so that the Comments Card shows the comments based on the Show drop down option within the card. This user preference does not apply to the comments preview window that appears when holding the mouse over the comment bubble on a work item. The preview window only shows user comments. This becomes confusing for end users because they believe that they had selected to view all comments and then do not understand why the preview is missing some, or in some cases many, of the comments.
... View more
The search drop down list within Processor Workspace is forced to be in alphabetical order. We are given the ability to specify the order that lookups are in within the LOOKUP resource parameters list, so the drop down should obey this order. Having frequently used searches at the top of the list is more streamlined and user friendly for the end users. This used to be functionality that existed but was taken away.
... View more
Users have ability to suspend BUT they can use the suspend feature to take work out of quality by Suspending and then having an activate status that wakes up in a different queue. Essentially bypassing quality. We would like the suspension feature to have additional access to restrict the activation status option or ability to add an activation status as addtional resource. Thank you
... View more
When inputting a comment, the text area is too small and only shows two lines. You do need to scroll to see the full comment if its longer than two lines. We have users that paste input or paste large comments and it would be helpful to see more of the comment when doing so.
... View more
Currently, User Comments show by default in Processor Workspace. We would like the ability for our users to be able to pick a different default in Preferences. Furthermore, we would like the ability to define a different global default in Chorus Administration.
... View more
When a user creates an item using the Create Work card, the work item doesn't show the current step of the item. It only shows the first step for that process. The user has to open the item or search for the item separately to see the item move through the process.
... View more
Printing AWD history from view station generated a .pdf file which could be presented to auditors for review. History exported from Portal is presented as a .csv file and is editable prior to printing to .pdf. Clients feel this is a shortcoming, a potential audit finding.
... View more
Status:
Planned-Later
Submitted on
03-01-24
06:28 PM
Submitted by
mclanderson
on
03-01-24
06:28 PM
Printed history from viewstation rendered in .pdf referenced all/any indexed values (ba/worktype/status/, fund/account, SSN, Misc ID) at the top of each page along with the CRDA ensuring the printed history could be verified back to the selected fund/account (primarily used for internal/external audit review of processed work) and the date time the history was printed. In Portal, only the business area and worktype are presented on the history card along with a truncated CRDA so it is not possible to tie back the history to the selected item and no indexed values are captured on the current .csv export.
... View more
Would like Copy and Paste from the comment section to work like Classic does now. If there are line breaks or carriage returns in a comment it will copy the same way into Word, OneNote, or an Outlook email. Currently in Processor Workspace it is all one continuous line unless you paste into a Notepad or a Sticky Note. This adds extra steps to get it to format correctly.
... View more
My client (on 23.x) having the following suggestion on the new Process workspace. In the Work object, currently when user view the History and select to Export, he need to export the History; Process; Services tab one by one. Client wish to have the function to export all of them (maybe in separate tabs in the exported csv) in one go.
... View more
The ability to add and view a lengthy set of comments increases the time spent by having to scroll up and down due to the size of the comments box. Enlarging the box and scroll bar on the right side of the window will help reduce time spent on reviewing comments being added.
... View more
In the Legacy Processor the user would be able to choose in the drop down what comments to show: All, User Comments, Batch User Comments, System Comments. Typically our users select "All" and then that will default all comments for all Work Items to be "All" with the new processor the comments always default to "User Comments" even if the user changes them. I submitted a Customer Care ticket for this and the response was that this is working as expected with the new processor. Requesting an enhancement to either: 1. Add to preferences the Comments and how the user would like the default setup as. 2. Back to the Legacy Processor way where they changed it one time and it would stick for all future items opened unless changed. 3. Allow a system default set at the company level.
... View more
Users would like to create a comment(s) and save it to my documents so it's readily available to add to the work object history as needed. The ability to do this would save time as the user would not have to retype the same comment over and over.
... View more
Concern is that a reply can be made to comments at different dates/times, so a reply can be missed by business users for day to day processing. Options are to either: 1. create a resource so that we can give specific users access to be able to REPLY OR 2. add in the Reply Filter in Comments
... View more
In Chorus when a user views the work items history the KE/ST steps in the workflow do not appear. This causes confusion for the user if they anticipated a step being done. It is also an audit concern because it is not a true history of everything done to the work item. Moreover, the KE/ST should not only appear in the history, but it should print as well. We print out the history for the purposes of audits to validate processing procedures were met.
... View more
Many business procedures have standard comments that are copy pasted onto an item, and then modified as needed. To streamline the process, as a user, I want an option for AWD to populate standard comments for a given Business Area/Work Type combination so that I don’t have to copy paste them from elsewhere.
... View more
In Doc split, there is an option to assign a newly created work item to a user. However, if the new work item is associated with a process that runs an automated service as the first step, the new item will not assign to the selected user because the SYSTEM id gets the assignment in order to run the service. Somehow Doc Split needs to handle this, as right now it gives the false impression this will work. The purpose for running the service is to create a relationship between the newly created item and the case object where doc split was activated, because there is no option to attach the newly created work item to that case. If that option were available, then the need to run the service (in this instance) would not be needed, and then the assign feature would work.
... View more
In adding the New Processor several miss the column layout of the Legacy Processor in the Work List and Search functionalities. Currently under preferences there is a Theme space and currently there is Default and Compact, the request is to add an additional one that would mirror similar to the column format with Headers like Legacy Processor where individuals can easily compare LOB's within several work items.
... View more
My client (on 23.x) would like the Worklist to be enhanced so that there can have the second level of sorting. E.g. first sorting on Worktype and second sorting on a LOB field.
... View more
