The Idea Reduce document / source (Mb) size, simplify document structure, and remove embedded risks to improve ease of retrieval, rendering performance, and overall system stability within Chorus. Summary Customers are experiencing an ever-increasing volume, size, and complexity of documents and source types arriving via email for ingestion into Chorus. These documents, depending on type and origin, introduce a range of performance, usability, and security challenges when processed and viewed within the platform. Examples include: PDFs containing live hyperlinks, external references, and digital signatures that trigger outbound calls when opened Word documents generated by third-party applications containing embedded macros or active content JPEG images, often high-resolution files (e.g. from mobile devices or SLR cameras), resulting in large file sizes RTF and other formatted documents, which can create rendering inconsistencies This increasing variation in document types and behaviour: Impacts performance, with slower load and rendering times Introduces security risk through embedded links, macros, or external calls Adds complexity to the content viewer, which must support a broad and evolving range of formats Degrades user experience and productivity, particularly when accessing large or complex documents To address this, Chorus Capture could be enhanced to support automatic conversion of inbound documents into a simplified, standardised PDF format at the point of ingestion. This would include: Conversion of all supported file types (including complex PDFs) into a consistent PDF format Sanitisation during conversion, removing embedded hyperlinks, macros, and dynamic content Option to generate a lower resolution and optimised PDF image, reducing file size Providing flexibility to balance image quality vs performance, depending on user need By standardising documents at ingestion, this solution would: Reduce document complexity at retrieval and viewing stage Improve performance and load times through smaller, simplified files Reduce reliance on content viewers needing to support an expanding range of document behaviours Minimise security exposure from embedded external content Improve overall stability, consistency, and user experience within Chorus N.B This post is customer sponsored. The (Chorus) product manager concerned would be happy to engage directly with SS&C, to discuss the present challenges and the feasibility of having such a product enhancement.     ... View more

Hi, currently, Hub supports OIDC authentication, however, it supports only deprecated approach via "implicit flow". Client suggests to implement newer "Authorization code flow" which is safer from security perspective. Regards Zdenek ... View more

Debugging issues with Rest API 3.0 Spec files can be challenging.    The Chorus Log files output could be enhanced to provide more information.   Please read attached Claude generated enhancement request. Thanks,   Doran ... View more

Allow WorkHQ Connectors to be callable as objects in WorkHQ RPA processes - improves the flexibility and the cost model for WorkHQ.  Also plays to the theme that Agentic Workflows do the reasoning, RPA does the doing. ... View more

Currently in UXB security, one can setup only one KeyCloak for OIDC: Requesting an enhancement to allow multiple KeyCloak connections.   spring: iam: clientType: "OIDC" roleAttribute: "roles" attributes: - displayName: "User ID" attributeName: "preferred_username" - displayName: "Full Name" attributeName: "name" clientType: "OIDC" roleAttribute: "roles2" attributes: - displayName: "User ID" attributeName: "preferred_username" - displayName: "Full Name" attributeName: "name" security: oauth2: client: registration: keycloak: provider: "keycloak" client-id: "chorus" client-name: "chorus" client-secret: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" scope: "openid,profile,email" authorization-grant-type: "authorization_code" provider: keycloak: issuer-uri: "https://keycloak-health-test.ssnc-corp.cloud/auth/realms/testrealms" ... View more

Hi, with current Session Logs configuration it's hard to review whole session, as not all data fields that are useful are available (i.e. Item Key) and if there is long string in Result field (i.e. long exception), table column is automatically extended, there is a bottom bar appearing to enable checking what's on the right side of the table, but at the same time if we have 50 logs on a page, we need to scroll to the bottom to be able to move table view to the right and then we need to scroll back up and try to find the row that we were interested in, but then log number is not visible. This ideation is to add option to customize Session Logs view - i.e. option to resize column, hide/show columns, maybe change the order of columns and at the same time option to add other data points that we may be interested in (like Item Key or Item ID). It would be also useful if we could filter based on any of the columns. ... View more

In current version when encountered an error on Attach action, Window Title and Process Name are not populated which makes it difficult to understand from the log perspective, where the process failed. Since in the Exception Details both options are mentioned, it would be a good idea to actually provide the current values.  Current system exception: 'ERROR: System Exception : Failed to attach to target application: Failed to perform step 1 in Navigate Stage 'Attach' on page 'Attach' - Target application could not be identified, please ensure the application is running and review the following action inputs and/or application model identifiers: WindowTitle, ProcessName' Idea: 'ERROR: System Exception : Failed to attach to target application: Failed to perform step 1 in Navigate Stage 'Attach' on page 'Attach' - Target application could not be identified, please ensure the application is running and review the following action inputs and/or application model identifiers: Application XYZ-Home/Login, Start Application XYZ' ... View more

Currently when reviewing logs in Blue Prism WorkHQ (previously NextGen) when we click on an eye to view parameters we're being transferred to a new page (in the same window) and when we want to back out we're being moved back to the beginning of the logs (1st page) with all our filters and logs per session reset. This is making reviewing logs very difficult (especially for big models where we may have thousands of logs) Please change how parameters, preferably with a window appearing on top of the screen, with possibility to close it without impacting session logs view.   ... View more

Our organization’s initiative is to transition applications from on‑prem Active Directory and legacy authentication mechanisms to modern authentication using Microsoft Entra ID. We would highly encourage Blue Prism Enterprise software to support integration with Microsoft Entra ID. ... View more

If there could be a way to disable or hide forms from being visible on the dashboard. Currently, this is causing some confusion, as users tend to submit forms directly from the dashboard instead of navigating through the Inbox. ... View more

It would be great if the emoji option (WIN+.) could be disabled in Chorus comments.  Comments can be used in a court of law and emoji understanding/meaning can change over time. ... View more

Currently the overview of the work queue offers a number of filters. This IDEA is to add the filter "Tags" The Proposal Introduce Tag‑Based Filtering on Work Queue Items A lightweight enhancement that allows workers and automations to selectively pull queue items based on business‑relevant tags  Business Benefits Faster processing of critical work Smarter workload distribution without queue sprawl Improved scalability & flexibility for new clients, regions, and use cases Reduced operational complexity and custom logic How It Works (High Level) Work items can have multiple tags Consumers apply simple include/exclude filters when fetching work Existing priority and ordering rules remain intact Fully backward compatible ... View more

The SS&C AI Chat does not appear to provide reference links to sources which is critical for verifying the accuracy of a generated response, e.g. checking for hallucinations. Majority of other providers (Gemini, Microsoft and Claude) include URL links at the bottom of the response for users to go verify the information returned by generative AI ... View more

It is highly recommended that Decipher IDP provides native capability of extracting Arabic text. Blue Prism (BP) currently provides the capability Arabic extraction via connecting to third party tools and connectors (which is charged separately and adds to the overall automation cost). However, the product itself should have this capability.  In addition, Blue Prism Enterprise currently provides basic capability of Arabic text extraction. However, it does not meet the business expectation of accuracy % for the extracted text.  ... View more

The following applies to  End User (internal user / client user) in which currently the Queue Item Defer date/time displaying in a format yyyy-mm-dd and make this configurable Supporting Actors could be Browser (Chrome, Edge, Firefox) Operating System Locale Web Application UI Layer Goal Allow users to view dates in their preferred format (dd‑mm‑yyyy or mm‑dd‑yyyy) within the web application UI to reduce confusion, misinterpretation, and data-entry errors. Problem Statement Dates displayed in web applications are often rendered according to the browser or OS locale, not the user’s explicit preference. This can cause ambiguity and errors, especially in international environments where both US (mm‑dd‑yyyy) and EU (dd‑mm‑yyyy) formats are used. Example: 04‑05‑2026 US user interprets: April 5, 2026 (mm-dd-yyyy) EU user interprets: 5 May 2026 (dd-mm-yyyy) Functional Requirements FR1 – User Preference The application shall allow users to select a preferred date format: dd‑mm‑yyyy mm‑dd‑yyyy FR2 – UI Rendering All dates displayed in the UI (lists, tables, detail views) shall respect the selected date format. Formatting is handled at the UI layer, independent of browser default locale. FR3 – Input Handling Date input controls must accept user input consistent with the selected format. Non‑Functional Requirements Consistency: Same date format across the entire application. Accessibility: Date format clearly visible and predictable. Internationalization: Decoupled from browser or OS language settings. Auditability: Backend data remains locale‑neutral (ISO format). Main Flow User opens Profile / Preferences. User selects preferred date format (dd‑mm‑yyyy or mm‑dd‑yyyy). Preference is saved. UI re-renders all visible dates using selected format. All subsequent sessions respect the stored preference. Alternate Flows A1 – No Preference Set System defaults to: Browser locale or Organization-wide default (e.g. dd‑mm‑yyyy for EU tenants) ... View more

We allow operations management to unlock individual users.  We do not allow them to unlock system / Process Models.  With 25.1.1 the UNLKTOOL resource appears to provide User and System unlocker functions.  We'd like to see a resource for each function. ... View more

This is found in the The messageBridge integration layer.  I would like the Chorus window console log to write entries for received and sent messages. These messages in older versions were: "[AWD - Message Received] Message ID:" and "[AWD - Message Posted] Message ID:" (including timestamps and correlation IDs. I needs to work like it did in Legacy Processor.    ... View more

I have utilized Smart Vision mode to identify an element within a Citrix-based application (Envision). However, when attempting to retrieve the value of this element, a discrepancy has been observed between the intended value and the retrieved value. Specifically, certain characters are being misidentified; for instance, 'G' is being recognized as '6', and 'A' as '4'.   The "Text Content" field within the Smart Vision editor is currently uneditable, which prevents the correction or update of these misidentified values. It is important to note that this is not a consistent character-specific issue. Within the same string, the character 'G' appeared twice; the initial instance was correctly recognized, while the subsequent instance was misidentified as '6'. The Citrix resolution remained consistent throughout the development and testing phases.   Therefore, I recommend the development of an updated version of Smart Vision that addresses and resolves this character recognition issue. ... View more

Currently you can use an expression the exception detail, however in some cases it would be useful to raise dynamic exception types based on the response of an API request. What I'd like to build is a rules engine that can "tell" a process to perform various core actions, one of those is around raising an exception which might look something like this: "actionType": "RAISE_EXCEPTION", "actionPayload": {"type": "Business", "reason": "Business reason here"} Currently I would have to create a choice stage and map each exception type which is very inefficient, especially if implementing across different processes.. This will also lead to a lot of code duplication and long term quality / maintenance issues. ... View more