Users have ability to suspend BUT they can use the suspend feature to take work out of quality by Suspending and then having an activate status that wakes up in a different queue.  Essentially bypassing quality. We would like the suspension feature to have additional access to restrict the activation status option or ability to add an activation status as addtional resource. Thank you ... View more

Chorus is not able to send a dynamic JSON array (that contains the object keys to delete). The length of the array is defined at design time, so in runtime there is no apparent way to populate an array with a dynamic number of object keys to delete. That is, there is no dynamic array capability within Chorus which presents a challenge for batch Chorus objects deletion. ... 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

Add visual markers or color-coded highlights in the timeline to indicate where filter-triggering events occur, enabling users to quickly identify and navigate to these critical points without manual scanning. Without this feature: currently Users have to manually review each timeline to locate trigger events, leading to inefficiencies, missed insights, and reduced satisfaction with the tool. Goal: enable faster and more accurate identification of filtered events, improving user experience, boosting adoption, and accelerating decision-making. ... View more

Introduce functionality to filter timeline events based on designated points, allowing users to view only events that occur before or after a specified event (e.g., show the journey after a letter X is issued). Without this feature: users face difficulties isolating relevant parts of the timeline for analysis, leading to slower insights, increased manual effort, and a less efficient user experience. ... 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

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

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 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

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

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 which is being built using the UX Builder and it has been noted that there is no option for a user to log out of the system. We would like to have the option to add a "Logout" button or link to every page in the system so that users can terminate their session as required. ... View more

We have commissioned a client-facing portal which is being built using the UX Builder and we require more complex client-side validation than is currently possible. For example, if the user were to enter a policy inception date (PID), a policy expiry date (PED), a claim event date (CED) and an insured date of birth (IDB) then we would want to validate that the IDB was prior to the PID, that the PID was prior to the CED, that the CED was prior to the PED. We would also want to check that the IDB did not make the insured person impossibly old or too young to have a policy. These dates are just one example of client-side validation that exceeds simple data typing - we would like to see configurable complex validation rules in the UXB, some of which will depend on mixed data types (e.g. if _this_ dropdown have value "A" then _this_ amount must not be zero). ... View more