Having a 'view only' role would allow reps to see the full content of a letter template without going through the process of creating a letter to see the details.  The existing Association Report does not sufficiently provide the full details of the templates or reusable content. ... View more

Currently, when a rep selects a shortcut to be inserted into a letter, the rest of the sentence is pushed to the next line. While this is a behavior of Word, a solution to this issue should be developed for Communications to reduce the amount of formatting/modifications a rep has to make to complete a letter. ... View more

Currently failed posts to Splunk by Data Gateways/Logstash are dumped to the Dead Letter Queue and left there to accumulate.  These can be resent using the Logstash API; however, this should be provided by the Data Gateways platform and represents a blindspot in the tool. ... View more

Setting up these products are always been a complex task. I'm wondering why are we not merging all the installers in a single package for the user to directly run it. We can also include Rabbit and Erlang in the same msi/exe installer so users can install it easily. When starting the tool the installation itself gives so much pain that users will definitely lose interest in the beginning only before using the tool. And it is not just with Decipher. Try Hub, Interact, BPD,  all of the setup steps are extremely complex and high chance of facing a variety of errors. Just to set up Decipher user needs to run 7 individual installers! I agree we have proper guides and videos for each component but installing and configuring these many items are really not user-friendly. For e.g. To install Blue Prism Enterprise we only run a single package likewise I believe each of the products should have a single and straightforward installer to make life easy for everyone. I've raised this before in one of our roadmap call with the product team last year in 2022 but new versions are coming up with the same installation steps and framework. Hence raising these here as an idea and to know how other users feel about the same. Thank you  ... View more

https://university.blueprism.com/certification/ Certification exam codes are not mentioned on these exam details pages. Can we please include the exam code in the certification details as well? On the Pearson portal, we can see the below codes - ... View more

With the current version of Capture we can only customize (under User Settings) for example company logo and colors. But is there a possibility to customize the Contents ? Right now when we are finished with the entire recording and want to download the PDD , it comes with a default set of Contents and it is tedious to change and adjust the headings and sub-headings according to the company standards and requirements. If we can set these headings and sub-headings prior to the download just like how we do with the Logo and color under user settings that will save a lot of time and energy.  Default Contents: Desired Contents: ... View more

Currently the WSS-Username Token Authentication for outbound SOAP calls only allows the use of a plaintext password. This request is to enhance this capability to allow the encryption of passwords when using this method of authentication. ... View more

In BP Client (v6.9) / System / Licenses, an overview of installed licenses are shown with various types of information. It would be nice to be able to select what columns are shown so non-essential information can be hidden (eg Processes, Resources, Alerts is always unlimited for us). Column should be resizable so longer owner names can be read Background: we have several environments with dozen of license keys and have to sometimes shuffle license between dev/prod and inbetween.  Owner name in a license file is up to 25 characters with the last to characters being the sequence number of the license. (A central license management across all environments would be best though) ... View more

Hello currently BP Desktop is compatible with version 7.1 and above. this idea is for backward compatibility of BPD with old version of BP. ... View more

When we run process from process studio and if there is any exception then it will bubble up to main page recovery (assume - no handling on subpages). There is option to find which stage given exception but if you restart from that step then process will again throw exception on END stage of sub-page. it should continue with flow before exception. ... View more

I'd like if the Object Conversion Utility (OCU) could be a Chorus Workspace, so I wouldn't have to log onto it separately from Chorus BPM.  Thanks! ... View more

Hi Team, How about adding a new feature in Blue Prism decipher to recognize stamp in a document. ... View more

A Command line switch for Immediate stop for the running session would be an added advantage for controllability ... View more

We would like Chorus BPM to support richer, multi-level parent-child relationships between work items, allowing a business hierarchy to be represented directly within the Chorus work model. The current Chorus object model supports explicit parent-child relationships, including a case containing multiple transactions/tasks. However, the documented relationship rules do not allow a transaction/task to be the child of another transaction/task. For more complex business processes, we would like to extend this concept beyond a single task level so that a hierarchy such as the following can be represented natively: Case ├── Task A │   ├── Sub Task 1 │   └── Sub Task 2 │ └── Task B     ├── Sub Task 1     └── Sub Task 2         ├── Sub Task 1         └── Sub Task 2 The intention is that each level represents an explicit relationship between independently processable work items, rather than representing the hierarchy indirectly through naming conventions, reference fields, or other metadata. Desired capability Ideally, Chorus would support: Multiple levels of parent-child relationships between processable work items. Explicit relationships that can be navigated and understood by Chorus rather than inferred from work-item metadata. Parent work that can coordinate processing based on the state or completion of its child work. Child completion that can signal or otherwise participate in progression of its parent, supporting event-driven orchestration. Multiple branches of work executing independently or in parallel beneath the same parent. Relationship information being available for operational visibility, troubleshooting and reporting. The objective is not simply parallel processing. The requirement is to maintain the business relationship between parallel work items as part of the Chorus work model. Business example A Disability Claims process provides a useful example. A single claim may involve multiple products that need to be processed independently and potentially in parallel. Each product may then have its own downstream activities, such as assessments, payments or work associated with individual payees. Conceptually: In this type of process, the hierarchy is meaningful business information. We would therefore like the workflow engine to understand and maintain these relationships directly. Where relationships must instead be reconstructed using naming conventions, reference fields or custom linking attributes, additional application logic is required to determine which work items belong together and when the related work has completed. This makes orchestration, reporting, troubleshooting and future extension more complex. Business value Native multi-level work-item relationships would allow Chorus to model complex business processes more closely to their real-world structure while preserving independent and parallel processing. It would also support a cleaner orchestration model in which relationships are explicit and process progression can be driven by the state of related work, rather than requiring consumers to reconstruct those relationships through conventions and queries. This would strengthen Chorus as a workflow orchestration platform for use cases where a single case can contain multiple levels of independently managed but related work. ... View more

We have experienced recurring incidents during certificate updates in Chorus where a certificate configuration issue, typically relating to certificate/keystore password misalignment or password compatibility (for example, special characters), results in a significantly broader platform impact than expected. To date, we have observed this behaviour primarily during mTLS certificate updates. When an mTLS certificate or its associated keystore is incorrectly configured, the impact does not appear to be limited to the integrations explicitly requiring client-certificate authentication. Instead, all SSL/TLS-based outbound integrations from Chorus become unavailable, resulting in a complete loss of outbound API connectivity rather than an isolated failure of the affected mTLS interfaces. This creates a significant operational risk during certificate introduction, renewal, replacement and configuration changes, as an issue affecting a single certificate or keystore can potentially become a common point of failure for otherwise unrelated integrations. While our incidents have predominantly involved mTLS, we would like the investigation to extend beyond mTLS and consider the handling of all TLS certificates, keystores and trust stores used by Chorus. We want to establish whether similar failure behaviour could occur when any TLS-related certificate or configuration is expired, unavailable, invalid, incorrectly configured, or protected by an incorrect or incompatible password. Could you please investigate: Why a failure associated with an mTLS certificate or keystore can affect outbound HTTPS integrations that do not require mTLS. Whether Chorus uses any shared SSL/TLS context, certificate store, keystore, trust store or initialization process that creates this common failure dependency. Whether equivalent behaviour could occur with other TLS certificates or certificate stores, even where mTLS is not involved. The failure behaviour when individual certificates are expired, invalid, unavailable, incorrectly configured, or have an incorrect/incompatible keystore password. Whether certificate and keystore validation failures can be handled in a manner that isolates the failure to the integration or function that actually depends upon that certificate. Ideally, we would like the platform architecture and certificate handling to ensure that: mTLS-specific client certificates and keystores are isolated from general outbound TLS/HTTPS communication. Individual TLS certificates, keystores and trust stores are isolated from unrelated integrations wherever technically appropriate. A failure affecting one certificate, keystore or TLS configuration impacts only the integrations that depend upon it. Standard HTTPS integrations that do not require a client certificate continue to operate if an mTLS client certificate is expired, unavailable or incorrectly configured. Unrelated TLS integrations continue to operate where a different certificate or certificate store has a configuration problem. Invalid certificate or keystore configuration is detected and reported with sufficiently specific diagnostics to identify the affected certificate/store and dependent integration, rather than resulting in a wider loss of outbound connectivity. Given that Chorus 26.1 includes a specific correction for outbound mutual TLS whereby the platform reads the mTLS system configuration before invoking connector APIs, we would also appreciate confirmation of whether this change affects, or is intended to improve, the failure/isolation behaviour described above. Blue Prism Chorus 26.1 Release Notes documents this change under (AWD-85176) Outbound mutual TLS. ... View more

Within Processor Workspace, users must resize and position cards each time they hit 'Get Work'.  Ideally, Chorus Processor Workspace would remember preferences on card size and placement so that after this is done once, users don't need to do it again (unless they want to change it).   ... View more

When Generating a PDF for an attachment in UX Builder, the FLNM is too generic: document_2026-10-05.pdf . If a second pdf is generated and attached to the same work object; both sources FLNM are called document_2026-10-05.pdf. If a UXB Project generates 100 PDF's in one day, all the PDF's generated are called document_2026-10-05.pdf, stored in FLNM. Solutions: 1. Change to a timestamp for more uniqueness. 2. Allow UXB to name the document. If the name is not valid, default to timestamp, Use a data source! A Case was generated (CS0542621) to determine if this was a bug, but it was reported as working as designed. What does the community say?  Generic name or something more specific?   ... View more

Support for SSO/AAD-SAML Authentication in the Decipher VBO Product and Version Blue Prism Enterprise Decipher IDP 2.4 Decipher VBO 1.1 Description: Customer is currently migrating from Decipher 1.2 to Decipher IDP 2.4. The Decipher web application is configured to use Single Sign-On based on AAD/SAML. Users can successfully authenticate to the Decipher web interface via SSO. However, authentication fails when configuring a connection through the Decipher VBO in Blue Prism Enterprise. The Decipher server is reachable through the configured hostname or IP address and port. Invalid usernames are correctly rejected, and the valid user account is recognized. However, authentication fails with an “Invalid Password” or similar authentication error when the Windows credentials of the SSO user are used. The same user can successfully log in to the Decipher web interface via SSO.  Current Behavior: A connection to the Decipher server can be established. The configured server and port are reachable. Invalid usernames are rejected with an appropriate error message. The valid user account is recognized. Authentication through the Decipher VBO fails with a password or authentication error. The same user can successfully authenticate to the Decipher web interface via SSO. Expected Behavior: The Decipher VBO should support authentication against Decipher environments configured for AAD-/SAML-based SSO. If SSO authentication is not supported by the Decipher VBO, Blue Prism should provide clear, documented, and security-compliant guidance on the officially supported integration approach. This guidance should specify: which authentication method is supported by the Decipher VBO, which credentials must be provided in the VBO, whether a dedicated non-federated service account is required, whether any additional configuration is necessary, which limitations apply to Decipher IDP 2.4. Business and Security Benefits: Support for SSO/AAD-based authentication in the Decipher VBO is a specific customer requirement but for sure relevant for other Enterprise Customers.. This requirement is primarily driven by security and compliance obligations, as well as the strategic preference to manage access exclusively through centrally controlled Single Sign-On wherever possible. The current dependency on native Decipher credentials or separate non-federated service accounts represents a limitation in SSO-centric environments. This limitation must currently be explained and justified to internal stakeholders from both a security and compliance perspective. Native SSO support in the Decipher VBO, or alternatively a clearly documented and officially supported workaround, would: support compliance with security and regulatory requirements, reduce the number of separately managed credentials, lower administrative overhead, simplify the integration of Blue Prism and Decipher in AAD-/SAML-based environments, improve the suitability of Decipher for organizations with mandatory SSO policies. ... View more

  During webhook integration testing in BPE 7.5.1, i noticed that platform currently supports only Basic Authentication ( user name, Password ).  This idea is to support other method as well -> Client ID / Client Secret authentication Bearer Token authentication others Webhooks #Webhooks #7.5.1 ... View more