88 results found
-
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.
12 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.
12 votes -
Date Column Option in DataGrid User Element
There's no direct support for formatting the date column in the DataGrid User Element.
11 votesThank you for voting on this feature request. Our product team is currently reviewing it and evaluating its feasibility and potential impact. We will keep you updated on any progress.
-
View Data Grid columns without being in edit mode
It would be nice to be able to view data grid columns without first having to be in edit mode in studio. As it stands, when you select a datagrid element while not in edit mode, it only previews the column names in that boxed area, and depending on the length of the names, only shows a few of them. It would be super helpful if we could go a layer deep to view each column, it's data source, and perhaps just the entire edit screen in general without having to officially open it up for editing.
9 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…
9 votes -
FlowScript Code Formatter
Currently, Flow Script does not offer any assistance in code formatting, which could lead to less readable and harder to manage scripts.
We suggest the introduction of a "Code Formatter" button in Flow Script. This button would apply some basic formatting rules, such as indentation, to make scripts more readable and easier to maintain. Even though users may request further customization options, having basic formatting support will be a significant improvement over the current situation.
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…
8 votes -
Enhanced DataGrid Selection Control with Default Row Selection
We kindly request an enhancement to the DataGrid functionality in Studio, allowing users to pre-select one or more default rows when binding the DataGrid to a table and enabling selections, including single selection mode. Currently, users are unable to set default selections, which can result in additional manual steps for users to accomplish this. This proposed feature aims to improve the usability and efficiency of DataGrids by providing the ability to automatically mark specific rows as "selected" upon binding.
8 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 -
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…
7 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.
7 votesThank you for voting on this feature request. Our product team is currently reviewing it and evaluating its feasibility and potential impact. We will keep you updated on any progress.
-
Expanded Menu Priority Order Integers
Currently, the menu sorting order in our system is limited to priorities 1-10, which restricts our ability to effectively organize a large number of menus. We kindly request an enhancement to the sorting functionality that allows for a broader range of priorities, specifically from 1 to 100 or, ideally, any integer. This would provide us with much-needed flexibility and control in managing our extensive menu collection, leading to a more seamless user experience and improved efficiency.
7 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.
6 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
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 -
Enable Seamless Script Integration with Included Workflows and Machine Steps
We request an enhancement to enable script steps to directly interact with included workflows and machine steps. Currently, this limitation leads to complex workarounds and inefficiencies, particularly when processing datasets in loops. With the proposed improvement, users can easily call included workflows and machine steps from within script steps, streamlining data processing and reducing the need for intermediary datasets. This enhancement will significantly improve workflow efficiency and simplify task execution.
6 votes -
Hide Grid Column when empty
Dear Novacura R&D,
As much as powerful the grid element in the User Step is, it would be great to enhance it with dynamic features.
Like the 'Condition to hide' that affects the elements in the User Step, it would be great to have something similar for the content of the grid. And thus, if a particular condition is met, say a column is empty, then it could be hidden.
We quite often find ourselves in situation where we have multiple scenarios and data that differ from each other. Instead of creating multiple grid variants in one User Step, it…5 votes -
Enable "Workflow Fragment" as Seed Item with Data Arrow in Flow Studio
We kindly request the implementation of a new feature within Flow Studio, allowing the integration of "Workflow Fragment" as a Seed Item while utilizing a data arrow to the start step. Currently, any attempt to include a Workflow Fragment as a Seed Item leads to undesired outcomes. Specifically, when users press the "Run" button, the flow crashes, or upon selecting the "Publish" button, an error message surfaces: "Missing mapping for NovaCura.Flow.Designer.CanvasItems (..). Possible usage of unconverted elements from previous Flow versions."
5 votes -
Additional Options for Right-Clicking User Steps - "North" and "South"
Currently, when right-clicking a user step in the application, users have the helpful option "Select Everything East of Item" available in the context menu. However, we propose the inclusion of additional options, specifically "Select Everything North of Item" and "Select Everything South of Item," to further enhance the usability and flexibility of the user interface.
5 votes
- Don't see your idea?