An enterprise customer (Chorus/ Bridge/ Document Automation) uses the capture process to ingest images that originate in emails. Because the sources are sent as a packet that should be worked as a single work-item in Chorus, they would like to send them as one transaction to Document Automation.  Our request is to facilitate transitioning this customer to be able to submit multiple sources into a single DA batch. ... View more

The ROS plugin, when activated, automatically opens two windows which are visible to the user -- Word and Excel.  Users can accidentally close one or both of these windows, resulting in errors.   Can the windows open invisibly in the background? ... View more

It would be beneficial if we had the ability of exporting credentials from one version of BP such that they can be imported into a newer version of BP. Issues were experienced during our migration from V6.8 to V7.1 such that it was strongly advised for us to do a migration of automations over a few weeks, instead of over a weekend. Our migration required about 190 bots to be migrated. Future migrations could be double or more. Having to extract the password from BP by running get credentials once per user and then manually keying those across to 7.1.2 was very time consuming and annoying. ... View more

It would be beneficial to designers integrating with REST services to natively provide instructive messages for connectivity exceptions.  OpenApi/Swagger describes http response codes but not java exceptions outside normal http flow.  For example this exception is captured for connection errors: com.dstawd.processengine.model.flowobjects.AutomatedActivityFlowObject.executeService(ProcessInstance, String, String, Element): Service failed to execute. Error: java.lang.IllegalAccessException: The response object is javax.ws.rs.ProcessingException, not an fastrequirementsapi.ApiException Service Error Stack:   It would be beneficial for these types of errors to expose the actual java exception or a friendlier message to the designer.  This information can be found in log files that typical designers do not have access to. ... View more

Right now, BP does not have trigger-based run features, which are much needed in automation. This is something that can be added in the BP, as there is no native trigger-based mechanism. It is much needed and useful in many use cases where users don't want to keep polling and occupying licenses. ... View more

With Search forms and potentially and Chorus form designed for work processing whether UXBuilder, Dynamic Forms, or Traditional forms the ability to denote a one of these are required.  My thought on implementation would be to contain the fields within a group box and mark the box with a css class of oneOfThese.  There could be multiple group boxes with independent oneOfThese markers.  This was implemented as custom javascript on a Search form that required a hidden text input that was marked required that the custom javascript managed inputting/clearing to get the Search button enabled/disabled appropriately. ... View more

Currently, in Decipher there is no option to see the submitted batches, which can be helpful for what the user has verified and helps to understand if there is any mistake done by the verification user. There should be a tab available in Decipher with all the submitted batches and once we click on the particular batch it should show the data as like the Data Verification screen with 3 panels for that batch with Page overview, fields, and mapped/verified data. The batches should be grouped with that specific unique identifies for the template as like if it is Purchase Order then it should have to group with the Document Type and then if the multiple PO templates from customer 'ABC' then batches has to be grouped with that customer name with the timeline of the batch. From this we can achieve the machine learning capability of the Decipher to train that particular document type and update the way of document training through verification. ... View more

Currently when configuring Parent/Child relationships in Communications, there can only be one parent client associated with multiple child clients. Clients would like the ability to have multiple Parent/Child relationships in Communications so they can have more flexibility to support global settings for a subset of children.  Some clients have different divisions within their organization like a French, English or German division.   By having the flexibility of having multiple parent/ child relationships they can better manage the content, date sources and delivery set-ups for these scenarios. ... View more

We have a mix of Users who either love or are overwhelmed by Processor Workspace (as compared to Classic Workspace).  Some of our Users find Cards ability to go anywhere and not have a permanent Docking (or Pinning) Spot (for each Card on Workspace) can be overwhelming.  With an update to allow Docking (or Pinning) of Cards the Users would be able to Move and Pop out Cards (which they have with current functionality) or Dock/Pin in permanent spot to be similar to Classic depending on each Users own preference.    #ProcessorWorkspace #Cards #Chorus #DockingCards ... View more

HTML Content Viewer – Provide an option to enable links within the html email body source.  Currently these links are suppressed for security reasons.   Clients are receiving high volumes on emails ingested into Chorus providing links to additional information instead of including attachments. We have tried these work-arounds and none of them provide a good user experience Open in the default HTML CV, then select the option to open in native – which downloads it, requires a double click to open it, then launches a new tab where we have to manually close it later. Create a resource to open in the native HTML application – which automatically downloads it and opens it in a new tab, where we still have to manually close it later.  But this is an all or nothing option.  Even for sources that don’t have links.  Use an “EQM flow” where a service operation can retrieve the html source and load it into an “external” form so that the user can reply to or forward that original email as part of the workstep.  Although we don’t have a requirement to reply to our forward the email as part of this step, we determined that it doesn’t enable the link either. ... View more

As a Chorus user I need to be able to print all attachments related to a Case to comply with legal review and FOI requests.    As opening and printing each attachment in Content Viewer is time consuming, I would like: To be able to print from the attachment context menu in Processor Workspace (this was a documented option for Legacy Workspace on Chorus 20.1 but not implemented). To be able to print option from the work item context menu in Processor Workspace, with an option to select which child attachments to print. ... View more

We would like the AWD Option of 'Expire by Date' to work with Processor Workspace as it did with Classic Workspace.  In Classic Workspace we used the 'Expire by Date' option to have any items suspended for a day to unexpire with first Batch run of the day.  However with Processor Workspace this option doesnt work as Processor was not coded to use it.  We would like this 'Expire by Date' option to work with Processor Workspace to match how it works currently with Classic Workspace.  Let me know if there are any questions.  ... View more

During initial demos to users, several of them have asked for a dark mode option to offset the glare you get from lots of white space. Our users will have the Chorus Processing screens open all the time during their workdays. ... View more

Currently, the Exception Types are created by users manually typing into the combo box within the Exception Stage's properties. This often leads to multiplication of the same exception type due to typos, misunderstandings, etc. Example below: This in turn becomes a nightmare when it comes to reporting, as often a hard set rule cannot be followed for extrapolating these from the overall pot. I suggest removing the ability to add new exception types by typing into the combo box, and instead make it a privileged action within the System settings. For example within the already existing Exception Type screen: This could be done by implementing an "Add new exception type" action on the side panel, below the already existing "Scan processes" ... View more

We should consider raising this display/resolution issue with the development team, as it has been observed by numerous users. Ideally, software should be capable of adjusting to users' display settings without requiring them to change display settings on their machine. ... View more

I would like to have the ability to have Decipher consider the option that a document may not match any document types associated with its batch, and to classify it as 'out of scope' or 'other'. Currently if a batch type has two document types assigned to it (for example), then when it classifies a document, it splits its 100% confidence between those two types. So, if it is only 5% sure that the document matches type 1, then it is 95% sure that it matches type two by default. If your document stream contains files that are out of scope (other forms, or photos or email attachments) and don't match any document types associated with the batch type, this can lead to false positives. It also doesn't give you anywhere to 'put' these out of scope documents other than raising them for verification. I would like a way to indicate that a batch type contains out of scope documents and for decipher to consider matches to all known document types and if the independent confidence level for each match is below a certain threshold, the document can be classified as 'out of scope'. ... View more

In the latest version of Blue Prism, the standard VBO will no longer be included with the installer, but will be downloaded by each user from the DX. A search for "Blue Prism Enterprise - Core" now shows 26 VBOs. Downloading them one by one is complicated, and there is a high possibility of errors such as missing downloads. Please change the DX specifications so that downloading and bookmarking can be done for all Core VBOs at once. ... View more

In Chorus when a user views the work items history the KE/ST steps in the workflow do not appear. This causes confusion for the user if they anticipated a step being done. It is also an audit concern because it is not a true history of everything done to the work item. Moreover, the KE/ST should not only appear in the history, but it should print as well. We print out the history for the purposes of audits to validate processing procedures were met. ... View more

I believe it is advantageous to include the list of default objects within the learning edition of Blue Prism (which was the case prior to 7.3). I can't speak on behalf of everyone but we currently don't have a training environment within our Enterprise install of Blue Prism and utilise the learning edition to run training of the Blue Prism product. Not having these included with the learning edition requires us to provide a release file to each trainee, or have them download what they need from DX directly. Also, I note that the documentation is not correct for verifying an installation as it still points to the VBO folder, which is now empty as of 7.3. ... View more