Hi, we've noticed that "Get Report Data" action within "Work Queue" business object is available for selection but cannot be used in BP Next Gen. When we try to use it, we get message "Action "Get Report Data" not yet available.". Because of that we need to do multiple steps get that same result -> Get Completed Items, Get Exception Items, then combine those 2 into one collection and then count them in a separate calculation stage. All of that is typically available in this one "Get Report Data" action. Please have Next Gen Work Queue Business Object aligned with Enterprise in terms of options available. ... View more

If you are currently using manual variables in your communications cog, you have already mapped the data sources in Design. If you add a new manual variable in Communications Admin > Data Source Setup, when you go back to your Communications cog in Design Studio, your new manual variable is not visible.  The only way to get it to show, is to uncheck and recheck the ManualVariable checkbox listed in the Data Sources drop-down list of the Configuration tab in Design Studio.  This more or less "refreshes" the data sources and you new manual variable is visible to be mapped.  The issue is that by unchecking and re-checking that ManualVariable checkbox, is it that it wipes out any previous mapping you've done to other manual variables and those have to be remapped.   See attachment ... View more

We have been utilizing the Chorus Communications feature for some time now and have been hitting several roadblocks in terms of reporting on out bound Chorus Communications emails.  Document Delivery provides very limited details and doesn't provide us all the information we need and also doesn't allow us to go back in time over 30 days.  We are looking for values from the Work Item to be transmitted to the out bound source or recorded from the Communication Service so that we can do additional reporting required such as: Create date - we can get that from the item itself when it created. From Address - this can pass from the parent to the source. To Address - this can pass from the parent to the source. Subject Line - this can pass from parent to source. Plan ID - this can pass from parent to source. SSN - this can pass from parent to source Result - Error/Success like in document delivery) CC Address - this can pass from parent to source. BCC Address - this can pass from parent to source  Enclosure Name(s)  Business Area - this can pass from parent to source Parent Work Type - this can pass from parent to source. Other items she brought up to pass LOB's would be: Who generated the communication (Author) Parent Work Item Key NIGO Reason(s) Doc ID Comm Letter Name (Code) Delivery Type (if we Print/Email/etc). In general, would like to see more reporting capabilities around communications. ... View more

In AWD Classic View, the suspend days option defaulted to max days for the worktype.  We have a client moving from AWD Classic (20.3) to Chorus (24.x) and notice that functionality no longer exists.  The client says productivity is impacted by not defaulting to max days.   A BPS ticket (CS0298627) was opened to showcase this issue, which suggested a product idea should be opened.  ... View more

Implement parameter passing for MAX_SELECTED_ITEMS and MAX_WORK_ITEMS in the POST New Chorus Assignment REST Service, restoring the functionality previously available in SRVGetNewAssign. The Rest service currently uses the defined MAX_SELECTED_ITEMS and MAX_WORK_ITEMS values from the console configurations, which limits solutions to retrieving the same number of items when using the Rest service. This impacts our Customer Serivice solutions which used the SRVGetNewAssign to pass from 1 to 15 as the number of work items to be selected and worked depending on client requirements. While the current REST service will enable us to eliminate the XML Port, it will be a loss of client-side functionality.   POST New Chorus Assignments Creates a set of work selected items for the current user or for a given user ID. Every request will attempt a new work select. Every request can return additional work selected instances up to MAX_SELECTED_ITEMS. Authorizations: basicAuthjwt query Parameters page string The response will start at page number N. Defaults to 1 if a value is not given. pagesize string The number of items that will be work selected for the user. Defaults to 10 if a value is not given. Maximum allowed value is 25.     Java based socket call to a job SRVGetNewAssign where we can pass the input parameters using the XML port:  <AWD>   <xsl:copy-of select="userID"/>                 <xsl:copy-of select="password"/>                 <xsl:copy-of select="maxSelectedItems" />                 <xsl:copy-of select="maxWorkItems" /> </AWD> ... View more

As a Chorus report writer, I need to report on the events within a process and the time taken to complete each event. We also need to report on the Line‑of‑Business (LOB) fields for each event, enable filtering of SYSTEM events where required, and support reporting on both in‑flight and completed work. It is currently difficult to meet these and other reporting requirements using the existing Chorus dimensional reporting schema. We would therefore like to request the following enhancements: Access to LOB history across all reporting objects At present, the Work reporting object is the only object that holds LOB history (CURRENT = 0). We require access to LOB history in all relevant reporting objects. Inclusion of the User dimension in the Queue reporting object A reporting object to distinguish assigned vs. unassigned work We frequently need to report on work volumes by assignment status. Currently, the only workable solutions involve AppStudio or HOLD files, which is not efficient or scalable. Availability of Workstep Names and Process Model information Information such as process names, versions, and workstep names should be included in the reporting layer. Their absence makes it extremely challenging to move beyond basic Queue/Status‑based reporting. Inclusion of efficiency reporting metrics Key operational performance measures should be available directly within the reporting schema. ... View more

I would like to submit a priority enhancement request to increase the character limit for the LOB field, which is currently restricted to 75 characters. For our upcoming initiative, I am building a ticketing system in UX Builder that will allow our clients to submit issues and enable our internal teams to manage and work those tickets end-to-end. As we design the intake forms and workflows, we are finding that the current 75 character limit is not sufficient for the level of detail required. To support this use case, we are requesting that the LOB field be updated to: - Preferably unlimited characters, or - At minimum, expanded to 1,000 characters This change is important because the field needs to capture more descriptive information that will directly support ticket routing, triage, and internal processing. Given the impact to the new client ticketing workflow being built in UX Builder, we would greatly appreciate this being treated as a high-priority enhancement. Thank you for your consideration! ... View more

When you load Process and Service History in Chorus Processor Workspace, not all the history displays at once.  You have to scroll down / resize the window before all of the history appears (if there is a large amount of history).  We would like all the Process and Service History to immediately load. ... View more

Search Limitation within the Document Delivery screen in Communications, as we are unable to search past any items where the Date is over 31 days (From and To) , where we need the ability to search past this.  If we want to search for a Comm doc id we are not going to know necessarily when something was created and if we need to reprint, as it may be outside those 31 days for certain Clients. By increasing the search date it allows users to narrow down search results to a specific period. Users can also filter out any irrelevant results from their search. By providing a longer date range this enhances the user experience by giving them more control over their search and making it easier to find the document they are looking for. ... View more

When assigning items in mass, present a number somewhere on screen of how many you have highlighted at that moment.  ... View more

If a client uses UXBuilder over a private link setup, then SS&C (Project/Support Team) can't access it at the same time. As the private link url would be different than the internet url- devpl.{clientname}.awdcloud.co.uk awddev.{clientname}.awdcloud.co.uk The URL needs to be amended in WSUXBUILDER  resource parameter to get the access.  The issue that makes this one complex to solve is with the variety of UXB setups you can have (not just with CPC), e.g. (non-exhaustive): - A pure over the internet/whitelisted setup where Chorus and UXB sit behind the same URL - A mixed setup (as in this case) where users might reach Chorus and UXB via a number of different endpoints (internet/VPN/Private Link) - A setup where UXB is behind a different address to Chorus entirely (e.g. a 'devuxb.oldmutual' address). The last option is what product have assumed is in play but is not currently something supported by CPC, and even if it was it could still end up with a split access scenario if the customer wishes to use a private connection i.e. you end up with 4 addresses: Chorus over the web, Chorus over VPN, UXB over the web, UXB over VPN. Which would lead to the same problem. Unfortunately because the redirections happen at the browser/user desktop side there is little CPC can do directly to override this. The suggestions given as a solution when discussed were: - Use a browser plugin https://modheader.com/ as a workaround to redirect one address to another locally. (No product release required but of course not ideal) - Update product to allow a map of endpoints for UXB to use which would vary depending on the current Chorus URL (e.g. map awddev.oldmutual to uxbdev.oldmutual and devpl.oldmutual to uxbpl.oldmutual etc), this was seen as quite complex to implement and may still cause gaps in future. - Update the way UXB endpoints are handled within Chorus so that if no specific UXB URL is given in config then the current Chorus URL is used, this was my preferred option but it was recognised there may be edge-cases where this wouldn't work. ServiceNow Ticket Ref - INC2280374 CPC Client: Old Mutual   ... View more

Current Behavior When creating attachments in UX Builder using the “Create Work Object” action on a button, the configuration only allows specifying a fixed number of attachments. This approach can become highly complex and inefficient when dealing with a large number of source or document types - for example, 100 different types . Proposed Enhancement Consider introducing a mechanism to parameterize the attachment source type. Instead of selecting a specific source type from a predefined dropdown, UX Builder could allow passing a variable (e.g., a data source) that determines the document type dynamically based on the user’s selection. UX Builder would then create the corresponding attachment accordingly. This enhancement would be particularly valuable for clients with extensive document type libraries, which is common in banking and financial institutions. Error Handling If the specified document type does not exist in Chorus, the system should display an appropriate error message. ... View more

We would like to have the ability to define the minimum and maximum values for a Number field. Currently, we write process logic to evaluate the values entered and display an error message when it's not in the permissible limits. It would help us greatly if there's a way to define the limits of a field on the form itself. ... View more

Enabling clients to monitor user browser activity within Chorus would provide them with real-time insights, allowing for proactive identification of system issues and reducing reliance on anecdotal feedback, thereby facilitating more efficient incident prevention and resolution. ... View more

With the unlocker tool moving from Utilities to the Management Console, users are now by User ID rather than name. I would like to request that the username be added back to the user field and that sorting be enabled by name. ... View more

Currently, when you use Doc Splitter to create multiple attachments (or sub-documents) that are saved as TIF images.   Clients would like a setting added that gives you a choice of what default format the split documents will be saved as:  PDF or TIFF While there is the feature in HTML CV to export these files as a .pdf, clients don't want to have to export the document and then import it back into Chorus and link it to the original work item. Clients that have their own archiving repositories sometimes can only load images in PDF format, thus making the Doc Splitter TIFF images unviewable.     ... View more

To enhance the Quality element of the Communications process it would be helpful to be able to allow a secondary reviewer of a Letter, the ability to amend the enclosures associated to the letter and then view the output again before passing. Currently when this has been attempted in GIDS UK a new letter is created and data values lost. ... View more

We would like to have the ability to re-publish the archived version of a UXB form. This makes it easier to use the previous versions of the UXB forms without having to create another version of it. ... View more

Today, designers can create and save Process Flow and Automation Service assets, but Chorus lacks a curated, searchable library with categories. This makes existing components hard to find and often leads to re‑building existing work. I propose a Reusable Library embedded in Design Studio where PF and AS assets are categorized and searchable by name or category. This would allow entries to become discoverable via a search by category/name when creating a new Service element. From the designer’s perspective, a one‑click Insert would drop the selected asset directly into a Process Flow or an Automation Service canvas. This would reduce duplicate work, improve design speed, and ensure consistency across builds. ... View more