222 results found
-
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.
1 vote -
Introducing a Feature to Locate Published but Unshared Flows
During development, I utilize a fantastic feature to update and auto-publish flows affected by changes. However, transitioning to the Production stage is less straightforward, requiring manual searching, opening, and sharing of modified flows.
To enhance this process:
Simplified Sharing: A 'Share' option accessible through right-clicking flows in the server view could eliminate the need for individual openings, complementing the existing 'Publish' link.
Unified Sharing Checkbox: Similar to the 'Publish' checkbox, an equivalent 'Share' checkbox for updating flows could streamline post-approval sharing, especially for numerous flows influenced by fragment adjustments.
Differential Version Listing: A feature listing flows with differing published and…
1 vote -
Enhanced Functionality for Identifying Flows Requiring Update
When sharing a flow across different environments and switching between them, I notice the flow being marked with a green circle containing a white star, indicating the need for updates.
Kindly introduce a feature that enables view filtering, allowing me to exclusively display flows requiring updates. This is particularly essential when dealing with a considerable number of shared flows, as manually clicking, scrolling, or searching by name becomes time-consuming. The ability to readily access 'All Subscribed Flows with Updates' would be greatly beneficial.
I would appreciate the inclusion of a 'batch update' functionality for flows. Currently, updating each flow individually…
1 vote -
Extend Language Support in Portal 2 (Spanish)
Currently, Portal 2's assets only include support for English, Swedish, and Norwegian languages. This limitation impacts the usability of the Syncfusion components within the system for Portuguese and Spanish speaking users.
We propose the inclusion of Portuguese and Spanish languages into Portal 2's assets. By expanding the supported languages, we can enhance the user experience for a broader audience and meet the needs of more diverse customer bases.
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.
1 vote -
Enhanced Log Analysis Tool for REST M3 API Connector
We urgently request an upgrade to the existing log analysis tool for the REST M3 API connector. Currently, the tool lacks the essential capability to efficiently search for specific transactions or data within the logs. With each call and response generating individual log files, the volume of transactions quickly becomes overwhelming, rendering effective analysis nearly impossible. In contrast, the previous socket-based M3 API connector generated a consolidated API text file that enabled easy data search and facilitated comprehensive analysis, including input and response times. The current limitation significantly hinders error diagnosis, making the troubleshooting process arduous and time-intensive. We propose…
1 vote -
Addition of "Ask for Help" Feature in Offline Data My Work Screen for Mobile Apps
The new mobile apps lack the essential "Ask for Help" feature within the Offline Data My Work screen. This absence prevents users from effectively reporting errors to Administrators for prompt resolution. By integrating the "Ask for Help" feature, users will be empowered to send problematic records to Administrators, streamlining the troubleshooting and repair process. This enhancement aligns with the documented Novacura Flow Help page, ensuring consistency and comprehensive functionality across all platforms.
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.
1 vote -
Enhance SQL Machine Steps for Direct Flow Table Usage and Improved Performance
Currently, the process of using a table variable within an SQL machine step in our workflow involves a workaround using JSON, which can lead to extended user wait times due to additional processing. Additionally, Flow's handling of table iteration within SQL is notably slower compared to direct SQL operations on large datasets. Our proposed feature request aims to streamline this process and enhance performance. We kindly request the implementation of the following enhancements to Flow's SQL machine steps:
Direct Reference to Flow Tables: Enable the ability to directly reference Flow Tables within SQL machine steps. This functionality would eliminate the…
1 vote -
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.
1 vote -
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…
1 vote -
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.
1 vote -
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.
1 vote -
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.
1 vote -
Option to delete recent environment connections
At times, certain servers may no longer be in use, or their names might change. In the current system, these outdated entries remain in the "Recent servers" list, potentially causing confusion or clutter.
We propose to implement an option to delete previous connections from the "Recent servers" list. This feature would enhance the user experience by keeping the list tidy and up to date, reducing potential confusion or errors.
1 vote -
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.
1 vote -
Temporary Editable Columns Table Portlet
Currently, modifying values in a table requires the use of Edit Operations. However, there is a need to allow temporary or inline editing of table records without employing Edit Operations. This would enable users to make temporary changes to selected records and then execute a custom workflow using a special button. The workflow's InputTable would include all records, reflecting any changes made.
1 vote -
Persistent Rendering of Results in Scheduler
Currently, when users render a result in the scheduler, then navigate to a different page, and later return to the scheduler page, the previously rendered result is not retained. This behavior contrasts with the functionality found in the filter portlets and the Gantt portlet, where results persist through page navigation.
We propose that the scheduler should retain the rendered results even after navigating to a different page and then returning. This persistent rendering will provide a more consistent user experience and align the scheduler's functionality with other parts of the system.
1 vote -
Linked Highlighting of Allocations in Scheduler
Scheduler is often being used to manage allocations, with multiple allocations often tied to a single operation. While these allocations are perceived as the same object, they aren't currently treated as such in the Scheduler.
We propose a feature that enables linked highlighting of allocations tied to the same operation. When one instance of the operation is selected, all corresponding allocations should be highlighted. The actual selected instance could be distinguished with a unique color while other instances are highlighted with another color. However, when interacting with a single instance (e.g., dragging it forward in time), only that instance should…
1 vote -
Enhanced and Customizable Highlighting for Scheduler
Currently, the visual emphasis when an object is selected in the Scheduler is quite subtle. This could potentially cause users to struggle in identifying their selected object, especially in a dense schedule.
We suggest enhancing the object highlighting functionality in the Scheduler. This could involve introducing a more pronounced visual cue, like a more prominent shadow or highlight. It would be beneficial to make the intensity of this visual cue customizable. Additionally, users should be allowed to choose the color of the highlight, providing another layer of customization and personalization.
1 vote
- Don't see your idea?