My suggestion is to add an AutomateC command to enable or disable a specified existing schedule. This capability would greatly expand the flexibility of the Blue Prism scheduler.  Currently we have processes that have to be scheduled to run once (or more) every day, mostly just to determine that they don't need to do anything on that day. These superfluous runs create noise in the control room, extra logs, and potentially cause other processes to not run because all licenses are in use at that moment. For example, we have a process that needs to run every 30 minutes but only on one or two specific days of the month. The only way to do this currently (using just the BP scheduler) is to schedule it to run every 30 minutes every day, and either add logic so the process can determine that it shouldn't do anything most of the time or manually disable it for most of the month and manually enable it on the days when it should run. With the proposed enable/disable AutomateC capability, we could maintain a file (Excel workbook?) containing a list of schedules. Each schedule in the file would have a business day or calendar day of the month and whether the schedule should be enabled or disabled on that date. A BP process would run early every morning and process this file. The BP process can determine the current business day and calendar day and enable/disable schedules accordingly. This would enable more efficient scheduling for processes that only run quarterly, monthly, bi-monthly, or on specific days (whether calendar days or business days). ... View more

We have a lot of requests in Interact all sent to the same role since they need to be able to view each others errands. But it would really ease handling if you could create subfolders to the Inbox and move requests around with same principle as your email inbox. ... View more

When exchanging experiences with the team of another (non-RPA) automation tool we got an idea that might improve how BP identifies (web) UI elements. Currently BP seems to use the absolute path of an element for identification and has to parse the whole UI / HTML page to find this element again. The identification consists of the 'path' to the element and the attribute of the element.  The disadvantage is the increased time to parse the whole document (therefore using matchIndex can bring big improvements) and failures in case the actual path to the element differs to what BP expects. An alternate approach is to use the hierarchical organization of element. The difference would be: absolut path might look like: /HTML[1]/BODY[1]/MWD39-MODAL[1]/DIALOG[1]/DIV[1]/NG-COMPONENT[1]/DIV[2]/DIV[1]/FORM[1]/DIV[1]/SELECT[1] If any order changes (eg DIALOG changed from 1 to 2) the element will not be found. The alternative would be to identify the element in steps with each step would be able to have its own identification. eg go to MWD39-MODAL, find DIALOG as defined by..., find DIV with NG-COMPONENT, .... This way it would not matter if DIALOG (or any other part of the path) is [1] or something else since it is identified by more attributes than a simple number. ... View more

Interact and associated forms should be able to be unlocked via another user. We have experienced forms being developed by a user remain perpetually locked by developers just like a BP process or object. ... View more

Currently in AWD 20.3 the max length of a manually created variable is limited to 75 characters.  Client has need where they enter up to a 750 character variable text that they need to be included in letter. Within Communications - Data Source Setup, created variable with field type of "textarea" but length cannot be set beyond 75 characters.  Has this been addressed in later release? On horizon?  If not then this is desired so larger text variables could be passed into Word during letter generation. ... 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

We would like the ability to read a barcode or QR code for the purpose of sorting and identification (i.e. envelopes) ... View more

Utility for Code Updates with Administrative Privileges.   Scenario: There is a requirement for a utility that can update parameters and data values for various objects, specifically utility objects. This can be achieved by providing inputs such as:   - Type: Process/Object - Page name or action name - Stage name > parameter name and its corresponding value - Parameter/data item name and its corresponding value, and so on.   Problem Statement: Frequently, the browsers used for 90% of automation processes undergo updates, which are beyond Blue Prism's control. These updates often lead to the disruption of automation processes. For instance, the default settings of Edge and Chrome browsers in version 117 disable Active Accessibility  rendering the command line parameters used in the application modeler or passed through the Navigate stage ineffective. In large-scale enterprise organizations where hundreds of automations are running concurrently, making code changes to each automation simultaneously becomes a nearly impossible task.   This situation highlights the need for Blue Prism to develop a solution that addresses such scenarios, providing a competitive edge in the automation platform industry. If Blue Prism were to offer a feature allowing inputs like process name, object name, parameter name, and its value to be supplied, this capability could be executed by platform administrators or individuals with administrative rights. They would be able to directly make changes in a production environment, efficiently managing automation processes in response to browser updates and other similar challenges. ... 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

We would like to have the ability to mask few characters of a field in UXBuilder. Like Bank account numbers for example, we would like to show only last 4 characters on the screen and mask the rest. ... View more

We would like to have the ability to set relative default dates in UXBuilder date picker element similar to what we have in classic forms currently. For example, we use NOW-1Y in Default attribute of Date element in Classic forms to set the date to current date - 1 year. ... View more

The ability to reload a object or process after making changes to another or a web api that is connected inside it would save so much time. ... View more

Need the ability to automatically split documents in addition to the current manual feature. With Documentation Automation integration, it seems like this should be possible. Right now, DA charges for every page submitted. sometimes a document will always have pages that are not templated, so they reject consistently, even when they always accompany other pages that are templated. See attached - this shows a current solution that uses Abbyy ... View more

One of our client, who is a dedicated user of Blue Prism Interact for multiple processes, has voiced a valuable suggestion for an enhancement. They express the need to include URLs as a column type in the Table Field directly, allowing for seamless navigation without the need to copy and paste into a separate browser. Currently, URLs can only be added as text, requiring additional steps to access them. Implementing this feature would greatly enhance the automation experience for our client and add substantial value to the platform. I kindly request the consideration of this enhancement for inclusion in upcoming versions of Blue Prism Interact. ... View more

Currently if you send a Composition by email and the address is incorrect, the email will move to Error Status.  The client would like the ability to "Cancel" the email (would prefer to change email address and resend, different request) and move it to the Cancel Status so that it is apparent the item was reviewed and error caught. ... 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

Currently, we can only use images with URLs in UXbuilder. It would be good if we can have the ability to upload images from local machine or to be able to use base64 encoding of the image. ... View more

The table operations options in UX builder need extending so that the add, edit and delete can all be chosen independently. Particularly, the need to edit and add without the option to delete is going to be a common requirement for customers. ... View more