Users would like to create a comment(s) and save it to my documents so it's readily available to add to the work object history as needed. The ability to do this would save time as the user would not have to retype the same comment over and over.  ... View more

Functionality(ALERTS) should be available for controlling/monitoring any abnormal activity encountered by Run Time Resources   Example: unable to login to Target application, unable to connect to virtual desktop infra, unable to perform any actions due to crashes of target application ... View more

It took us some time to understand the intention behind how Active Queue works and I think there are options for improvements that greatly enhance AQs. The ideas is to enable continuous processing triggered by new queue items and without occupying a runtime resource al the time while doing nothing. Short summary on how AQ currently work (please see documentation for general description): The assigned processes have to have a Poll loop that keeps the process active all the time even when there are no queue items available. This is necessary since the runtime resource is removed from the Target Resource definition when the process stops. Various AQ can share the same Resource Group and resources can be assigned by de-/increasing the number of Target Resources and AQ will take care of starting the correct processes. The ideas for improvements: Most important: AQ Target Resource definition does not decrement when a process stops working but stays as it was defined. This removes the need of the empty Poll loop but processes are started by AQ when needed. (And does not use a license for just polling and waiting) Nice to have: Adding thresholds for parallel processing. Something like 'active one resource for each x numbers of items'. Meaning, if x=100, one resource should be used if there are less than 100 items in the queue. If there are <200 two resources should be used and with <300 three resources asf. This will increase efficiency for low amount of processes and very quick processes. Instead of spawning the process, opening the applications, possible login, or navigating to the correct windows... the resources with all the technical basics already done can focus on business related steps. Nice to have: Assign Target Resources dynamically. This could be in combination with the parallel processing idea. Here the point is to set a min / max Target Resource value. min would set the number of resources being reserved for this AQ. Although there might no process running on this resource, it will not be used for other processes to ensure the queue will never be blocked completely. max sets the max number of concurrent processes of this queue running in parallel. Nice to have but tied to the prev point: Dynamic assignment of Resource Groups. The idea is to allow the total number of max Target Resources be greater than the actual available resources. With resources are made available again when there is nothing to process this setting would create an automatic dynamic assignment of resources for most efficiency. All resources not claimed by an AQ (Target Resource min setting) are moved to a common pool. AQ takes resources from this pool in peak times and returns them at off-peak times, making them available for other AQ. Nice to have but tied to the prev point: AQ prioritization. In times when several queues are processed and there are not enough resources to meet their max Target Resources demands, the AQ with the highest prio should create an event to a lower prio AQ to free a resources. This freed resource then can be claimed by the higher prio queue. The first point is the most important one that would enable a lot of customers the use of Active Queues. ... View more

Within Design Forms provide the ability to have a search box at the top where a user can start to type and the forms that start or have those letters in will start to appear below the search field.   ... View more

The idea is to develop the BP Alerts function, alerts in their current form only show historical events from BP about failed schedule launches, terminations. It could, for example, show in real time such events  - a suspended session and alert about it,  to have a quicker response  - it could also show information about the termination of a process that has not been resumed - once resumed, this could disappear from the alert plug-in (and only appear in the alert history) - it could also show the unavailable machines that are scheduled to be activated in the schedule in order to be able to react earlier - which would help with the non-termination of such a schedule - could detect infinite loops in the log - could report unplanned problems during the start of scheduled schedules, such as not starting all the machines that were scheduled to be started,  - and other similar It would be nice to be able to set these and other functions according to your own preferences - that is to have the option to customise such a plug-in. In my opinion, this would be a added value for the BP as well as for the consumer  ... View more

Hello everybody ! When creating many environment variables inside the system tab, it becomes difficult to organize the variables and find them quickly. The idea would be to implement the same folder organization system that we found in the Studio within the space for creating environment variables. That way it would be much easier to organize the variables and find them quickly I hope I helped with this idea. Regards, Guilherme Morandini. ... View more

Currently, when Export and Print buttons are clicked, the outputs do not display work type.  Work type information is essential when reviewing individual processed work. Please add Work Type as a column to display in the output. ... View more

Can BluePrism come up with a functionality with regards to Adhoc debug mode so that developers don't have to face issues when they step through the process and into the Business Object and make changes. If we step back into the BO (after making changes) it opens in Adhoc Test mode and we are unable to make other changes. This is making it difficult to re-spy elements and edit pages in the BO. We have to reset the Process and step back through from the start in order to get the BO to open for us to make changes. ... View more

Chorus BPM can display visuals from 3 rd party tools through an iFrame. However, Chorus BPM does not currently support writing information into this iFrame. By enabling the ability to both read & write through iFrames, Chorus DA would reduce the need to break focus and toggle to alternative systems. For example, users could perform manual transcription into Chorus DA, update diagrams in LucidChart, or validate NLP/IDP results within a single pane of glass. ... View more

The group feature in the Design/Form tool is very faint/non-existent using the modern theme.  We use this group on forms to visually relate data points to improve the user experience.  We think it would be beneficial to be able to see the group (box) and make the lines around the box darker/viewable.   ... View more

Allow users to create a Communications letter at any time by launching a  presentation flow from the Action Menu of the parent work item. The letter created would attach with the existing work item. This is similar to EnCorr functionality. ... View more

Enhancement request for the Delivery form to be configurable by Chorus BPM Admin as a resource: 1. Source Type - value should allow for admin to predetermine the source type, not user input 2. Phonebook - ability to save public or private entry should be controlled access. User can be directed to have to enter values each and every time manually in order to mitigate from incorrect selection from their private phonebook ... View more

Is Item in Queue action in Work Queue object is case insensitive. It false positive the existence of a queue item even if it's not an identical match. (See Screenshot)  Accordingly, I suggest having a Match Case flag option for the developers to decide. The screenshot is for a MS graph api message id, which I am sure it is being used widely and will continue to be used even more. So it will be very helpful to have that option.  Additionally, it was suggested by @PvD_SE to have an action that gets all queue data. Which can also be useful not only in the previous case insensitive situation, but it will also be very useful to read item data instead of items ids as the are not valuable in most cases without reading the data of each item one by one. ​ ... View more

*** Added 30 day impact because of lack of a 24 hour work window for BATCH UserIDs.                            The CHORUS BPM 'User' Screen allows an 'In By' and 'Out By' time window.  The values can be set to '00:00:00' and '23:59:59' respectively; but is NOT 24 hour window. There are two holes, the second before midnight and the second after midnight.  The two seconds may not seem like much, but, if you are engaged in BATCH processing using REST Calls at midnight, incoming work will fail to be created or updated.  This is causing out-of-synch issues.  This impacts ALL versions of Chorus and AWD.   Customer Support informed me that In By and Out By are working as designed.  We now have REST services that stay true to time ranges and cannot process for 24 hours.    We need a 24 hour option for BATCH Users. This is impacting clients every day, data updates are lost.  Please help. There are two errors in LOG Files: User cannot logon this early User cannot logon this late ... 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