With BluePrism Hub there is a need to store and distribute the API key. If this could be automated so users can request this and rabbitmq could distribute the key. It would probably need to have an approval or HITL stage gate. Moderator note: Changed the title of this idea to sentence case.     ... View more

Raised on behalf of Antonio Mathias Kühle: We wish that it is possible to have a separate log that show all API request transactions, with all details, so you can track exactly what your request contains, and what the response was.    This log could be a page visible in the BP interface, but the easy fix is just to create a DB table or log file for this.  Important thing is that it is something you can toggle "on" "off" from API configuration settings, separately on each API.  And also important for the DB table is that you can add "number of days" to keep the logs before they are automatically deleted.  ... View more

When a user tries to open an email (.msg) file uploaded to Chorus, the Content Viewer (CV) window opens but the email file is not displayed in the CV window, rather the file is downloaded and then the user is prompted, by the browser, to open the file. This is OK unless the email file in question is large (e.g. contains a large attachment); when the user tries to open such a file, the CV window opens but in chromeless mode, meaning there is no visible cue that the download is running and there is a risk that after a period of time with no file opened and no cue that anything is happening the user will close the window and report that the file cannot be opened. Is it possible to show some sort of status bar in the CV window to indicate that the download is in progress? Either a custom bar or the built-in browser status bar (I believe this would require the CV window to be launched with a flag that forces download progress to be shown in the status bar). ... View more

The application passes sensitive parameters in the URL line of many of the requests. BUSINESS IMPACT: Sensitive data could be disclosed unintentionally through transmission in the URL. Description The application uses the URL to pass sensitive data from the client to the server. Data passed in the URL can be exposed because data passed in this manner ends up in unintended locations. These locations can include server logs, local browser history, and proxy logs. Reproduction Steps Using Burp Suite, navigate through the application. The application passes sensitive parameters in the URL line of many of the requests  Affected Locations HUB v4.7 and Interact 4.7 Decipher v2.3 Recommendation When sensitive data is sent, it should be ensured that POST requests are used instead of GET requests. POST data is not treated the same way as URL data is when requests are sent through systems and do not typically get cached or logged. If there are technical constraints that require data to be sent in the URL then strong encryption should be used to encrypt values. It should be ensured that part of this encryption scheme contains protection against data replay so that captured cryptographic values cannot be replayed back to the server.  References Information exposure through query strings in url | OWASP Foundation A02 Cryptographic Failures - OWASP Top 10:2021   ... View more

Feedback from our processors: Request: Using the quick search lookup we are able to save lookups, however if one of the ‘Fields’ need updating, we cannot edit it, we have to delete the field from the query and re enter it. Are we able to make it editable instead. This will allow for day to day search to be made easier, particularly ones that the date needs to be altered every day for – streamlining our processing times. ... View more

Extend the TO DO List operations to allow replacing multiple substrings with the same new value. Users can input multiple strings to be replaced (e.g., separated by commas) or use an updated UI that supports selecting multiple options for streamlined bulk replacements. Without this feature: users must perform repetitive replacements one substring at a time, leading to inefficiencies, increased manual effort, and a higher risk of errors when managing large datasets. Goal: simplify and accelerate substring replacement tasks by supporting multiple options in a single operation, improving efficiency and user experience for bulk data management. ... View more

Allow users to assign multiple categories to a single event in the timeline, enabling richer classification without the need to overwrite or remove existing tags. For example, categorize an event as both "FTE event" and "legacy tag applied." Without this feature: Users must repeatedly create or edit categories for different analyses, leading to inefficiencies, reduced flexibility, and potential loss of critical context for multi-faceted events. Goal: enhance event categorization flexibility, allowing users to perform diverse and overlapping analyses seamlessly while preserving existing tags for future use. ... View more

Enable the creation of metrics to count the number of times a specific pattern (e.g., X → Y → Z) occurs across all timelines, rather than limiting the count to the number of timelines where the pattern exists. Without this feature: Users cannot accurately quantify the frequency of specific patterns within timelines, leading to incomplete analysis and missed insights into recurring behaviour. Goal: provide detailed insights into pattern frequency across timelines, improving the depth and accuracy of process analysis in the Predecessor Analysis module. ... View more

Add the ability to use logical operators (AND, OR, NOT) in derive field conditions, allowing users to define more complex and precise criteria for deriving new fields in the dataset. Without This Feature: Users are limited to basic conditions, requiring workarounds or multiple iterations to achieve desired results, leading to inefficiencies and reduced flexibility in field derivation Goal: enable more advanced and flexible field derivations by incorporating logical operators, enhancing analytical capabilities and reducing manual effort. ... View more

Introduce a percentage format option for derived metrics when shown in Side by Side module, allowing users to display results as percentages (e.g., 92%) instead of decimals (e.g., 0.92) in the modules. Currently, when derived metrics or KPIs used in Side by Side, we cant use number formatting to achieve percentage values Goal: this would be improving data presentation and user experience. ... View more

Include a breakdown table in the Predecessor Analysis module to provide detailed tabular insights, such as the frequency of each predecessor pattern, associated attributes, and their distribution across timelines. Currently Breakdown feature used in Predecessor module do not have table which gives values in tabular format allowing users to copy these values easily(which is possible in Breakdown module) Goal: this will help for enhancing analysis depth, enabling better comparisons, easy copy data from tabular format. ... View more

Allow users to apply and select categories across different modules when choosing events, enabling a consistent categorization experience throughout the platform. Users face limitations when working with multiple modules, requiring separate categorization efforts for each, leading to inconsistency, inefficiency, and potential data fragmentation. Goal: enhance flexibility and consistency by enabling the use of categories across modules, simplifying event selection, and improving overall workflow efficiency. ... View more

Allow users to open and apply saved queries from the Query Module directly within the Predecessor and Classifications modules, enabling easier access to previously defined queries for streamlined analysis. Users must manually recreate queries for different modules, leading to inefficiencies, redundancy, and potential errors in replicating complex query conditions across modules. Goal: improve workflow efficiency and consistency by enabling users to quickly access and use saved queries across different modules, reducing repetitive tasks and enhancing analysis speed. ... View more

Enable users to select events and attributes across all modules where they are used, similar to how dimensions are filtered, allowing for consistent and efficient selection of data throughout the platform. Currently accessing attributes and events options are different from module to module. Without this feature, Users must manually search for and select events/attributes in each module, leading to inefficiencies, potential errors, and a fragmented experience when working across multiple modules. Goal: streamline data selection by providing a unified, efficient way to select events and attributes across modules, improving workflow consistency and reducing manual effort. ... View more

An ip Rest AP Testing tool, similar to Postman, to test connectivity, payload, to both internal and external api calls.  This saves time/effort to 'test' during a run through a process model.  The testing tool could use the integrations deployed within Chorus.  ... View more

We would like to be able to report if a work item is assigned (Yes/No) within the active detail report or add as an option in searches.  This data element isn't tied to productivity but is only on the dimensions that are at a protected at user level.  ... View more

We have commissioned a client-facing portal to give our clients the ability to log cases in our Chorus system and a requirement has been raised by a client who has seen the suggested solution demonstrated: they require that when they have created or updated a case in the portal they can then generate a summary of all the details they have entered and the documents they have uploaded. They would like the summary to be in the form of a PDF that they could then download and store in their own system. Ideally the summary would be generated on user request. ... View more

The action of hovering over the comments bubble results in a "Preview - User Comments" screen, which only displays a limited number of the most recent comments. The request is that this screen be changed. Rather than a "Preview" -- which only displays some --not all-- of the comments, the request is to just show all the comments & a scroll bar, if it is necessary to scroll up & down through all of the comments.   We are on Chorus v21.2.4.7.  If this improvement has been applied to more recent versions of Chorus, please let me know.  ... View more

Some of our users like to work the cases/searches in the Pop-Out mode.  Others do not. A suggestion has been made by users to build out the 'Preferences" menu to include an option to enable/disable pop-out mode so every card opened by the user is opened in the style the user prefers.   We are currently on Chorus v21.2.4.7 -- so, if this functionality has already been applied to more recent versions, then just let me know. ... View more