When using Chorus we want to label the new UI screens like Design with a label to indicate that we are in a test environment and which environment level. Something like "21.2 UAT" in a bold color so that it stands out. This is for safety so that users will not accidently enter Prod data into test or test data into Prod. ... View more

Ability to read the images dynamically into the image type data item would help in reading data from dynamic image paths. Currently a single hard coded image can be used. ... View more

In the add to queue action where you place a collection into the work queue there could be a flag option to write only those that dont already exist in the queue. At the moment we need to check each row if it exists in the queue already and if so then remove it and with a few thousand rows this takes a while. If the option existing in the Add to queue action it could add and check simultaneously removing the need for a time consuming loop. ... View more

Hi Team, We are currently using 6.8.1 version of BP and in the process of upgrading to 7.2. Most of our current processes in production using "Microsoft Excel 6.4 Version VBO" and we had to bring that version even after our upgrade because some of the actions such as " Open workbook with timeout", "Save workbook with timeout" etc are not available in default excel VBO's for newer version. Only option we had is to bring 6.4V VBO to the upgraded version or download and import the "MS Excel 10.1.7 VBO" which is available on portal.  It would be great if we can have all the functionalities/actions in single/Master VBO so we don't have to worry about missing items and that will avoid having multiple VBO for excel. ... View more

We have a lot of requests in Interact and our back office aren't working fast enough. And now they are always picking the newest Interact Inbox. We have tried to make them click on ID to take the oldest first. But they forget after some weeks. And now we have requests that never go through. An Inbox that remembers what the last user did will really help our customers to receive faster human-in-the-loop answers. ... View more

In the current specification, even if the following operations are performed from the process through the Interact Remote API, it is not displayed in the notification on Interact.   edit submission field value move submission to any tab   For example, even if the processing result of the process is reflected in the Interact form, the notification will not be displayed and the user will not be able to recognize it. So it is necessary to send notifications from the process via a different route than Interact, such as e-mail. In this case, interaction between users and processes cannot be completed only with Interact.   If it is possible to display a notification even when the above operation is performed, or if it is possible to display an arbitrary notification at an arbitrary timing from the process through the Interact Remote API, I think "mutual cooperation between users and digital workers" will be more enhanced and be easier to implement.   I would appreciate it if you could consider. ----------------------------- 現状の仕様では、プロセスからInteract Remote APIを通じて下記の操作を行っても、Interact上の通知には表示されない認識です。   ・フォームの内容を更新 ・フォームの格納フォルダを移動   例えばプロセスの処理結果をInteractフォームに反映しても、通知が表示されずユーザに認識してもらえないため、プロセスからメール等Interactとは別の経路で通知を送る必要があります。これではユーザ⇔プロセス間のやりとりをInteractのみで完結することができません。   上記の操作を行った場合も通知を表示する仕様とするか、もしくはプロセスからInteract Remote APIを通じて、任意のタイミングで任意の通知を表示させることができれば、「ユーザとデジタルワーカーの相互連携」がより実現しやすくなるのではないでしょうか。   ご検討をお願いします。 ... View more

Requirement: The Work and Source Report Some of scenarios need to filter on both work and source objects. Furthermore, on the reporting columns, the client also needs to show both work and source objects. Currently, we have the Work Reporting Object and the Source Reporting Object, but cannot combine them as a single report. ... View more

I would like to suggest the implementation of a built-in code scanning tool within Blue Prism. Currently, we face challenges in identifying bugs or vulnerabilities in our Blue Prism projects, as there is no dedicated code scanning tool available. While we attempted to integrate with SonarQube, it did not yield satisfactory results. The primary issue we encountered with SonarQube is its treatment of the .bprelease files as XML, which leads to inaccurate analysis results. The tool primarily focuses on detecting code smells, which are not applicable or relevant to our specific requirements. Therefore, I kindly request the development team to consider incorporating a native code scanning tool into Blue Prism which can scan code stages like C#, Visual Basic, JavaScript . This tool would be tailored to analyze Blue Prism's unique code structure and provide comprehensive feedback on potential bugs, vulnerabilities, and any other code-related issues specific to Blue Prism processes. By having a dedicated code scanning tool within Blue Prism, we can streamline our code review process, enhance the overall quality of our projects, and ensure compliance with security standards. This tool would greatly contribute to maintaining the integrity and reliability of Blue Prism solutions. Thank you for considering this suggestion, and I look forward to the possibility of a built-in code scanning tool being introduced in Blue Prism. ... View more

Chorus View Station allows you to perform multiple searches and place the results side by side for comparison.  Client would like Chorus Portal to work in the same manner.  This makes it quicker to identify and resolves items. ... View more

GraphQL-fronted web services are being increasingly seen in the wild as an HTTP-based alternative to standard RESTful services. To widen our OOTB API integration coverage, it would be very useful to have a GraphQL integration option direct out of Design Studio. ... View more

During a presentation of the ROM2, the importance of good process construction, proper testing and continuous service improvements was frequently highlighted without going into the detail of how this was achieved. Thus, when developing BluePrism processes, it is critical to invest in increasing process quality and an efficient testing process in terms of both cost and time investment. When it comes to process development, there are a number of important factors to consider. One of the most important factors is process quality. This refers to the extent to which the process meets the specified requirements and has the ability to function safely and reliably. Another important factor is process complexity. The more complex the process, the more chance of errors and problems and the more difficult to test. When complexity increases the possibility for introducing errors and the difficulty to test escalates. It is important to reduce implementation complexity by choosing simple workflows, using business logic and reducing redundant actions. A general rule adopted is that the more paths through a piece of code, the more complex it is. To my opinion, BluePrism implementations also have cyclomatic complexity that depend on the size and complexity of the processes, sub-processes and object actions and the amount of decision points in these components. A BluePrism implementation with high cyclomatic complexity can lead to problems such as poor performance, higher costs and errors. That is why It is important to reduce cyclomatic complexity to ensure the quality of the implementation. Several scientific papers have shown that there is a positive correlation between cyclomatic complexity and the probability of errors in software programs (e.g., Jones, 1986). Another study has shown that reduced cyclomatic complexity contributes to improved readability, maintainability and testability of software programs (e.g., McCabe, 1976). Cyclomatic complexity is a also an important factor in the quality of a BluePrism RPA implementation. Reducing complexity can prevent problems and ensure the quality of the implementation. Cyclomatic complexity could be an indicator of the quality of BluePrism process / object implementations. This indicator aims to measure and quantify the complexity of a process. The higher the cyclomatic complexity, the more difficult it is to understand and maintain the process. McCabe's Cyclomatic Complexity can also identify the points that generate the complexity. These points are also called "cyclomatic paths" and can be found by analyzing the graphical representation. Each decision point (decision stage, choice stage, loops, etc.) potentially generates a new cyclomatic path, increasing the complexity of the flow in the process and/or object. By identifying these cyclomatic paths, the flow can be optimized to reduce complexity and improve readability and maintainability. Some studies that can help in this regard are the following: "Cyclomatic Complexity and Software Maintenance" by Thomas J. McCabe - This 1976 article introduced cyclomatic complexity as a measure of software complexity. "An Empirical Study of the Relationship Between Cyclomatic Complexity and Software Maintenance" by Jaroslav Pokorný and Petr Baudiš - This 2014 article presents a study examining the relationship between cyclomatic complexity and software maintenance. "An Efficient Algorithm for Computing Cyclomatic Complexity of Programs in java" by Surya Narayan Sharma and Suresh Kumar - This 2017 article describes an efficient algorithm for computing the cyclomatic complexity of Java programs. In addition to cyclomatic complexity, there are other measurable factors that can affect the quality of BluePrism RPA implementations. Some important factors are: Duplication in processes and objects: When a piece of implementation is used in multiple places, it can lead to problems in maintaining and extending processes and/or objects. Duplication should therefore be minimized. Test coverage: To ensure that the BluePrism RPA implementation works properly, it is important to write tests that cover all functionality of the process/object flows. The more tests that are written, the better the quality of the implementation. Test coverage is the extent to which a test suite covers all possible paths in the process /object under test. A cyclomatic path is a sequence of steps through a process /object flow that touch each logical path or decision point in the program once. To determine test coverage based on the given test suite and cyclomatic paths, each path in the test suite must be analyzed to determine if it corresponds to a cyclomatic path. If a given cyclomatic path is not covered by the test suite, more test cases must be added to the suite to cover the path. Test coverage can then be calculated as the percentage of all possible cyclomatic paths in the program that are covered by the test suite. The ultimate goal is to achieve high test coverage so that there is sufficient assurance that the software program is functioning correctly and meeting customer expectations. So if we know the cyclomatic paths of a process/object, we can derive a desired dataset that maximizes test coverage. This dataset is often referred to as a "test suite." The purpose of a test suite is to ensure that each test performed contributes to testing a unique path in the flows. The process of deriving a test suite is quite cumbersome and can be done manually or automated. It involves going through each path in the flow and identifying the requirements for the inputs of each function and each condition to be considered. This requires in-depth knowledge of the flows in the process/object and the ability to identify "corner cases" that may lead to errors in the flows. In addition to manually deriving a test suite, tools can also be used to automate the testing process. These tools could take the cyclomatic complexity of the flow as input and generate the test cases that test each line and branch of the flow. This results in a test suite that comprehensively tests the flows and would provide maximum coverage. In short, knowing the cyclomatic paths of a process/object can lead to deriving a test suite that maximises test coverage. This can be done manually, but should also be possible with tools to automate the process. The purpose of a test suite is to ensure that each test performed contributes to testing a unique path in the flows, which is important to ensure software quality.  Readability: A good implementation is easy to understand, even for people who are not directly involved. Readability can be improved by using meaningful variable names and clear process/object formatting. Process testing does not stop at one test. It is important to conduct regular regression testing to ensure that any changes to the process and environment do not have unexpected side effects. Test suites with associated test data that ensure high coverage can be used to detect regressions in advance. This also helps to detect any errors and problems quickly and efficiently.  There is also the continuous service improvement component which is an important aspect of process development. This means that continuous improvements are made to increase efficiency and improve quality. This is achieved by constantly monitoring the performance of the process and addressing problems immediately. Efficiency is essential in process testing. Efficiency means using minimal time and resources to complete the testing process without compromising the quality of the tests. By having proper test suites, test coverage, regression testing and continuous improvement, you can ensure that the processes and objects are of high quality and tested efficiently. It is important to consider these factors when designing and implementing BluePrism processes and/or objects. Scientific articles that offer more information on these topics include "The Relationship Between Cyclomatic Complexity Metrics and Software Quality: A Controlled Experiment" by D.R. Kuhn and "Agile vs Traditional Methods: A Meta-Analysis of The State of The Art" by A. Subramanian et al. Perhaps a study topic for a graduate student to measure the quality of BluePrism processes and objects? ... View more

While debugging, if there is an option to export the current collection values to excel will help in analysing the collection data. Thanks! ... View more

Hi everyone. I`m sharing an idea to improve the dev experience in Blue Prism. Blue Prism isn`t available to see the params and inputs of the actions in Business Object/Process comparison. This functionality would be good to compare previous commits and restore versions that would need to restore. In the example below, I need to see the inputs of each actions to compare the previous version of the navigate. When I analising directly in the Object, It`s able to see the inputs values, as you can see in the attachment file: BP Version: V6.10.4   Regards Eduardo ... View more

It would be a great enhancement if we could have the ability to select the number of aborts we can release by data selection or amount. Right now you can only select all or one at the time and when we have some type of error that result in a lot of aborts it can cause the system to slow down.  ... View more

As for the SQL Server connector, a Snowflake connector to connect to, run a SQL script and return the result. With Snowflake becoming ubiquitous, this would be a highly useful object. ... View more

I would like to see an in-build feature in blueprism which will allow me to select 2 things while scheduling or triggering a process: Retry limit Defer time Basically when I run a process on a particular resource or resource pool and none of the resources are available then the process fails. Instead of failing it should consider the retry limit and try to run the process again on the same resource or resource pool after the defer time limit. It will allow the process to wait for some time and let the resource be free. ... View more

Integrate search into design  -  enhance design studio functionality and allow searches to be incorporated into design without having to  rely on SP and search forms being developed. Having flexibility to  incorporate in process search will reduce the time  and effort to complete design, ensure  that SP syntax is controlled and inline with standards.  Currently we are utilizing  in process search where base on criteria results are returned and displayed  to user to review and take necessary actions. Example of in process search are providing  users a quick view of other work in system that they will need to consider when working on current work item. - Account search -  search  for work pertaining to specific account - Outstanding work search -  search for outstanding work for specific team            - NIGO Bundling search – search for outstanding work for specific broker/ advisor – allowing associates who are performing callout to address multiple pieces of work in one reach out Thank you ... View more

1.Multi tenant environment -  allow for search across multiple business area.  When servicing multiple clients users often  perform search across multiple business area (e.g  searching for order requests pertaining to specific advisor across multiple business areas) Enabling this functionality will reduce the number of searches user will need to perform to retrieve the information they are looking for. As a result the number of requests submitted to the database will be reduces as well, overall  resulting  in better performance  2.Search criteria on card -   Add scroll bar to search criteria section.  For search forms that have multiple rows of fields  user is unable to navigate to all fields that are on the form 3.FVD(field value domain) - Enhance functionality to allow FVD values to be displayed on search forms  for AWD fields  (e.g. Worktype, Status, Queue) 4. Search Resource access control  -  Enhance functionality  to mimic behavior in classic workspace and allow management of resources that are showed on list of searches for user In instances where search resource is used in design process , user will need to have access to the resource to perform the search in design , however the resource does not need to be listed on search card under available searches for the user to manually run on demand.  ... View more

Worklist card filtering/ search  -  Enhance functionality for worklist card by adding filtering/search option and allow for dynamic  filtering/searching by multiple criteria (example -  user would be able to configure and  filter work list by Worktype /Account Number/ Broker /Queue) Similar logic could then be incorporated into Get Work  - were user would be able to define preference on what the next piece of work  they are getting should be (still within the constrains of what user is coded for).  Users often find it more productive to work on same type of work .  ... View more