It would be beneficial to have an option to export session details from Control Room, similar to the option available for exporting queue details. This would allow for easier tracking and analysis of session data. Therefore, it is recommended to add an export option for sessions in Control Room. To my understanding, currently, there does not seem to be a manual export option or an automated solution available to export all session management console details. This can potentially create a hindrance in efficiently managing and analyzing session data for business purposes. Therefore, it may be beneficial to explore options for implementing an export feature for the session management console. ... View more

The existing design control covers quite a lot in terms of usable syntax and logic errors but it is limited with best practice checking. There should be a base set of configurable best practice controls set up based on peer review documents. Example controls: Overcomplicated pages - Check for X number of stages. Stages that could be sub-pages - Check for duplicate named sequences of stages. Possible infinite loops - Check to ensure a decision stage exists between a set of links that go backwards. Attach stages at the beginning of actions - Check for an attach after a Start stage These are just some possible controls. Rules should be developed based on the existing peer review checklists on the portal. Organisations should have some flexibility in modifying the controls and increasing/decreasing thresholds based on their own needs. ... View more

User Work Group hierarchy shown visually would also be helpful ... View more

Actually looking for a more effective way in searching for objects together with its actions. Ideally we can filter for the object name in the studio then have to open it manually and look at all the actions. Another way is maybe keep a tracker of all objects via Excel or SharePoint. Is there an existing solution to this? ... View more

Work ownership for the BusinessArea – WorkType- Queue combination would be helpful, so this can be updated and also made available via Analytics ... View more

We (and our Risk team) would like an audit trail to report on AWD process flow changes. We need to know who made an update, when, and what was changed. ... View more

Hi Team, Blueprism provides a very good write stage which works most of the case and the best thing it works in backend. But there are lot of modern application where write stage is not working properly. Even though we write it is not writing in the text box. As alternative we are using globalsendkeys. It would be great if Blueprism provides a type into stage by using the same we can directly write into any text box instead of using globalsendkeys. ... View more

Currently the "Create Source" function offered by the Utility task in Design Studio only allows for a source to be created from a Content ID - so effectively can only be used in a Capture process where the Content ID is already known and the content is already present in the image store. For the main "Create Source" use case, where the *content* is already known, but the ID isn't, the "createObjects" operation on the AWD Processing Service SOAP web service must be used, so: The call goes out of the container and back in through the web server, creating a new execution thread in the process, rather than being a simple inline call from the Service Engine As a separate execution thread, that update is in a separate database transaction, so won't roll back if an error down the line in the current process triggers a transaction rollback ... View more

Hi,  currently there is the only option for warning when robot gets stuck at an action for longer time than is certain number of minutes - it is displayed in Control Room. It would be very useful to have more options here. I can think of: sending an email or sms Restarting the process Terminating the current process It would be particularly useful when running overnight processes so that in the morning the robot is not blocked by hanging process. ... View more

Especially when dealing with browser automations, various lags and errors lead to rather messy Process level design. To counter surprising attach or timeout issues, Process level flowchart tend to be filled with actions surrounded with blocks, resume/recover stages and retry loop structures. (Yes, you could clean the process by submerging retry logic into object level, but in the end, it's a same mess, but under a different carpet.) My suggestion is to add a Try-Catch tool into a Process Studio toolbox. Idea is to place an action inside of Try-Catch area and handle exceptions the action might cause. Visually it mimics a Block tool, but adds to its design properties: number of retries action within a Try-Catch will be retried (or possibly a timeout after x seconds?) two exit nodes, one for positive and one negative end (means despite of retries, object faced an error) - error node could be a Recover stage and it's up to a developer if the error is rethrown or suppressed by resume to visualize which retry round is going on, add a caption to stage that signals the retry round for developer The trickiest part is to create a nice design for a error node, but I hope you'll get the idea! ... View more

When object name is changed then in all processes where this object was used it no longer exists in the actions and it should be again added for all the missing actions. It could be the same as for process - when the name is changed it still exists in other processes where it is used as it is referenced by ID I guess. ... View more

Idea:   I'd like to suggest the customization / expansion of the code-linting (aka Design Controls in design studio) capabilities that design studio currently has by allowing users to create and add their own rules.   An organization should be able to customize design controls that fit their own organization's best practices (eg. verify that spied elements follow a specific naming convention) and code styles (eg. all START stages have to be font color = green) background:   Most modern IDEs (eg. vscode or vs) have the capabilities to allow developers to create custom code-linting rules that fit their organization's best practice and coding styles.  These rules help standardize code within an organization which can lead to improved code maintainability, improved performance, and minimize bottlenecks development (eg. code reviews). other information:  Currently, it is possible to export Design Control settings to an XML file and share it with anyone.  So, it should make it possible for organizations to share their best practices with anyone, allowing new developers to benefit from the knowledge of more experienced developers.  Essentially, making it possible for new organizations adopting Blue Prism to copy design controls from experienced organizations who have been using Blue Prism for years. ... View more

For out-of-the-box functionality there should be no excuse for missing descriptions. The Work Queues:Set Data action (image below) is a perfect example.  This is a highly useful function but even if you've been using BP for a while, who knows what it does? Frankly, it is lazy product development not to have descriptions for standard functions when the facility to display descriptions is right there. Importantly, they should be useful - not just the obvious "This action sets data in a queue" but detail of how you do it, so someone developing their skills can understand.  For example "On Get Next Item this action writes the data in the output Queue Data Collection back to the queue..." or whatever. Perhaps you provide a facility to crowd source the descriptions and have a panel choose the best? ... View more

Instead of UI based installation, if we can install BluePrism via PowerShell commands with valid parameters, it would be helpful for IT team to schedule the automated installation for newly onboard person to team or during the version migration. For the larger scale team it will be very useful. ... View more

Hi Team it's very difficult to resize choice stage when there are more than 10 conditions. Once we make any changes then it's again resizing or rearranging th branches of choice stage. It's a pain to resize everything. Blue prism should remember the previous saves or there should be an option to remember or not. PFA for the same ... View more

We can add a new stage named like Dialogue box or something which will pop up a window and ask the user to enter the value of a specific data item. Such a stage can come in handy for attended automation where the user is expected to enter some value during the run time. ... View more

We are looking for something in our beta region that shows the user is logging into beta instead of production. Per Product team: There is some upcoming new work regarding a Unified Login Screen where this visibility might be incorporated. ... View more

Add the ability to report when a graphical interface element is not found. When Blue Prism doesn't find an element, it should return the element that is closest match to the specification of the target element, giving a percentage similarity. ... View more

​Would be nice if the first mode that opens would be the last one you used.  If you're spying 20 SAP fields with SAP mode, currently you have to type through to "SAP mode" 20 times ... View more