Showing ideas with status New.
Show all ideas
If other schedules are already scheduled for the same resource on the same day and time, please issue a warning when creating the schedule. I am having trouble because both schedules set to start at the same time for the same resource are not working.
... View more
I am not sure if such feature is available in BP v7 at least I am not aware of it.
The idea is to have a tool that supports the replacement of VBO and sub-process in depending objects. Since the underlying XML is well defined and known it should be possible to create a program, script, VBO that list all objects used by a specific VBO/process and then allows to specify with what this should be replaced.
In theory this replacement could be done directly in DB but might be safer to extract the XML and do the replacement on the file and import it again. (export/import could be done manually). This exp-/import the replacement would be visible in the change history too.
Alternatively it would be helpful to publish the XML definitions so customers could do such a tool themselves.
... View more
Many VBOs appear to be unnecessarily set to a run mode of "exclusive". If any of these VBOs are used in a process or object that is exposed as an API, we will be limited to a single instance at any given time on that resource. In order for us to advance our callable process/object capabilities, we need the flexibility to run multiple instances on a single machine. The following is a list of VBOs that have an "Exclusive" run mode:
Email - POP3/SMTP
MS Excel VBO
MS Excel VBO - Extended
MS Outlook Email VBO
MS Outlook Email VBO 6.10.4
MS Word VBO
System - Active Directory
Utility - Encryption
Utility - HTTP
Utility - JSON
Utility - Numeric Operations
Utility - Network
Utility - Screen Capture
Webservices - OAuth2.0
Webservices - REST
I think the MS VBOs could at least be reduced to "Foreground" run mode(as they might temporarily require exclusive use of those applications), but all of the others should be changed to "Background" as there is no discernable reason that multiple instances couldn't be running at the same time. If we need to make them more exclusive, that should be our choice in our local environments, but there's no need to be so restrictive as a platform default setting.
... View more
The usability of the scheduler entry will be more appropriate if we are able to change the order of the tasks
... View more
Right now, When adding DLLs to an object, you can either set your relative path to the dll and it will look for the file in the Blue Prism install folder, or you can specify a full path to a file. I would find it useful to be able to set a path in the database as a second place for Blue Prism to find these dlls and not require to place dlls directly into Blue Prism install directory. This will help keeping blue Prism install directory clean and easy to manage over time. Also it will not require enterprise environments to repackage and update a new version of Blue Prism to be sent out for every dll to be added for object usage..
... View more
Status:
New
Submitted on
08-05-24
06:58 PM
Submitted by
Vinodh__Kannan__Krishnan
on
08-05-24
06:58 PM
Blue Prism as a RPA tool has been around for more than 10 years now. We have many RPA enterprise instances that have BP code written by 3rd party vendors, federated units as well as erstwhile employees. Not all of the code components are properly annotated or written following best practices, this makes understanding, maintenance and enhancement of these automations a very difficult task. Since Blue Prism/SS&C has been investing in GenAI research it would be great if we can have a tool that can ingest Blue Prism code [as .bprelease file] and provide an interface to the users. This GenAI tool with a chat interface can provide detailed code docs as well as decipherable insights into the BP Processes. This will reduce maintenance & enhancement efforts and will increase investments into RPA. Blue Prism Enterprise v7 Next Generation
... View more
Sometimes we need to manually run a process in control room and usually more than once (most of the times because of forgot something). Please create an option, when we right click on a previous run to "rerun" it again. By rerun I mean to start a new instance of the same process on the same resource.
This would make this process much simpler, mostly during the Testing phase where we might need to run the same process many times.
... View more
While creating a new schedule ,the tool should show possible conflicts between two schedules , if they both share same resources and kickoff timings . Something which we see in ServiceNow if two CR are scheduled at the same time and for the same application
... View more
Currently, when a User clicks Get Work and the work item goes to their Worklist, no row is inserted into the View History to document that the work item was received by the User. If the User updates the work item such as changing the status, then a row is inserted. The problem is that View History does not show an accurate history of who has had the work item if no update was done. However, in the WA5 table, there is a row with the EVENT_CODE = BIWRKSEL.
... View more
Problem: Per the Blue Prism documentation, Auto Archiving "causes a registered, running resource to check periodically throughout the day for any session logs that ended before a specified date/time and archive/delete them if such are found". My team has found that when very large sessions logs are being archived, it taxes our database and negatively impacts the performance of our automated sessions actively trying to run. The stress on the database can be so large that it seizes our servers and even takes down the entire environment. As a workaround, we identify large session logs and manually archive them before the auto archiving process gets to them. This is tedious and not ideal. Solution Idea: Alternatively, it would be great if Blue Prism added a way to configure Auto Archiving so it only runs during specified hours instead of checking "periodically throughout the day". If this were an option, we would set our archiving to happen outside of business hours so our database would not get so stressed.
... View more
This would help reduce the number of Environment Variables and help collapse / consolidate numerous environment variables into one single Environment Variable name which makes management / use of these a lot easier/efficient.
... View more
With resource pools, it is not possible to execute all tasks of a scheduler on the same resource. Example: We have 3 resources in a resource pool (VM1, VM2, VM3). When I create a scheduler, I always have 3 tasks (I am sure this is the case for many customers):
- Windows login - process - Windows logout
If I now run a scheduler on the resource pool, the following happens: The login process logs into VM1. The actual process is trying to run on VM2. The logout process tries to log out on VM3.
We want all tasks from a scheduler to run on the same resource in the resource pool. This is important because of security reasons. We have set it up in such a way that each process has its own Windows user, which has limited access rights to directories etc.
... View more
The "Mark Exception" action automatically creates a tag if the Exception Reason is not empty. The automatically generated tag has the format: "Exception: {Exception Reason}".
The exception reason often contains case-specific data. E.g., "product 523462 could not be found.". Blue Prism then creates a tag from this exception reason, causing our BPATag table to grow indefinitely.
... 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
The ability to reload a object or process after making changes to another or a web api that is connected inside it would save so much time.
... 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
Isolation and portability: Docker containers provide a lightweight and isolated runtime environment for applications. Running Blue Prism in a Docker container allows you to encapsulate the application and its dependencies, making it easier to manage and deploy across different environments.
Reproducible environments: Docker containers allow you to create consistent and reproducible environments for running Blue Prism. By packaging the application and its dependencies into a Docker image, you can ensure that the exact same environment is used during development, testing, and production.
Scalability and resource utilization: Docker containers provide efficient resource utilization and scalability. You can run multiple Blue Prism containers simultaneously, allowing for parallel execution of processes and optimizing resource allocation. Containers can be easily scaled up or down based on the workload, ensuring optimal utilization of computing resources.
Version control and rollbacks: Docker enables version control of container images. Each image can be tagged and versioned, making it easier to manage different versions of Blue Prism. This facilitates easy rollbacks to previous versions in case of issues or the need to revert to a stable state.
Simplified deployment and updates: Docker simplifies the deployment process for Blue Prism. With a Docker image, you can easily distribute the application to different environments, minimizing the manual setup and configuration steps.
Resource optimization: Docker allows for efficient resource allocation by running multiple containers on a single host machine. This reduces hardware costs and optimizes resource utilization.
Collaboration and development efficiency: Docker containers provide a consistent and reproducible environment, making it easier for teams to collaborate on developing Blue Prism processes. Developers can share containerized development environments, ensuring that everyone is working in the same setup. This streamlines the development and testing process, leading to increased efficiency and productivity.We are looking seek guidance from their support or community forums for best practices and specific instructions on running Blue Prism in Docker containers.
... View more
As we're iterating through a collection, there are a number of cases where we want to make updates to the input data. When these data sets are in the thousands of rows, it's typically better on memory usage to use the same Collection in the input and output tabs.
One of the .NET quirks of this dataset, is that making these sorts of changes will set the current row to 1 each time. So if you use a Collection within a Loop stage and make changes to the Collection within that same Loop, you'll end up creating an infinite loop because it will never reach the last row. It would be useful to have an action in the Internal Object for Collections to set DataGrid.CurrentRowIndex or something equivalent in order to prevent these infinite loop scenarios.
... View more
As Operator I would like to have a column "locked" in addition to "Worked, Pending and Deferred" when viewing the list of queues, making it easier to see if a process is stuck at any point in time as one could compare the prev. no. of worked against the no. of locks in the queue...
... View more