As a process designer I would like to be able to compare two versions of a model and for the differences to be highlighted in Design Studio.   This will help me identify and assess the impact of changes. The bpmn.io framework used by Design Studio supports this capability, but we currently need to export models to use it. ... View more

Regarding EQM inbound email contents, our client found that when the email body has over 10k chars, those content length after 10k will be truncated. This is confirmed with development team on the limitation. Our client needs a search of Ref id in the email body text, so that the workflow logic will link the email in source to the work with same Ref id. In the case when email go back and forth, it will become a long email thread. This long email body text has been truncated and unable to return the Ref id for further processing. This limitation is impacting the business operation, client requests an enhancement on the EQM capture component and allow configuration.   ... View more

Work items which are stuck in infinite loops impact Chorus BPM system performance, and in some cases system stability.   This issue impacts both hosted and self-hosted clients. When we see high CPU utilisation on the application and database servers, we query the WA2 BI event table to find work items which are stuck in a loop.   This reactive step allows us to identify the work items which are impacting performance but doesn't address the root cause. We could like Chorus BPM design studio to identify potential infinite loops as part of process validation.   The beta process test automation framework was able to identify loops.  Maybe this code could be used as the basis of a solution? ... View more

Enhancement Request: As a Chorus processing user, when I add an attachment (Word or Excel) these documents have a document name as shown in the diagram below. Once it is created in Chorus each attachment is given a 12‑digit Collection ID and the original filename is stored in the FLNM lob field as meta data as shown in the diagram below. When I subsequently download or view the attachment, it uses the Collection ID as the filename in the banner.   The use of the Collection ID in the banner is confusing as I am not able to see at a glance what the document is, particularly as I will have multiple documents open.  I also have to share these documents with others and the name of the document is incorrect. Therefore when I save the document I have to rename it back to the original document name which introduces potential errors as I must follow a specific naming convention. Desired outcome:   When an attachment is opened in its native application, the application banner will display the meta data held in the LOB field (FLNM) and the file to be downloaded with the document name (FLNM).  Additional information There was an enhancement made to ROS 2.5 that has the functionality being requested. The source type MASTER has been set up as Revisable: The user has created the MASTER attachment (revisable): The original filename (FLNM) can be set by the user before launching the selected template.   When the native application is launched, the meta data from the FLNM is displayed in the banner: When using the save as function, the meta data from FLNM is used.   ... View more

As part of accessibility standards, users navigating by keyboard (using the tab key) should be able to move sequentially from left to right and top to bottom through the focusable elements on a page.  They should also be able to see the tab focus. Tabbing in Processor does not meet this standard.  Users should be able to start at the Workspace menu and tab across (to User profile) and down (through function cards Worklist, Search, Create et cetera, and Quick Creates), then tab through their open cards and minimized cards. ... View more

Allow the user to select font, font size, and font color in Processor Workspace view history.  Our clients complain the current text color is too light and small to read easily. ... View more

My client feedback on the Comment box of the Processor workspace is too short, suggest to enlarge the comment box so that it is easier for user to enter multiple lines. ... 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

SS&C stated this is the Chorus behavior and not a bug. But to user side, this is not logical.     ... View more

We have a mix of Users who either love or are overwhelmed by Processor Workspace (as compared to Classic Workspace).  Some of our Users find Cards ability to go anywhere and not have a permanent Docking (or Pinning) Spot (for each Card on Workspace) can be overwhelming.  With an update to allow Docking (or Pinning) of Cards the Users would be able to Move and Pop out Cards (which they have with current functionality) or Dock/Pin in permanent spot to be similar to Classic depending on each Users own preference.    #ProcessorWorkspace #Cards #Chorus #DockingCards ... 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

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. To indicate whether a Source image is ever being viewed. Usually, there are lots of Sources under the Work object, it is beneficial to the client to indicate if any Source is already opened (by anyone), or the other way round, which Source never being viewed, etc. ... View more

My client (on 23.x) comment on the tagline (via Worklist or Search result), do not have sufficient space to display all datavalue.  Currently, they are allowed to displayed up to 20 fields onto the tagline, but the tagline is just limited to two lines, quite often cannot show all of the data. Since client use our Legacy Processor before, they ask is it possible to give them back the table view (as in the Legacy): ... View more

Currently, when a User clicks Get Work and the work item goes to their Worklist, no row is inserted into the View History to document that the work item was received by the User.  If the User updates the work item such as changing the status, then a row is inserted.  The problem is that View History does not show an accurate history of who has had the work item if no update was done.  However, in the WA5 table, there is a row with the EVENT_CODE = BIWRKSEL.   ... 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

My client (on 23.x) having the following suggestion on the new Process workspace. In the Worklist or Search Results (for Work objects), client would like to have the function/button that can auto show the child Sources under every Work objects (say have paging of 25 Works each time). Currently, cilent has the need to review for specific Source, need to click each Work to expand down the child Sources. ... View more

My client (on 23.x) having the following suggestion on the new Process workspace. Similar to the Export function on the History, client would like to have the Export function on the Worklist and Search result as well. (Export result in excel/csv, export fields of AWDID and those fields defined in taglines) ... View more

My client (on 23.x) having the following suggestion to indicate 'the end' on the Search result / worklist. Very often, client search result is a large set of Work objects, user is difficult to tell where it is the end of the search result, or it is still loading.  Suggest to add indicator at the end of list, e.g. “—end—”   ... View more