When we run process from process studio and if there is any exception then it will bubble up to main page recovery (assume - no handling on subpages). There is option to find which stage given exception but if you restart from that step then process will again throw exception on END stage of sub-page. it should continue with flow before exception. ... View more

I would like to have a new action stage, to be shown in the stage choice panel on the left side in Studio. You can call it whatever you like, but I'd like the new stage to be definable by the developer. For the fun of it, we could call it a Tiny Template. The new 'Tiny Template' stage would contain a stage, or a block of stages that are regularly used by the developer. Choosing the new stage would imply that the block of stages will be dragged into the page the developer is currently working on, in the same manner as the single stages that we have today.  The new customizable 'Tiny Template' stage can be defined once by the developer and will remain accessible within BP Studio until its definition is changed by the developer. The 'Tiny Template' definition will be saved so it can be used again at any later time Studio is used. Why would this be practical? Lemme give y'all an example: When I'm testing new or modified parts of a process or object, stuff tends to crash. This is ok as it indicates where efforts for error handling are required. In order not to let any of these small crashes lead me back to to the Main Page, or wherever it bubbles up to, I usually add a temporary recover-resume-note block on the page. This will catch any errors and remain on the page I'm working on. When I move my work to the next page, I move or copy the block along with me to the net page. When all is done, I remove the blocks as not to permanently disturb the process flow. In the example above, I'd define my 'Tiny Template' as a recover-resume-note block and deploy it in every page I need it. Happy coding! ---------------- Paul Sweden ... View more

We would like to be able to freeze a group on a form like you can freeze panes in Excel so agents don't have to scroll up and down to see important information. ... View more

Currently, we can change the logging for all stages in a process by choosing one of the three options, disabled, enabled or errors only.  It would be great if we can have one more option which is changing all log according to best practices and recommendations. This option can be disabling what needs to be disabled, setting errors only for what needs to be that way and leaving all decision and choice stages enabled.  Simply an option that  can be used before releasing to production as usually a lot of things enabled while developing which makes the currently available 3 options important but they still require manual work to change the logging for specific stages.  In a big process this can be a problem since not noticing some stages can be possible. ... View more

Automatically Show LOB Fields Using View Data in Processor Workspace in Alphabetical Order The vast majority of times that we bring up View Data in Processor Workspace in Chorus BPM we toggle to view the LOB fields in alphabetical order.  Can this please be made the default in a future version? ... View more

We can now archive individual UX Builder Project versions.  Can we please add the ability to deprecate/archive entire Projects? ... View more

I'd like if the Object Conversion Utility (OCU) could be a Chorus Workspace, so I wouldn't have to log onto it separately from Chorus BPM.  Thanks! ... View more

I love that Chorus BPM 22.2 includes the ability to deprecate unused Presentation Flows, Automation Services, and Sampling Services.  Can this deprecate capability please be added for the Processes and UX Services? ... 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

Currently, to autoincrement a counter variable that adds +1 (typically) on every loop round, a separate calculation stage is needed plus a variable to hold a counter data. My suggestion is to integrate autoincrement function into a loop (checkbox to trigger the feature on/off per loop) in case autoincrement functionality is used a placeholder for a name of counter variable (datatype : number) button next the counter variable name to create a stage that holds counter variable a placeholder for a base value (typically 0 or 1) This is mostly a QoL enhancement. ... 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

Hi Team, How about adding a new feature in Blue Prism decipher to recognize stamp in a document. ... View more

When opening System / Archiving in manual mode, there is a time frame to be specified that limits the shown logs currently in DB. It would be nice to have the Start date being 'open' in order to query all history until End date. There might be some logs in 2019 and I would never know (or maybe in 2018? 2017? you get the point :)) ... View more

How about having a native end-to-end Chatbot solution in Blue Prism. Since Chatbots play an integral role now as the organization advances in terms of the latest technological advancement it becomes important to have a Chatbot functionality. ... View more

We're currently at BP6.5.4 and in the process of migrating to BP6.10.5. For this migration we get to verify all our processes in 6.10 prior to go live in 6.10. While doing so I cannot help but notice that some of the screens where in 6.5 an escape was handled as a Cancel, for the same form in 6.10, the escape is no longer Cancel and I have to divert from using the keyboard to using the mouse. While this may seem trivial to some, any change away from the mouse is welcome in my view. Specially if you're doing this full-time. Example:  Try the calculation stage properties and press escape - it will Cancel. Now press button 'Evaluate Expression' on the calculation stage properties and press escape - it will not Cancel in 6.10, but will Cancel in 6.5.  There are more screens that have similar changes in behavior.  In my view as a user of BP and as a software developer, similar forms should always have similar behavior. Any given property form should always behave as any other property form of similar type and function. I can add that the same goes for a screen that in 6.5 did not react to an Enter, but in 6.10, the Enter is interpreted as the Ok button. This I call progress, and I would like to see more of this. We're still at 6.10, but no doubt one day we will see the lights of BP7. I do hope that we by then are presented with a consistent way to blend mouse clicks and keyboard strikes each leading to the same and predictable result. Happy coding! --------------- Paul Sweden ... View more

A Command line switch for Immediate stop for the running session would be an added advantage for controllability ... View more

A Quality of Life suggestion. Take, for example, the humble 'Item Data' collection, after getting an item from the queue. There could be any number of fields in this collection that will be referred to constantly throughout the rest of the process. Each time you need to refer to one of them, you have to type [Item Data.Field Name], being very careful with your typing. It would be much simpler to instead co-opt the fields that are returned from the queue and have them going forward as pre-defined fields that you can click on via the expression editor. ... View more

We need the ability to add the communication user's email address to an outgoing email. It would be useful to add email address to the user set up, similar to phone number. The address would then be available in Data Sources under User Properties in design services. ... View more

We have run into an issue post upgrade to edge which does not allow us to read a table after spying only a column. Before you were able to just select a value and then could have the bot read the entire table. Trying to highlight the entire table properly and have it read it and save to a collection has been impossible with Oracle Reports. ... View more