Showing ideas with status New.
Show all ideas
We have a mix of Users who either love or are overwhelmed by Processor Workspace (as compared to Classic Workspace). Some of our Users find Cards ability to go anywhere and not have a permanent Docking (or Pinning) Spot (for each Card on Workspace) can be overwhelming. With an update to allow Docking (or Pinning) of Cards the Users would be able to Move and Pop out Cards (which they have with current functionality) or Dock/Pin in permanent spot to be similar to Classic depending on each Users own preference. #ProcessorWorkspace #Cards #Chorus #DockingCards
... View more
My client feedback on the new Processor workspace: the scroll bars is just too thin (the width is too narrow), very hard to use. This applies to both the horizontal and vertical scroll bars. My client is undergo the upgrade to 23.x, so they tried both 22.x and 23.x. I feel the same, and tried on 23.x regarding the Worklist, Search card, Forms, etc
... View more
As a user, I want to a rules engine that can:
Can handle rules at scale
Tech-savvy BA’s can partner with IT to author and maintain rules with min developer involvement
Source control and change management to see what was changed and by who, and to test in lower environments
API integration
Can handle complex rules outside of code
... View more
Many business procedures have standard comments that are copy pasted onto an item, and then modified as needed. To streamline the process, as a user, I want an option for AWD to populate standard comments for a given Business Area/Work Type combination so that I don’t have to copy paste them from elsewhere.
... View more
As a user, I want to be able to “pin” one or more comments so that they always display first. This way if a comment contains important information, it can be seen quickly.
... View more
It would be beneficial to designers integrating with REST services to natively provide instructive messages for connectivity exceptions. OpenApi/Swagger describes http response codes but not java exceptions outside normal http flow. For example this exception is captured for connection errors: com.dstawd.processengine.model.flowobjects.AutomatedActivityFlowObject.executeService(ProcessInstance, String, String, Element): Service failed to execute. Error: java.lang.IllegalAccessException: The response object is javax.ws.rs.ProcessingException, not an fastrequirementsapi.ApiException Service Error Stack: It would be beneficial for these types of errors to expose the actual java exception or a friendlier message to the designer. This information can be found in log files that typical designers do not have access to.
... View more
Having the ability to export roles and permissions from an existing Active Directory user account and then import them into a Native user account would indeed be beneficial. This feature would streamline the process of managing access rights and ensure consistency across different user accounts. Having this functionality, Blue Prism admins could efficiently transfer permissions, maintain security standards, and simplify user management. It’s a practical enhancement that aligns with best practices in access control.
... View more
Blue Prism v7.3 provides dual authentication feature. Native user authentication. Active directory authentication. It would be very useful to have a functionality, which can help clone an existing Active Directory userid to Native userid, providing the same Roles and Permissions as of the Active Directory userid.
... View more
We would like the AWD Option of 'Expire by Date' to work with Processor Workspace as it did with Classic Workspace. In Classic Workspace we used the 'Expire by Date' option to have any items suspended for a day to unexpire with first Batch run of the day. However with Processor Workspace this option doesnt work as Processor was not coded to use it. We would like this 'Expire by Date' option to work with Processor Workspace to match how it works currently with Classic Workspace. Let me know if there are any questions.
... View more
With Search forms and potentially and Chorus form designed for work processing whether UXBuilder, Dynamic Forms, or Traditional forms the ability to denote a one of these are required. My thought on implementation would be to contain the fields within a group box and mark the box with a css class of oneOfThese. There could be multiple group boxes with independent oneOfThese markers. This was implemented as custom javascript on a Search form that required a hidden text input that was marked required that the custom javascript managed inputting/clearing to get the Search button enabled/disabled appropriately.
... View more
If a table in UX Builder has row selection enabled(single or multiple), it should also have the option to mark it as a required field. This will force the user to select a row from the table before being able to continue on. Currently as a work around we have to use a button that calls a UX service to ensure that table.selected has data before activating a second button to actually let the user progress. This adds clicks, is not intuitive to an end user, and creates more services to maintain.
... View more
Filter functionality is currently set to only one filter per data field/column. We would need functionality to apply AND/OR filtering at numerous levels within a particular data field. For example, if the user works on portfolio's CS_CABSLF and CS_ALPEN then we would like the ability to filter the 'Item Key' data field to be CS_CABSLF OR CS_ALPEN. There should be no limit to the number of levels we can filter a particular field for. Again, if a particular user works on 12 different funds, we would have 12 levels of OR filtering within said column/data field. There is no functionality to move columns around within the view in a different order. We are referring to drag and drop functionality on screen. Column width appears to be pre-defined and user does not have ability to expand or shrink a particular column based on underlying data length. If the underlying value in the column goes out further then the current column width, the UI merely adds '…' and we cannot see the entire value. For example, item key 'CS_CABSLF - 1/8/2024 - Rerun 15014…' or Exception Reason 'Max Retry Reached - GoCheck Ticket 10...' or Tags 'Exception: Max Retry Reached - ...' - there is no ability for the user to see the entire wording on screen within the UI. Ideal solution would be to introduce the wrap text functionality per column. User should have capability to retrigger a process within the Work Queue screen. For example, item key 'CS_CABSLF - 12/21/2023 - Rerun 193554
... View more
There is no functionality to save filters on the work queues screen. For example, if one individual is working on only portfolio CS_CABSLF - we would like to have the ability to save custom user filters so that when that user opens up the work queues dashboard, they will automatically see their respective funds
... View more
Once in the work queue for a particular item key - we would like to have the capability to drill into the details of that item. For example, item key 'CS_CSNOVA(LUX) - 1/8/2024 - Rerun' has a completed status, but we need to be able to click into it to see all the underlying processes within that item. Our idea is to have the capability for the user to click on the item and have the box expand detailing all underlying processes using the same format as the current view/layout. To minimize the user would click on the item again to return to normal summary view.
... View more
Blueprism HUB Auto refresh is not saved as part of the custom view that the user creates/saves
... View more
Entitlements need to be added to Blueprism HUB as users should only have access to the clients. HUB control access to Business team level. Example: Business supposed to see only their process and queue details in control room
... View more
Almost all actions that you carry out on a document during verification are accessed via the right-click menu. the menu is a long one, but unless the document you're working on is scrolled right to the top of the list, part of the menu disappears off the bottom of the screen. Only if you're right at the very bottom of the screen does it re-position to open 'up' from where you click, so the whole thing is visible.
Rather than having to use the right-click menu at all, it would be much better to have a toolbar at the top of the verification screen with buttons for all possible actions.
At the very least make the menu render fully visible regardless of where you click on screen.
... View more
We should consider raising this display/resolution issue with the development team, as it has been observed by numerous users. Ideally, software should be capable of adjusting to users' display settings without requiring them to change display settings on their machine.
... View more
We are using Decipher v2.2 in our environment and enabled SAML.
As part of security policy, we deleted "admin" and "generaluser" and tested the environment.
BP Decipher:
Deleting the default user “admin” and “generaluser” impacting the functionality of the application.
To enable the SAML Authentication to have AD User login requires to enter master SSO user – admin and its password. (if we delete default admin user – we need to give a alternate user detail which has Admin Role)
Same way config files in the Decipher Automated Clients requires “generaluser” details to be entered for performing Decipher task.
After deleting the “admin” and “generaluser” in DEV, Decipher functionality got impacted
... View more
As a Chorus user, I'd like to be able to specify (independent of locale, browser settings, or system configuration) how dates appear in Chorus. This should include both entry fields and other places (such as history) where dates are presented.
While it is possible for Chorus process developers to control input fields in form design, the options are limited, and this does not change other areas such as history, which results in further user confusion. This also does not address a single process used in different regions with differing standard date formats, where the only current solution is the creation of multiple otherwise identical forms.
One suggestion is to enable an additional user preference, as this would cater for Chorus implementations where a single solution (set of processes) is used across multiple geographies.
... View more