I see in Batch types there is a setting called Validation lists which allows to use Odbc to connect to database. In my case I want to use Excel file. I use following connection string:
Driver={Microsoft Excel Driver (*.xls, *.xlsx, *.xlsm, *.xlsb)};Dbq=C:\Users\JMarkowski\Desktop\test.xlsx;
When I test connection, it says it's successful, however when I go to document form definition I don't see there any data.
Can you please implement this functionality working with Excel in Decipher?
... View more
Modify Chorus Worklist tagline to display the Assigned to User ID and name or at least last name. Currently, the tagline has a round, orange person icon. When a user hovers over it, the "Assigned To: userid" displays. Most processors do not have other user IDs memorized and displaying a name would be more informative. Users are aware of the Standard Search - Assigned Work Search allows a look up by ID or name, but this is more clicks.
... View more
Status:
Planned-Later
Submitted on
17-11-23
08:56 AM
Submitted by
xie_surbiton
on
17-11-23
08:56 AM
As per the product roadmap, the UX Builder is to replace the Chorus form functionality, it would be nice to have a multi-select dropdown on the UX Builder, which could serve as an alternative to the current 'List Builder' on Chorus, except that it would save a lot of space on the screen by comparison. Please see attached for example.
... 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
Currently you place variables within content and the information is filled in through LOB fields or variables entered within the Presentation. The client would like to be prompted to complete certain variables (fields) once the letter is presented for view. Word Developer offers some ability but nothing forced or the ability for it interact so it takes you to the next spot for entry.
... View more
Option to read/write fields of a collection with dynamic field names i.e; [CollectionName.[FieldName]] where field name can be changed using calc stages depending on the requirement while the collection is being looped.
Currently there's an option where field name and index as well is an input using utility - collection manipulation. The above is useful when the collection is used in a loop.
... View more
Hi Team,
Outlook VBO must have an action to save .msg File as pdf file.
Two options can be configured,
Saving the file as pdf document & Image file by passing Entry Id
Saving the file as pdf document & Image file by providing .msg file location
Looking forward to have these option in Outlook VBO.
Best Regards,
Vidhya Anbalagan
... View more
We're running into an issue where Hub is failing to handshake with our SQL instance due to a discrepancy in the expected type of encryption. We are able to successfully connect to the SQL instance from the Application Server using connection string arguments. Please allow for the same functionality when asking for information to connect to SQL where required in the installation of other components as well. Edit: This problem is currently specific to Hub 4.7. We are installing it alongside a 7.2.0 x64 environment.
... View more
Status:
Under Consideration
Submitted on
01-08-23
05:05 PM
Submitted by
DorinG
on
01-08-23
05:05 PM
Source /Image quick preview functionality
Build a Quick Source/image preview without having to open the source/image. Functionality would allow user to hover over the source and will display a preview of the image (first page , or all pages). Image retrieval can be leverage for this functionality.
This will be helpful when work item has multiple sources/images attached to a work item and the user need to focus on one source .
Functionality can be extended to instances where a source needs to be selected during fax out , email out functions that are currently available in Chorus. Quick preview will ensure correct image is selected and will reduce number of errors and potential privacy breaches. Attached screenshots for current faxout card and processor workspace.
Thank you
... View more
Prior to deploying a new version of a changed process or object, we are obliged to go over the changes with a colleague. To do so, we use the Studio Compare functionality.
This Compare highlights att changes in green, yellow or red for new, changed and deleted functionality. You use the hop to next or hop to previous buttons to navigate.
When there are a lot of changes on one particular page, they are all highlighted in yellow. Again, the hop to next or previous buttons are used to show what was changed to my colleague.
Unfortunately, the current stage is not indicated in any way and the screen just shows the yellow stages that were changed. This makes it quite hard to explain where we are.
This is what it looks today:
Wouldn't it be nice if the current stage would be marked in some manner? Something as simple as this perhaps:
Happy coding! --------------- Paul Sweden
... View more
Problem/Opportunity: Missed Components in Packages
This would be a job aid for deployment accuracy by tracking components as they are changed for inclusion in packages.
Blue Prism has a configuration option that prompts for Save Comment.
Add in the Save Prompt: Change ID
When creating packages if Save Comment/Change ID turned on prompt for Change ID and create a distinct list of components saved with the Change ID that can be dragged to the package.
This will help identify components as they are changed.
An extended suggestion would be to allow multiple Change IDs when creating a Package.
... View more
Status:
Under Consideration
Submitted on
13-07-23
07:35 PM
Submitted by
bmurali007
on
13-07-23
07:35 PM
Hi Blue Prism Support Team,
We at Best Buy, Canada use CITRIX environment to access our Corporate Applications. Recently, we have deployed Capture 3.2 in our CITRIX Environment and tried to record our business process automations. We noticed that the Process Definition Document (PDD) extracted from Capture was skewed and was missing several steps and descriptions. Also the Blue Prism Release file did not capture all the steps and required several modifications.
We would like to submit an idea to make Capture tool compatible in a CITRIX environment. A lot of clients use CITRIX environment to access Corporate applications and host RPA solutions. Hence it would be a great idea to make Capture tool compatible with CITRIX so that a lot of clients can benefit from Capture tool.
Thanks,
Bharath Murali
... View more
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
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
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
Status:
Under Consideration
Submitted on
08-06-23
07:00 AM
Submitted by
ManishRaw
on
08-06-23
07:00 AM
Hi Team,
When a BOT is used to call an API endpoint, the BOT machine details are send as an incoming requestor to the endpoint.
In case the authentication mechanism requires the creation of certificates to allow only the needed traffic, then all the BOT machines needs to be added to the certificate.
Moreover if there are any deletion or addition of BOT machines as per the requirement, then we need to create new certificates.
I want to propose to create an internal API gateway in Blue Prism using which we can redirect all the BOT API calls to BP Server and then BP server will in turn make the calls on BOTs behalf, this way we only have to create the certificates once that too with just the BP server details
If you like the Idea, please upvote so the SSC team can put that to their review list.
... View more
Additional options when creating a rule would be very helpful and reduce the volume of rules required for a form. My highest priority would be to have AND / OR settings (for example, field2 state is mandatory if field1 has a value of 'A', 'B' or 'C'). A While option would also be very useful as this would prevent the need to create 2+ rules in case a user changes something on the form (for example, field2 state is hidden while field1 = 'no'). Other suggestions include rules based on more than one field and any other basic functions. We currently have a very simple form which usually displays 7 fields on 1 page which uses 130 rules, the above changes would reduce that to under 10 rules.
... View more
Many security policies these days do not allow the same set of credentials to be used concurrently. ie. different sessions, same credentials. We need a configure so that the number of concurrent login sessions can be controlled or disabled to comply with security.
... View more
We tend to lose a lot of work when locks are released accidentally from all the locked process and business objects. This needs to be further improvised in the upcoming feature where admin (or superuser) can only release locks if required from all the process and objects. Developers would have restricted access to unlock either the process and objects that they have created or only one at a time.
... View more