Unlock Precision Control with UX Builder Buttons: Customize Button Length According to Your Scenario and Business Needs. Along with the current text-dependent spacing, manual length adjustments provide a sleek, uniform appearance for enhanced visual appeal and user experience. Witness a more polished and professional design in the form below, where uniform button size elevates the overall aesthetics. In the below form, you can see. It will look even better if the same-size buttons are presented. Or   ... View more

There are times when work can get stuck in a process and either be locked to SYSTEM or just plain be stuck.  If this occurs, the work has to be manually aborted via a SQL update to the "state" in the WU8 DB table.  This either has to be done by a DBA on a non-hosted environment or by our hosting group via a hosting ticket if they are hosted.  This will then allow the work object to be aborted so it will show in the Process Monitor Aborted tab to be resumed.  It would be nice if the client had an admin type tool to be able to manually abort a work object without having to update at the DB level or open a ticket with hosting to have it done. ... View more

We would like the ability to automate the hopping of in-flight work to the latest deployed version of the process model associated to the Business Area / Work Type. In seeing how each user task within a process model is associated to a back-end identifier (GUID), there would be a match for the same GUID on any newly deployed version of that process model. All active work on the previously deployed version of the process model to be transferred to the corresponding GUID on the latest deployed version of that model.   The Scenario: A business request is received to update/fix an existing process model with a change to routing attributes (for example). The process model is updated with changes to a particular gateway and deployed as the newest version to that BA/WT.   Given Statements: All the work objects created prior to the deploying of the latest version remains on the previously deployed version. The changes to the gateway on the newest version do not apply to any active work objects created on the previous version. The only options at this time: inform the business that the latest changes to the process model will only apply to newly created work objects (date-specific) and that any in-flight work is to remain on the old process model. or the workflow administrator can manually hop (pause existing tasks on previously deployed process model version and resume on corresponding task on the latest deployed version)   Some Limitations: There are some restrictions to manually hopping (pause/resuming via Monitor) work from old to new: Once a work object is "paused" by a workflow admin: any pending timer expiry attributes are lost any suspension activate attributes are lost any user assignments are lost For larger process models that have numerous user tasks, this task of manually hopping could be resource intensive (although it depends on the scenario as well). A monthly deployment cadence where process models could be deployed once a month is not as bad. For process models that have nested sub-processes (could be various levels deep), the manual process of hopping work objects from tasks within a nested sub-process out to the same user task that is nested in a different version of the process model is also labor intensive and requires a methodical approach (where to pause on parent process prior to resuming, etc.).   The Ask: Provide functionality within the Monitoring tool (or elsewhere) to automate the hopping of active work objects to the latest deployed version of the process model associated to the BA/WT. Hop work from and to the same user task (as identified by the GUID) on the newest deployed process model version (if a GUID match is found). For each work object that is hopped, as applicable: retain and reapply the timer expiry attributes retain and reapply the suspension activate attributes retain and reapply user assignments For work objects on the old model that are in a user task that does not exist on the newly deployed model (no GUID match), these work objects are left as-is on the old model and is flagged to the workflow admin (via report or through the Monitor interface, identifying those that were not hopped, requiring manual review/action). Provide the ability for workflow admin to select which processes to apply the hopper automation as there may be situations where hopper automation would not be required, for example, the newly deployed process model is a complete overhaul (user tasks deleted, etc.).   History: Prior to our upgrade to Chorus (previously on AWD SP8.8), we had an in-house SQL script that would fulfill the above functionality. With each month's release, we would include the execution of the process model hopper within our deployment runbook. For the past decade, this script executed without flaw and workflow administrators did not have to manually hop work from previous to newly deployed process model versions with each deployment. The "Active" tab within the workflow admin suite would have the list of all process models deployed, and all work would be always on the latest deployed version (providing ease of work object maintenance as well). However, with the move to Chorus, due to the changes to the back end database tables for work objects, our current scripts utilized with AWD is no longer compatible, and would require a re-write/mapping of GUID, process model version comparisons. ... View more

When emails sent from Communication fail or error in Document Delivery due to one of the email addresses being invalid, we need to be able to resend that email by updating the invalid email address. ... View more

We would like to have the ability to restrict a user’s ability to use the reply to a comment feature. The risk is that users reply to an old comment and that reply is missed by someone in a subsequent step.  Some clients may prefer not to use the feature and prefer only to use standard comments. ... View more

Blue Prism visual studio have an option to integrate with any source code repository such as SVN, TFS, GIT, etc  This features allow the developer work on parallel on the same process ... View more

This is functionality that exists in Legacy Processor workspace and would be very helpful to add to Modern Processor workspace.  Currently, all columns in the history have the same width and the width cannot be adjusted.  This is a challenge because the Comments column can have lengthy test, which is very hard to read if only a couple words can fit on each line.  We should be able to adjust the column width and the system to remember preferred column width.  Also, the Comments column should default to being wider than the other columns. ... View more

We would like to be able to make words on forms bold/bigger/darker color as some of our agents have trouble seeing the words being so small. Especially in read only fields. ... View more

The ability for Chorus Admin users to easily unlock specific objects that are locked to "System" would eliminate the need for self-hosted Clients to engage IT to release objects. Hosted Clients could save time/effort since they would not be required to open a ticket for SS&C Hosting to complete the unlock. ... View more

In the Legacy Processor the user would be able to choose in the drop down what comments to show: All, User Comments, Batch User Comments, System Comments.  Typically our users select "All" and then that will default all comments for all Work Items to be "All" with the new processor the comments always default to "User Comments" even if the user changes them.  I submitted a Customer Care ticket for this and the response was that this is working as expected with the new processor.  Requesting an enhancement to either: 1. Add to preferences the Comments and how the user would like the default setup as. 2. Back to the Legacy Processor way where they changed it one time and it would stick for all future items opened unless changed. 3. Allow a system default set at the company level.  ... View more

Concern is that a reply can be made to comments at different dates/times, so a reply can be missed by business users for day to day processing.  Options are to either: 1. create a resource so that we can give specific users access to be able to REPLY OR 2. add in the Reply Filter in Comments  ... View more

Give form designers more options how to structure the fields in the forms not only in sequential manner but for example in columns. Just to have better flexibility how the form elements are positioned and structured on the page to meet the user experience expectations. ... View more

Good Day, BP Interact could benefit from the following change: Synchronization of AD group membership into Interact Database is 100% manual and Synchronization can not be scheduled - If you add a person to a group that person isn't loaded into Interact until you manually synchronize the people. ... View more

Currently the remove buttons are still shown in read only tables. They are disabled and thus not working, so technically that is correct - but it is still irritating to end users of the platform. Read Only Tables should thus not display the remove buttons at all, which also increases the usable screen space. ... View more

Setting Priority: The Interact Form cannot set the “Priority” on the Blue Prism Queue Item. We have certain SLAs to meet for our processes urgent items i.e., 2 hrs. So definitely need that functionality regarding that and also if possible its better if we can provide statues of the queue item from Interact ... View more

There should be option to save a previous version of a process/ object from the version history. Right now we can just the view the previous saved instance by right clicking in the version history. but we are unable to edit or save it as a new process ... View more

​ I want to have the Option for a CodeReview / Approval Tab in the Obejcts / Processes. ... View more

We need a ‘single modern’ AWD Form Designer. Currently we are having multiple Form Designers in AWD where features found in one are not available in another. It would be good to have all the features in a single form designer which would make it feature complete. ... View more

AWD Viewstation attach docs button automatically truncates the file name to 75 characters. LFG is asking that we develop the same functionality currently available in Viewstation. ServiceNow ticket #CS0014450 was opened as a defect. ... View more