After having used the Blue Prism product for a few months now, our team has identified several items which, depending on one's perspective, could be considered bugs OR requests for enhancements. We'd like to share some of these with the forum and see if anyone else can corroborate these experiences, or if Blue Prism staff are aware of and actively working on any of these items -
1.) Toolbars and app elements do not stay where they last were placed in the Blue Prism application.
-When working within the Blue Prism application (Object/Process Studio), placement of utility and tool bars is not saved within the application and resets to defaults when closing/opening any given object/process. This is mildly annoying to developers (who can get quite accustomed to their particular operating and working environments) and should be easy enough to fix.
2.) BP dialogue windows do not "pop to the front" or play an audible sound when they have locked the application and require a response
-Dialogue boxes in the Blue Prism studios sometimes require input or acknowledgement and "lock out" other BP application windows, but do not pop to the front of all open BP windows or otherwise make themselves clearly visible and indicating they require acknowledgment. This is prohibitive when multiple windows and studio environments are open for development, making it unclear what window or dialogue box requires attention or acknowledgement before moving forward. It would be advantageous if Blue Prism would force the window(s) requiring input to the front of all current BP application windows when this occurs.
3.) Link stage maintains original wait element text when copying from one object to another
-After copying one Business Object page to another Business Object, the wait stage that is pasted does not dynamically update when the element of the wait stage is changed/modified for the context of the new Business Object. After modifying the wait stage element and value of the wait stage (in the copied object), the text linking from the anchor point to the next stage remains as it existed in the source Business Object.
4.) Unable to resize multiple stages
- When selecting more than one stage (i.e., a set of Navigate, Read, and Write stages that compose a single application action of some sort), the ability to resize all of the shapes at the same time is lost. It would be advantageous to be able to select multiple stages on a given page, and resize them in a collective group, rather than on a one by one basis.
5.) Unable to use arrow keys to move stage shapes
- When selecting a stage shape, the only way to move the stage around in the workspace is to use your mouse by click and drag methodoogy. It would be a nice feature to be able to use arrow keys as well for fine-tuned placement of stages.
6.) Targeted Collection row removal
- Current BP logic requires loop stages through collections in order to "target" any given row for removal or deletion. It would be beneficial if there were some sort of "Remove Target Row" option or object that could quickly and easily address this.
7.) "Click & Drag" of stages in workspace can cause extreme shifting of workspace sroll bars/scale.
- If multiple stages are selected and a click and drag function is initiated (hold left-click to move all items simultaneously), AND the cursor/stages are brought near an edge of the displayed workspace (horizontal or vertical edge), the application can engage automatic scrolling (horizontally or vertically) in an "extreme" scale, which is difficult to effectively clean up without arduous zooming in/out and restoration of relative stage positions. It would be very beneficial if this effect could be controlled either by means of a slider value or option that would allow for more granular control of this scaling.
Please let me know if any logs or further information can be provided to support these reports/requests, and thank you all for your time and consideration!
