222 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 -
New Connector in order to work with Excel files
We would like to have a new conector in order to read and process excel sheets as part of our daily business. At the moment we can only work with .csv files using existing Novacura connectors. We would like to request to add a Connector to make it easier to work with Excel Files.
25 votes -
Ability to edit data in a mobile client like Excel
The ability to edit data in a true table grid format, rather than having a separate screen for each record, refers to a user interface design where data is presented in a tabular structure that resembles a Excel format
22 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 -
Customized Button Placement in Clients
The suggested improvements to the current system involve enhancing the user experience and customization options in the graphical user interface (GUI). The proposal includes two main features:
Customizable Button Placement: The users express a strong interest in having the freedom to choose where the buttons (outputs) from user steps appear in the GUI. Currently, the system only allows the selection of priority, but the buttons always appear in the bottom right corner of the user step. The proposal seeks to provide flexibility, allowing users to position the buttons according to their preference, resulting in a more intuitive and user-friendly interface.
…
16 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 -
Native Image Markup and Annotation within FLOW Client App
Our customers have expressed a strong demand for a more efficient and seamless image annotation process within the FLOW Client app. Currently, users face inconvenience and inefficiencies as they need to save images locally and then upload them separately before performing annotations or markups. To address this concern and elevate the user experience, we request the integration of native image markup and annotation capabilities directly within the FLOW Client app, enabling users to capture images, annotate them, and instantly save or submit the annotated pictures.
15 votes -
Close Pinned Steps
A process involves calling a flow fragment with a pinned user step. After completing the fragment, returning to the main flow retains the now irrelevant pinned step, potentially causing confusion. Pinned steps should close along with their parent flow to avoid this issue.
12 votes -
Mandatory Offline Data Update Prompt
The feature in question is the "Offline Data Update Interval" setting, which prompts users to update their offline data after a specified time interval. While this functionality is beneficial in maintaining up-to-date data, we observed that users have the option to dismiss the update prompt by clicking "No" and proceed with launching the flow without refreshing their offline data.
We have tested this behavior in the Windows 10 Flow Client, where we configured the offline data update interval to 1 hour. As expected, we received the "Offline Data Expired" notification when the interval elapsed. However, we found that clicking "No"…
12 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 -
Add Branding Capabilities to NG Webclient
At present, the NG Web Client lacks branding capabilities. This limitation restricts the ability to customize the look and feel of the platform, which could affect the user experience and the alignment with the company's branding guidelines.
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 -
Reduce Whitespace Between Checkbox Elements
In our current Flow design, the use of checkboxes creates unnecessary and excessive whitespace, particularly when two checkbox elements are placed close together. This not only affects the aesthetic appearance of the interface but can also impact the usability by requiring additional scrolling and making the layout appear disjointed.
9 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 -
Descriptive Error details in Web Service connector logs
We would like to get more information on the error when an error is thrown by the remote system when communicating through the web service connector. Sometimes there is not much information available to the user or developer for that part. It would be great if this error in full could be written to the error log file which would make debugging this a lot easier. And of course also present the correct error message in full to the user.
9 votes -
Export datagrid from workflows as Excel documents
We would like to have the feature to export datagrids in workflows as excel files
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 -
OData Error Format Change
We would like if the OData connector return error (Error.jpg) like in IFS structure (IFS error structure.png) as a flow structure: record error containing fields code, message and table details with code and message columns. This would remove the need to beautify the ErrorMessage in flow script. Also using the break workflow feature could show just the error.message and details.code + details.message (Error in flow.jpg).
8 votes
- Don't see your idea?