268 results found
-
Dual Line Data Grid for Enhanced Data Presentation
In ERP systems, item descriptions that are 90 characters long are common. These descriptions are crucial for end-users, especially when picking unpacked items. However, due to the current Data Grid's single-line layout, users often need to scroll both vertically and horizontally to view all the necessary information, which is not efficient.
While questions regarding how to determine what should be displayed and how to show column headers in the second row need to be addressed, the dual line option could start as an optional element. The benefits of this improved data presentation format would likely extend to other customers with…
2 votes -
Barcode Configuration and Recognition Improvements in Multi-List Selection
Customers using our mobile client have reported inconsistent performance when scanning barcodes using the List multi-selection input component. Specifically, it appears that the barcode recognition feature is not always operational. Additionally, the List multi-selection input component in Flow Studio lacks barcode configuration options. There's no way to change the default "Match By: Rows" setting to "Match By: Specific Columns". This restriction limits the flexibility and usability of this component for developers.
Proposed Solution: We propose to add the barcode configuration to the List multi-selection input component in Flow Studio. This should include the option to change the "Match By" settings…
2 votes -
Customizable Number Format Parameter in DataGrid
Currently, in the DataGrid component, setting a number format is fixed and cannot be parameterized. This limitation hinders the flexibility of developers to customize the number formatting based on different data and user requirements. As a user of the DataGrid component, I request the implementation of a customizable number format parameter to enhance the control and usability of this feature.
3 votes -
Responsive Data Grid Columns in Client View
In the current NG webclient, the GRID columns with "FIT" size mode aren't dynamically adjusting to window resizing. When viewed on full screen, all columns are visible. However, when the window size is reduced, certain columns disappear, forcing users to scroll horizontally.
Proposed solution is to enable truly responsive design for GRID columns, especially those with the "FIT" size mode. When a user adjusts the window size, columns should auto-adjust their width proportionally, eliminating the need for horizontal scrolling. This ensures a seamless user experience across various window sizes.
2 votes -
Empowering Precision and Control with MidpointRounding in Flowscript's Rounding Process
Empowering Precision and Control with MidpointRounding in rounding processes with two conventions
1. Rounding away from zero
2. Rounding to nearest even2 votes -
Component workflow parameters as default template for added components
When I add a component to a workflow I want to have all the component parameters as a default input to the component when I add it to a workflow.
As it is now I have to open the component to figure out what parameters to use, copy them and paste them into the component step in the workflow.
1 voteThank 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.
-
Improved List of Values Display in Portal2 with Filtered Inputs
In Portal2, when using a List of Values (LoV) tied to a table column, there seems to be an issue displaying the data if the LoV's data source is a Flow with an input filter. The data is displayed if no input filter is considered, but it does not show up when inputs are taken from Portal.
Proposed solution is to address the inconsistency by ensuring that the List of Values in Portal2 displays data correctly even when the LoV uses a Flow with input filters from Portal. It's crucial to provide consistent visibility and accessibility of data irrespective of…
2 votes -
Explicitly set the type of values fetched in SQL machine steps
I want to be able to define the data types for my SQL query so that the Designer knows the types I can work with when designing my apps and components.
1 vote -
Addition of "Today" Option in WebNG Datepicker
The WebNG Datepicker currently lacks a "Today" button, a feature that was available in the old web client. This button allowed users to quickly return to the current date, enhancing usability and navigation efficiency.
1 vote -
Hide Non-Editable Columns in DataGrid When Adding New Row
In the current implementation of a DataGrid, when a user adds a new row, the text from non-editable (display-only) columns still appears, giving an impression of inconsistency in the UI. This can be confusing for users.
Proposed solution is for non-editable columns to be hidden or made visually distinct when adding a new row to a DataGrid. This way, only the relevant editable fields will be displayed, providing a more intuitive user experience.
2 votes -
Lazy Loading in List of Values on Mobile Clients
When data is loaded for a user step, sometimes the user may have to search for data in LOV with large volumes. Eg adding a spare part to a work order.
Adding such a LOV to a user step may take time to load as the flow wouldn't move to the next step without completing that step. In order to improve the user experience, it is better to have the following;
Load batch-wise
The user step will get populated once the first 100 records are fetched, and the list has the option to load all or the next 100...Load…
1 vote -
Enhance Workflow Efficiency with Checklist Grouping Feature
We kindly request the addition of a new feature, "Grouping," to the control checklist subtask within workflows. This enhancement aims to optimize user experience and efficiency when dealing with extensive checklists. By introducing a grouping option, users can achieve a clearer overview of checklist items, particularly in cases where there is a substantial number of items. This feature will greatly improve workflow management and streamline task execution, contributing to a more productive and organized working environment. Your consideration of this feature request is greatly appreciated.
2 votes -
Auto-Centering of Portal 2 Scheduler Based on Current Time
In the Portal 2 environment, users must manually adjust the scheduler's view daily to align it with the current time. This manual process becomes inefficient for users, especially in environments where the scheduler is in a read-only state across all departments.
Proposed solution is to implement an auto-centering feature for the Portal 2 scheduler that automatically aligns the view with the current time upon refresh. This ensures that users always have a centered view of their schedule relative to the present time without manual adjustments, enhancing user experience and operational efficiency.
1 vote -
Offline Compatibility and Expanded Image Source Options for Image Selection Input Component
Our customers have expressed a need for offline compatibility and expanded image source options for the Image Selection Input Component. Currently, the component only supports URL-based image sources, limiting its use when offline access is required. To enhance the component's utility, we propose enabling additional image sources, such as JEPG, allowing users to utilize local data sources like tables in IFS. This enhancement would make the Image Selection Input Component fully offline compatible, significantly extending its usability and versatility for various use cases.
2 votes -
Streamlined Row Deletion Process for NG Webclient Datagrid
We kindly request the implementation of a more intuitive and efficient row deletion process in the NG Webclient datagrid, reminiscent of the user-friendly experience offered by the previous Novacura web client. The proposed enhancement aims to simplify the current multi-step deletion procedure, which includes clicking an empty circle, moving to the top of the datagrid, and confirming the deletion.
2 votes -
Enhanced Bluetooth Input Functionality After Manual Overwrite on Mobile Clients
Our users have reported an issue with the Bluetooth input in user fields on a mobile device. The problem arises when a value is input via Bluetooth into a user field, then manually overwritten, and a subsequent attempt is made to input a new value via Bluetooth. In these cases, the Bluetooth input fails to populate the field unless the user navigates to a different user step and then returns. This could potentially be due to the iOS keyboard taking over control after manual entry. This problem has been encountered while capturing Ultrasonic Thickness readings from an Olympus 38DL+ thickness…
2 votes -
Video Recording Capability from Android Clients
Users want the ability to record videos directly from Android devices using the Flow File gallery and Camera input. Currently, they are able to take pictures and access files, but they cannot record videos directly from the app.
2 votes -
Preserve Search Queries in WebNG
In the current NG webclient, search queries are not maintained after completing a flow. Users have to re-enter their search each time they finish a flow, which can disrupt their workflow and reduce efficiency.
To enhance user experience and productivity, we propose to preserve the search queries even after completing a flow. This means that after a user finishes a flow, their previous search query would still be in place, saving them the effort of having to re-enter it.
2 votes -
Always on Menu Bar in WebNG
Currently in WebNG, the workflow interface occupies the entire screen, hiding the left sidebar which houses important menus and settings. This design requires users to exit their workflows to access these menus, which can disrupt their workflow and reduce efficiency.
To enhance user experience and productivity, we propose a design change to allow the left sidebar to remain visible and accessible even while within a workflow. This change would allow users to quickly access menus and settings without needing to exit their workflows.
2 votes -
Option to hide search box in data grid
Currently, a search box appears automatically in a data grid, which may not be desirable in certain configurations. For example, when using a two-column data grid with interdependent list boxes, the presence of a search box can disrupt the intended user interaction.
We propose to add an option to suppress the automatic appearance of the search box in data grids. This would give developers more control over the user interface and allow for a cleaner look in specific scenarios.
2 votes
- Don't see your idea?