The scheduler should be improved to make better use of the availability of execution machines, in particular with resource pools. Due of the current scheduler limitations, any given schedule on a resource pool needs to be updated as soon the number of machines belonging to this pool changes. To illustrate how the current scheduler is limited, here is an example with a pool of 3 resources and 5 target sessions to run in parallel (session 1 to session 5 below). Task 1 - Login - Login - Login Task 2 - Robot start notification Task 3 - Clean resource - Clean resource - Clean resource Task 4 - Session 1 - Session 2 - Session 3 Task 5 - Session 4 - Session 5 Task 6 - Robot end notification Task 7 - Logout - Logout - Logout With more or less resources, all the tasks except the 2 about the robot notification start and end need to be updated. A smarter scheduler would specify this: Task 1 - apply session to all available resources - Login Task 2  - Robot start notification Task 3 - apply session to all available resources - Clean execution machine Task 4 - execute session as soon as an execution machine of the pool is available - Session 1 - Session 2 - Session 3 - Session 4 - Session 5 Task 5 - Robot end notification Task 6 - apply session to all available resources - Logout This means that the smart scheduler has two options for setting up a task. First option: it is possible to indicate that the task session must apply to ALL available machines in the resource pool. In the absence of this option, the session must be artificially duplicated in as many copies as the number of machines in the resource pool, which forces the task to be modified as soon as this number changes. Second option: it is possible to run the sessions of a task as and when the machines in the resource pool become available. This is also valid if the task is assigned to a single machine. In the absence of this option, two possibilities: 1) Splitting the target task into artificial tasks (like the first example), each of which includes a maximum number of sessions identical to the number of machines in the resource pool. ==> Very bad solution because if machines are not available, sessions are lost, and if all machines are available, the next artificial task will start only at the end of the session taking the longest time, in other words , machines are unoccupied when they could have been used for executions. 2) Use of a master process, which reads a dedicated queue, each item of which corresponds to a target session. The target session process is executed as a subprocess by the master process. Instead of running the target sessions, we run this master process on all the machines in the resource pool. ==> Better solution, but which requires having to modify the master process whenever you want to change the target sessions. And this solution poses a problem because the Blue Prism logs no longer make it possible to individualize the target sessions. ... View more

Hello Team, I've feedback for BPU and PDF guides. There are many courses on BPU that just shows slides of the PDF guide (e.g. BPC courses) A course should be video material with dynamic components, voice-overs, graphics, and charts to explain the tool and concept easily. Just having PDF guides broken into chapters and having it as a course does not sound to me like a good idea.  If it is just a PDF/Slideshow for a user to read then he/she can simply read the PDF guide outside of BPU. We have many interactive video courses as well e.g Decipher Training, Blue Prism Foundation Training, etc. on BPU which are great. My point here is we should have a clear delineation between video courses and PDF guides and it should not be mixed up on BPU. All SCORM video courses should be on BPU. All the PDF guides are on a separate portal. ... 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

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

The idea is to have a Data Item exposure such that we can store and update that variable across sessions - its more like an environment variable but to which we can make updates too. This will help us in storing variables across sessions like flags, data which requires the value from the other session run that currently has to be stored in externally like in excel, notepads, etc. ... View more

Unretiring a schedule as per current model requires create Schedule permission. in our scenario , we have separate teams for management and operations . So it is better to have a separate unretire schedule permission where operations can just retire or unretire based on business needs without updating the schedule. Thanks. ... View more

some findings on how task order is defined by BP can be found in my comment below In BP client Control tab, Schedules are ordered by their names and tasks according to their creation. Schedules can be arranged by structured names. The order of Tasks is defined by when they have been created that makes organizing Schedules unnecessary difficult over time. eg: Schedule: (numbers show the logical order) - Login (1.) - Process (2.) - Logout (3.) Now when adding a second process to be executed after the existing one it would look like: Schedule: - Login (1.) - Process (2.) - Logout (4.) - Process2 (3.) It would be better to order the Tasks by their names so order can be easily amended as needed by prefixes in their names. ... View more

Capture Creates a lot of value for creation of new PDDs and Digital workers, but how about the already delivered solution? Running a large-scale (now 5 Y old) CoE come with some documentational challenges. What if there was a "plugin" which was activated to create a PDD. Using a combination of the BP process logic and screenshots and magically created "PDD" like output. Which could be used to actually see what the robot is doing - all to avoid the problem of outdated PDD.  ... View more

As we find it in the studio, a filter in the control room is very important and urgent to be implemented. We lost a lot of time for any intervention in the control room il there is a lot of bots implemented. It's very surprising that such functionality isn't present yet ... View more

We have different Business Areas who like their users to get different amount of work while they use get work (work select). Currently this is a global setting. We like to have the ability to set the count per work group or Business Area/WorkType. Another setting is release on log off that would be helpful to follow similar path. ... View more

Audit is becoming more of a challenge all the time and they are asking for detailed logs for every thing we do. One of our biggest problems is setting up of user ids and removing of access. We like to use the clone tool to grant and remove access by cloning against preformated "profile ids" . This saves us huge amounts of time in setting up access, anywhere from 10-15 min per id. The issue is there does not appear to be audit tracing on what is added and removed when the Clone ID is used. We would like to request improved logging to show what accesses (roles, security groups, User privileges get added and removed during the cloning of Id process) thank you ... View more

Use Case:  We have automations against the Epic EHR application.  They claim to NEVER have any downtimes, but they often had "silent pauses", or somesuch, which seem to be just as disruptive to our processes. Idea: Have a 'Pause' option, alongside the 'Request Stop' option.  The 'Pause' option would have a start and stop DateTime parameter.  When executed, the Process, upon reaching the Stop/Stop Time check would hold until the Pause parameters expired.  The exact mechanics in the Process could be addressed in a couple of different ways. So, rather than a full Stop/Restart, the Process is able to pick back up where it left off. ... View more

There are already ideas for centrally managing licenses. Additionally it would be nice to have one central management view on all RR regardless to what environment they are connected.  Another idea, related to the one above, is to have the possibility to change configuration of the RR. This might be connection definitions and LoginService configuration.  If one central control room for all RR in all environments is not feasible in near future, it would be still nice to be able to configure RR at least central within one environment. ... View more

Currently (at least for v6.9) a BP environment is basically identified by the connection name. The connection name is a free text that can be changed anytime.  When working with multiple teams in multiple environments it is important to exactly know what environment we are working in and talking about.  Avoiding ambiguous names like 'My BP 123', 'old/new BP', ... might be avoided to some degree with naming conventions and using scripts instead of manual configuration.  But still, changing the name of the connection or keeping the name but changing port, can lead to confusion. It would be nice to have the possibility to specify a name to identify a BP instance / environment and that is stored in the DB. This can the be displayed in the client. This name could also be added during archiving and reduces the risk of corrupting the target archiving structure.  ... View more

Currently, Chorus Document Automation is administered via a stand-alone website.  I would like to see this website become a Chorus Workspace that is accessed using the same user ID/password as Chorus BPM. ... View more

​ I would like to have a menu setting that can be used to disable/enable the 'Don't log parameters on this stage' option for the selected stages/all stages - similar to the options for the log levels. ... View more

Currently the only way to access Doc Splitter is to use the Action Menu option. As it is often part of the flow within a process, it would be ideal to have the same feature available as a button on the form of a work item ... View more

Currently the maximum limit of tabs (i.e. documents that can be opened inside the CV) is set to 15.  The initial thought was to optimize the performance when processing attachments in runtime prior to us introducing the node clustering feature in HTML CV 1.4.1 to support higher volume of transactions. We currently do not have an option to change the max no. of attachments that can be opened.  Comment from PS team:- Document Splitter (based on the same Snowbound Virtual Viewer code) does allow the number of tabs to be varied. This was at the explicit request of Lincoln Financial, who partially funded that effort. BUT, IMO many more than 15 tabs quickly becomes unmanageable from a user perspective. I believe that the count of "15" was directly ported from the desktop CV code. ... View more

After maximization i would like that the columns are automatical adjust to the screensize ... View more