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

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

Currently in the new processor if a comment box is popped out to another window and the work item is closed those comments stay open.  There is a fear that the processor will open another item and think those comments from the previous item are the item they are working on currently. So the ask is that when comments are popped out for a Work item when that work item is closed out that the comment pop out window also be closed for that item. ... View more

Enhancement request for the Delivery form to be configurable by Chorus BPM Admin as a resource: 1. Source Type - value should allow for admin to predetermine the source type, not user input 2. Phonebook - ability to save public or private entry should be controlled access. User can be directed to have to enter values each and every time manually in order to mitigate from incorrect selection from their private phonebook ... View more

SS&C stated this is the Chorus behavior and not a bug. But to user side, this is not logical.     ... 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

Adding 'Show all items' so that user will not need to click multiple times for using show more items (now this button only refresh the next 25 items)   ... View more

The comment section in the comment bubble window is not able to be expanded when entering your comments, resulting in only being able to read a sliver of the notes you are typing. ... View more

One of our clients would like to move the comments from presentation flow's automation service from User comments to System comment. This change is necessary because the automation service system comments are crucial for our users to understand the status of the work. Moving these comments to system comments makes more sense because they are triggered by the system rather than an operator.         ... 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

Provide Fax Out full API set ... View more

The latest version of Chorus disables the copy feature for user IDs on the work assignment screen. This feature worked fine in Chorus 21.1. The ability to copy assigned user information is used by existing clients in their workflows to facilitate their processes. The client wishes for the user assignment copy feature to be enabled again, as it would be helpful for their operations. ... View more

Enhance manual comments to allow comments to be flagged as either private/internal or public/external/global. All comments would be visible to users in Processor Workspace, but the RESTful API would be enhanced so that only comments explicitly marked as "public" would be exported via API for use in (e.g.) an external case-tracking Portal. Analogue would be Service Now's use of "work comments" (only visible internally in Service Now) and "additional Information" comments, visible to both SNOW users and clients.  ... View more

It would be helpful to have the Preview User Comments card pop on the worktype you are adding comments to.  Currently a case with several worktypes will pop the Preview User Comments card at the top of the case causing a user to scroll to the top.  Time consuming if you have a large case and the card did not pop and need to scroll down to click the bubble again.   ... View more

The add attachment pop up window disappears after one attachment is added in Processor Workspace. This only happens when the add attachment is used within a process.  We have had users ask for it to function like Legacy Processor where the window stays there until you are done attaching one or multiple items to the object.   ... View more

The idea is to add an "edit" and "delete" option to the new "reply" functionality for a comment.  The functionality would only be allowed for the user who submitted the comment or a manager to be able to edit or delete that specific comment if placed in error.  This would of course keep the history of the change for audit purposes but could help prevent an error if a comment was added in error or worded incorrectly.  I do enjoy the new reply feature so this would be in addition to this added functionality.   ... View more

Currently we have a custom code applicated that was created with AWD Toolkit to allow a bulk number of work items to be moved to a different business area/work type/status/queue combination upon request. As part of this custom code application, we also add a comment stating who requested the items be moved and the corresponding ticket number so that each work item has a history line stating why it was systematically moved. This is information that is verified during our audits. While AWD Portal has the Process Monitor to bulk move items, it does not have the ability to add comments. Our request is to add an optional comment field so that when items are moved comments can be applied. ... View more

In version 24.1, the View History - Service History window displays seemingly unhelpful information that requires the user to size column and scroll left and right to view columns that are important for troubleshooting.  More specifically, the columns "Job ID", "Process Step ID", and "Sub Job ID" seem to just cause clutter in this view.  If these are important data points they could be added to the Excel Export version... which interestingly they are not included currently. A great solution would to make the columns configurable - add/subtract columns and modify the order of the columns to make researching history much easier. ... View more

The new version of Chorus disables the spinning indicator when Chorus is busy which is available on Chorus 21.1. The absence of this busy indicator may lead to duplicate actions from users, as they may not realize that Chorus is still working on the previous task and has not yet completed it. This behavior can impact daily operations by introducing duplicate actions. For example, without the spinning indicator, users may be unaware if their previous click action created a work item, prompting them to click again and inadvertently create duplicate work in Chorus. ... View more