When a process or business object's name is changed all references to that process or business object are lost. This great affect reusability and results in artifacts with improper names to retain references. Proposed Solution: Artifacts have a NAME (static for DB), LABEL (shown in GUI for ease), and DESCRIPTION. This will allow artifacts to have their LABEL updated easily without breaking any references to that artifact. ... 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

Invesco has identified a loss in functionality from EnCorr.  Our processors would like to have the option to save a draft of a letter they are creating, to be able to come back to it, and complete the letter at a later point. They want this option when it is necessary to gather additional information about the content before completing the letter. ... View more

Electronic communications with customers (as PDF attachments) are often sent password-protected, requiring the customer to enter a piece of data known only to them.  This enhancement potentially prevents/reduces the potential for fraudulent activity should a customer communication end up in the wrong hands.  For email communication, there is the concern that emails could either be intercepted in transit or opened by someone other than the intended recipient. ... View more

We are thrilled we can now deprecate Chorus Design Studio Presentation Flows, Automation Services, and Sampling Services.  Can the Deprecate option be added for Processes that aren't currently deployed? ... View more

Currently conditional content relies on variable or LOB data to select content.  Our clients need an option to let the user select content from a list presented in Word that is driven by conditional content rules. Alternately providing a simple list of content to choose from fulfills the need. ... View more

Currently you place variables within content and the information is filled in through LOB fields or variables entered within the Presentation.  The client would like to be prompted to complete certain variables (fields) once the letter is presented for view. Word Developer offers some ability but nothing forced or the ability for it interact so it takes you to the next spot for entry. ... View more

Enhancement request for the Delivery form to be configurable by Chorus BPM Admin as a resource: 1. Source Type - value should allow for admin to predetermine the source type, not user input 2. Phonebook - ability to save public or private entry should be controlled access. User can be directed to have to enter values each and every time manually in order to mitigate from incorrect selection from their private phonebook ... View more

Currently in Blue Prism Hub/Interact v4.5 users with mail attribute not set cannot be imported from Active Directory. In our development environment it's quite usual to have test users without email address. For security reason our admin users are not allowed to get an email address. Nothing more to say. Please see [#191880] In BPHv4.5 users without email address can't be imported from Active Directory : Global Customer Support (blueprism.com) for more information. ... View more

In Communications, we have an enclosure template that uses variables such as the broker on record and the shareholder on the account. When you choose to include either of these when writing a letter you cannot modify the enclosure to change an address or a name or any other information. You also cannot add an enclosure to a letter if you forgot to do so in the process flow steps - you'd have to cancel your letter and start again.  Invesco would like to see more flexibility in handling enclosures where the processor does not have to cancel out of their current letter and start over. This is wasteful for the reps creating client letters. ... View more

In Document Splitter, all annotations on pages added to new subdocuments or compound documents are preserved, i.e. copied from the original documents.  In some customer implementations, these annotations need to be deleted manually each time a new document is created.  An option on not copying the annotations in creating new documents is required.  The option default (copying vs not copying) should be set at the system level or even at the user level. ... View more