75 results found
-
Enhanced Search Result Details in Web NG Client
In the current Web NG client, when users perform searches, the results do not indicate the menu under which each workflow is located. This lack of contextual information can lead to confusion, especially when multiple workflows have identical or similar names but reside in different menus.
Proposed solution is to improve the search functionality within the Web NG client to include additional details in the results, specifically the menu location of each workflow. This information should be displayed clearly beneath the workflow name in the search results. Providing this contextual detail will help users quickly identify the correct workflow, reducing…
11 votes -
Make Offline Data Persistent for Mobile Devices
Currently offline workflows support downloading data into the client and run workflows without an internet connection. However this data purely reside on memory when it comes to mobile devices.
If the application has to be closed for any reason, whole of the offline data will be lost.
This is essential for situations like off site asset count in remote locations. etc.
4 votes -
Descriptive Errors in Web Client
More descriptive error messages in the web client to pinpoint the exact issue in the workflow, instead of generic errors like "invalid step" or "string literal error."
2 votes -
"Finished" Status Visibility when Offline on Flow Inbox Items
In the current Flow mobile client, when operating in offline mode, users face a restriction where items in the inbox are marked as "Finished" after being acted upon. This status change makes the items inaccessible for further review, although they remain visible in the inbox until the user reconnects to the internet. This behavior limits the ability of users to revisit completed items for verification or review purposes.
Proposed solution is to implement a feature allowing users to toggle the visibility and accessibility of items marked as "Finished" in the inbox while in offline mode. This functionality would enable users…
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.
-
Customizable Pop-Up Controls for Streamlined User Experience in Portal
Requesting a feature enhancement in Portal to allow for the customization of pop-up controls during the review process. Currently, the mandatory provision of an exit button for publishing results in redundant close options (close button and 'x') at the bottom of the pop-up. It would greatly enhance user clarity and experience if administrators could define the visibility of the default close option, providing flexibility in tailoring the interface to specific workflow requirements.
5 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.
-
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"…
20 votes -
Improving API Execution: Scanner Event Optimization
We utilize scanner events to scan barcodes, extract item numbers, and retrieve item descriptions, locations, and stock balances. While this process generally works fine, we've noticed that Flow attempts to execute the API for connector steps even before scanning.
In the screenshot provided, you can see that there are three APIs that utilize the scanned item number to collect data. These APIs are triggered when the user step is displayed for the first time, even if the item number is blank. This leads to issues and longer response times.
If we bypass scanner events, the APIs should still run. However,…
1 vote -
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.
12 votes -
Export datagrid from workflows as Excel documents
We would like to have the feature to export datagrids in workflows as excel files
9 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.
-
Consistent Link Widths: Improve Visual Harmony in NG WebClient
We propose a feature enhancement to address the inconsistency in link widths within the NG WebClient. Currently, varying link widths create a visual disparity, particularly when compared to mobile clients. To enhance the overall aesthetics and maintain visual coherence across platforms, we request the implementation of a feature that ensures consistent link widths in the NG WebClient. This adjustment will contribute to a more polished and uniform user interface, providing a seamless experience for users across different devices.
1 vote -
Include Italian language in Flow Client and Studio
Currently Swedish, Norwegian, Finnish, German, French, Polish and English are the supported languages in flow similarly we need Italian added as well.
1 vote -
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 -
Checkbox Selection in Data Grid on Flow Mobile Clients
Users of the Flow mobile application face a limitation when interacting with data grids that contain checkboxes. Currently, to select a checkbox within a data grid column, users must navigate into each individual row and then set the checkbox. This process is seen as cumbersome and inefficient, especially for tasks requiring multiple selections across several rows.
The proposed solution is to introduce the functionality that allows users to directly select checkboxes from the main view of the data grid, without the need to navigate into each row. This enhancement should apply to all Flow mobile clients, streamlining tasks that involve…
2 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.
-
Customer brand login (sign in) screen
Current login screen only shows "Flow 6" (not even Novacura is mentioned).
We are gearing up adding external partners to the portal. It both creates suspicion and looks amateurish without our company name, and preferable logo, in the login screen. Enabling us to brand the layout with name, logo and maybe even colour would have made a big impact on the first impression.
5 votes -
Data Change Detection and Variable Utilization in Studio User Steps
In the current version of Studio, there is a limitation in detecting data changes made during a User Step. Proposed solution is to enhance Studio to include the capability of detecting any data changes that occur within a User Step. Following this detection, these changes should be easily accessible and usable as variables or properties in subsequent steps of the workflow. This feature would allow users and developers to dynamically adjust the workflow based on user inputs or changes, greatly enhancing the flexibility and functionality of Studio.
1 vote -
Enhanced Warning Message for Application Exit in Flow
Currently, the warning message displayed when a user attempts to quit an application in Flow may not be sufficiently informative or persuasive in communicating the potential consequences of exiting, such as unsaved changes being lost.
1 vote -
Unified Interface Layout for Consistent Navigation in Inbox
Requesting the option to standardize the visual presentation of the Inbox button to match the flat layout of other interface elements. Currently, the raised "depth" of the Inbox button stands out and lacks consistency with the rest of the interface. Providing a toggle or setting to align the appearance of the Inbox button with other buttons would enhance visual coherence and streamline navigation for users.
1 vote -
Concurrent Login Capability for Admin Users Across Multiple Platforms
As a consultant/developer, managing multiple clients often requires logging in and out frequently due to the limitation of one user/license per session. This process is time-consuming and inefficient.
Proposed solution is to enable admin users to be concurrently logged into multiple platforms - namely the Portal, Flow Client, and Flow Portal - without the need for separate licenses for each. This will streamline workflow management for consultants and developers who regularly need access to multiple clients or sessions simultaneously, significantly enhancing productivity and user experience.
2 votes -
Make it easier to write "Text"
To present relevant information our users, we type a lot of conditions and display variables practically everywhere. On arrows, in headers, in texts, in prompts and so on. Those fields can not be "opened" like a script-field (Condition To Hide) and when you try to navigate left or right in that field, it jumps around a lot.
Development is overall fast in Flow but those finishing touches that makes a good applikation great takes time.
Can we get the possibility to open these fields up to speed up development?
Thanks!
And I guess you already got a request to make…
1 vote -
Improved "Auto Focus" Option Behavior
The "Auto Focus " option currently fails to place the cursor in the first input field when it is the second element in a flow after a list box. This results in a non-intuitive user experience, requiring users to navigate through other elements before reaching the input field. We request an enhancement to ensure the cursor is directly placed in the first input field, or at least the list box, when "Auto Focus Input" is enabled, providing a smoother user experience.
6 votes
- Don't see your idea?