83 results found
-
Change Font, Colors, and Alignment within User Elements
Within a User Element in a User Step, I would like to be able to change the font, front size, font color, alignment, bold, italics, and more so that I can make more visually appealing workflows.
37 votes -
Scrolling in Workflow Elements Locked when Workflow is Not in Edit Mode
When double clicking an included workflow in studio to view what parameters are being sent, the scroll bar is locked unless the user is in “edit” mode.User should be able to scroll and view all the parameters without entering edit mode or resizing the window.
19 votes -
Enhanced Conditional Data Binding for List Selection Inputs in Novacura
Currently, Novacura lacks a native way to establish simple data dependencies between List Selection Inputs without using a DataGrid. We propose the implementation of an enhanced conditional data binding feature that allows users to filter or automate data in a field based on the selection or input in another field. This feature will improve usability and efficiency by enabling dynamic updates and conditional visibility of form fields. This would allow for more dynamic list selections within a User Step.
Sample Use Cases:
User selects a country from a list.
Another list automatically shows valid states/provinces relevant to the selected country.…
15 votes -
Introduce FlowScript in REST Service connector parameters
it would be highly advantageous to introduce the ability to execute this script as an option within a REST Service call. Currently, the REST Service connector parameters only offer limited choices such as "Variable," "Constant," and "Not Set." By incorporating this script execution as an alternative, it would empower users to execute more intricate operations within the flow, thereby providing greater flexibility and customization to the process.
10 votes -
Date Column Option in DataGrid User Element
There's no direct support for formatting the date column in the DataGrid User Element.
10 votes -
Allow Developer to Open a Fragment Without being in Edit Mode
We would like to open up a fragment from the editor instead of either needing to enter edit mode or search in the server content window. There are times when multiple fragments of the same name exist in the server, and it becomes important to know which version is actually used. Furthermore, editing fragments, and not committing or reversing changes causes lock out of apps - all just to open an fragment to inspect.
10 votes -
Overview of Scheduled Workflow Executions
As an Administrator of an environment, the customer would like to see an overview of machine workflows and their executions, specifically for scheduled workflows. It is possible to schedule a workflow, but it would be good to see if the workflow was succesful or failed. If it failed, at what part of the flow did it fail and what inputs and outputs were there at that point in time. It would be great if an administrator could make changes to the data and re-run it from the failed element within the flow.
10 votes -
Support Push Notifications for Swimlane Handovers with Multiple Languages
We would like to Enable push notifications for Swimlane Handovers to support multiple languages in the text.
8 votes -
Global Functions for Cross-Script Usability in Flow Environment
We request the implementation of a feature that enables users to create global functions within the Flow environment. These global functions should be accessible and usable from any script within the environment, irrespective of their location. By having the ability to define reusable functions at a global level, users can avoid redundancy and promote code modularity across their workflows. This enhancement would significantly improve the efficiency and maintainability of scripts within the Flow environment.
9 votes -
Progress bar UI element
When doing complex operations in Flow, either as a loop of machine steps or as a machine step with an iterator, the user is left in the dark about what is happening. It would be great to be able to present the user with a progress bar that gradually fills while Flow is processing the operations. This could be a special User step that requires no interaction from the user and disappears when the process is done. Inputs would be a counter variable, a total of the number of operations and a user message detailing what is going on.
A…
5 votes -
Resize images to fixed file size
we would like to have enable a feature that allows downsizing to specified size (in MBs). Solution calculates the required resizing factor and use a quality down sampling algorithm (e.g. bicubic) that maintain adequate image quality and get it down to specified file size or just below. from the flow itself.
6 votes -
Arrows are not easy to identify or get too long
Sometimes I have VERY long arrows. When i highlight the arrow I can see it nicely, but as soon as I try to move it is not highlighted. I want to be able to see my separate arrows ESPECIALLY WHEN THEY overlap.
A few options to consider.
Allow me to color arrows different colors for visibility.
Allow me to select an arrow and leave it “selected” so it stands out.
Allow me to have a shorter arrow that goes to a “GO TO” element which is just a pointer to another element in the flow.
3 votes -
Timezone script and setting in Flow
The current Now() function in Flow retrieves the time based on the device's local time. This can lead to inconsistencies for users or workflows operating across different time zones. To improve this, there's a need for advanced time manipulation functions and settings.
Proposed solution is to introduce new functions like Now().utc, allowing users to retrieve time based on specific time zones like UTC. Additionally, integrating a timezone setting for each user in Studio, similar to the existing Language and Locale settings, can ensure consistency and accuracy in workflows, catering to diverse customer needs. This enhancement will grant users greater flexibility…
5 votes -
Simplifying Workflow Conversion
Frequently, I design a workflow and realize the need to switch it from a User Flow to a Fragment, either due to oversight during creation or the newfound requirement for reusability. The current process of converting the workflow in the studio is rather cumbersome. Although I've managed to export the Flow, manually tweak the XML, and then re-import it to achieve a Fragment, it strikes me that this procedure could be streamlined. Perhaps a more user-friendly approach would involve incorporating a 'Convert To' option, accessible through a simple right-click within the server explorer, offering a range of flow type transformations
5 votes -
Optimize Database Performance by Implementing Version Archiving and Deletion for Workflow Version History
Our database has expanded due to numerous historical versions of Workflows, causing significant delays when making changes in the Workflow management system. To overcome this issue and enhance workflow development efficiency, we need version archiving and deletion capabilities. By storing older versions separately or deleting unnecessary ones, we can boost database performance, reduce loading times, and increase overall productivity.
8 votes -
Remove "Create" word in sequence arrow popup menu
When you create a sequence arrow then right click, there is no need to have the word "CREATE" before each element.
Additionally, the list could be alphabetized to easier find the type of element you want to add.
3 votes -
Enhanced Variable Management in Debug Mode (Test Bench)
When debugging workflows in the Studio with a high number of variables (200+), it is time-consuming and challenging to locate specific variables. Currently, variables are not presented in any particular order and cannot be sorted.
We propose to introduce the following enhancements for variable management in debug mode:
- Ability to sort variables by name and type.
- Search functionality to find specific variables (or part of a variable name).
- Option to monitor specific variables - a feature where the user can mark specific variables which will always be at the top of the list.
These features will significantly improve the efficiency…
6 votes -
Simplified "For Each" Loop Element for Dataset Processing
Currently, when looping through a dataset/table, users need to create a copy of it, check if it is empty, fetch one row at a time, process it, and then exclude that row before continuing the loop. This process involves unnecessary steps and can be time-consuming. Therefore, I propose the implementation of an easy-to-use "For Each" loop element. This element should allow users to set the dataset and define the assignment of each row, simplifying the iteration process. It should automatically handle row traversal without requiring additional checks or dataset manipulation. This feature would enhance productivity by streamlining dataset processing and…
6 votes -
Enhanced Flow Variable Update Capability Within Scripts
A feature enhancement that allows users to update the values of flow variables from outside of a script. Currently, when working with variables X and Y, executing a script step only allows for returning a value to overwrite one of them, or utilizing a complex workaround with a record to update both variables. We propose the addition of a simple syntax, such as ":flow.X = "something";" within the script, where the ":flow" prefix defines the scope of the variable being modified. This improvement will streamline the process of updating variables, eliminating the need for additional steps and making script operations…
6 votes -
Update the version of the SqlParser
Update to the latest version of the SqlParser For Special SQL Server Functions such as string_agg([Column], [separator]) function in combination with "WITHIN GROUP (ORDER BY [Column])"
2 votes
- Don't see your idea?