Provide the option to have the Break On Exceptions setting turned ON by default.  I always turn this on when debugging. Always. It's such a useful feature and it irks me that I can't just have this on be default all the time. Instead, every time I start work in a process I have to remember to go turn it on. Then when I step into an object I have to remember to turn it on there as well. On the odd occasion I do forget to turn it on the "runaway" behaviour and consequences to your session can be hugely frustrating and waste a great deal of time having to reset. Simple request: allow for Break On Exceptions to be on by default and save the time and sanity of many a developer 🙂 ... View more

Today, Every time a new Process or Object is imported into the Environment via AutomateC is automatically added to the Default Folder and does not maintain the Source Directory Structure. However, this is retained when importing via a .bprelease file. This is due to the <process-group> and <object-group> tags present in the bprelease file. Including this in the process/object xml will allow Users to import into an established folder structure. ... View more

Currently, the import switch in AutomateC does not put in an Edit Summary while importing into an Environment. The option to put in this customized text will allow users to manage command line imports much more effectively. ... View more

Additional options when creating a rule would be very helpful and reduce the volume of rules required for a form. My highest priority would be to have AND / OR settings (for example, field2 state is mandatory if field1 has a value of 'A', 'B' or 'C'). A While option would also be very useful as this would prevent the need to create 2+ rules in case a user changes something on the form (for example, field2 state is hidden while field1 = 'no'). Other suggestions include rules based on more than one field and any other basic functions. We currently have a very simple form which usually displays 7 fields on 1 page which uses 130 rules, the above changes would reduce that to under 10 rules. ... View more

The last screen for confirming DB upgrade during BP upgrade should show the DB name that will be affected. Currently it warns in red: those changes cannot be undone! and I have to enter the password again ... but I cannot verify if my previous specifications of the DB was correct anymore at this stage. There could be another line close to the lines with the DB versions saying: Affected database: <db name>. Or it could be added to the password prompt like: Please retype the password for database <db name>. ... View more

It would be a great support to developers or support teams if any of the session can be restarted by clicking on previously completed or terminated session. given the machine is available. ... View more

We tend to lose a lot of work when locks are released accidentally from all the locked process and business objects. This needs to be further improvised in the upcoming feature where admin (or superuser) can only release locks if required from all the process and objects. Developers would have restricted access to unlock either the process and objects that they have created or only one at a time.  ... View more

When viewing the processes running in the control room in the Management session, in the Environment panel when we want to see the Session variables of the running process to update the value of the variable, it would be very useful and fast if it allowed the option double-click on the variable and it will be enabled for value update. ... View more

Currently when items are loaded to work queue, the Created and Last Updated column in queue content is being populated by datetime. When any of the items have been marked as exception and retried, datetime in Created column remains unchanged and when the same item gets completed, the Last Updated column is updated and the difference between these two columns does not match the Total Work Time column. Would like to have new datetime in the Created column when item is retried so that when it gets completed, the Last Update column will be updated and there will be no difference in both columns when it comes to match the Total Work time column. OR Can have an one column which will be populating the retried items date item. ... View more

Add option to set breakpoint on all Exception & Recover stages. This option can really come in handy when the user wants to set a breakpoint on all Exceptions/Recover stages. So if it fails anywhere it will stop there. ... View more

We have the option to delete worked items from the Blue prism control room. When clicked it does not ask for confirmation and due to this many times, I tend to delete items while doing force retry. Can we add a pop-up window asking for confirmation to delete selected items from the work queue? Even we can add this checkbox in settings to have this confirmation window activate or not. ... View more

Hello, it would be cool during spying an element with the application modeller to have the screenshot of the spyed obejct in the final object. Like after spying is done and the object is done that when i open the action in the object that on the right side i see the screenshot of the  spyed element.   Benefit: error finding is much easier  Current Situation: you have getting an error then you have to start the part of the process and then you have to start the application modeller and use the function higlight so see what got spyed. On the other site you also have to open the process documentation to see if the right element got spyed or maybe the applcaition changed.  ... View more

There is a serious bug using a code stage: Pass in a collection containing not initialized fields (e.g. number or flag values) into a code stage. All values will be converted to their .NET defaults e.g. a not-filled number becomes '0' and a not-filled flag becomes 'False'. The reverse transfer (out of the code stage) works properly. Set a DataTable field to DBNull, the value appears as not-filled in BluePrism! This functionality is needed in case of serialisation/deserialisation to/from external data (e.g. XML or JSON format). To keep a possible solution backward compatible: Consider of a code stage option e.g. "keep null value(s)" ... View more

At the moment the Tenant function is based on the user roles only and the administration of tenants in BluePrism is very time intensive.  It would be great to have an setting like create tenant. This tenant is totaly empty like no objects no processes. The admin of Blueprism should add via Tenant Option like the Roles and Users.  On the start option of BluePrism then you should have the Possibilty to choose the connection and a second option choose tenant. The admin see for sure here all tenants but the end user here see only the tenant they have rights for. This would help in different team enviorments. ... 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

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

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

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