243 results found
-
Improved Handling of Fragment Versioning and Error Navigation in Flow Studio
In the current system, when there's an error in a flow fragment version, navigating to the issue via the Problems window takes the user directly to the fragment version causing the error. While this might seem like a logical approach, it can be counterintuitive in scenarios where multiple versions of flows and fragments are being worked upon concurrently. Users might end up editing older versions of fragments unintentionally.
Use Case Scenario:
Consider two flows, A and B, where B is a fragment invoked by A. Both have versions Av1 and Bv1 as the latest. Now, if a new version of…2 votes -
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 -
WebNG Push Notifications
Currently this feature is not available in the web client and only available for the mobile devices. The idea is to implement a push notification to a user or a group whenever a swimlane handover happens (i.e inbox items handover).
1 vote -
Enhancements to Offline Workflows while on Multiple Networks
Users experience challenges with offline workflows in Flow-app due to network variability. Devices connect to various networks throughout the day, but only one network provides the required server connection for data sync. As a result, offline transactions get stuck in a "failed" state, necessitating manual retries once the device reconnects to the secure network.
Proposed solutions are to implement a feature in the Flow-app to detect the current network. The app should only attempt to write back to the server when connected to a predefined, specific network. Alternatively provide users with an option to bulk retry all failed offline transactions…
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 -
Dynamic "Allowed File Extensions" in File Gallery Uploads
Currently it is required that the "Allowed File Ending" values are hardcoded when uploading documents to the File Gallery. This rigid setup limits adaptability and increases maintenance efforts, especially when file requirements change frequently.
Proposed solution is to integrate the capability to accept variable values for specifying allowed file extensions in the File Gallery. This dynamic approach will enable administrators or developers to modify accepted file extensions on-the-fly without the need to alter the flow itself, enhancing flexibility and reducing the need for frequent flow modifications.
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…
2 votes -
Enhanced Record Selection Consistency for Multi-Select Data Grids
Improve multi-select grid usability on the latest mobile client by enabling "Click Anywhere To Select" functionality, similar to single select grids. Also, align the de-selection behavior with single-select grids, allowing users to "Click again to de-select record," creating a consistent and intuitive user experience across different grid types. This enhancement aims to optimize record selection and de-selection, particularly on small screens, for enhanced usability and efficiency.
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.
-
Improved Machine Step Script Error Handling for Oracle Code
We kindly request the enhancement of the machine step script error handling process related to Oracle code. Currently, an error is being flagged erroneously, even though the syntax is accurate and aligned with Oracle object specifications. We propose an update to the error detection mechanism to correctly recognize the valid syntax on Oracle objects, ensuring seamless execution of machine step scripts without unnecessary interruptions.
2 votes -
Streamlined Fragment Version Update Button in Workflow View
We kindly request an enhancement to the workflow interface by adding a convenient "Update to Latest Fragment Version" button directly accessible within the workflow view. Currently, users are required to navigate through menus to initiate updates, leading to unnecessary disruptions and potential confusion. This proposed feature aims to improve user experience and workflow efficiency by providing a seamless and direct option for updating fragment versions.
2 votes -
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…
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.
-
Ability Access Control to root Folders of Flow Studio
When multiple parties are involved in Flow Development (eg Novacura/Partners/Customer) it is essential to control access to different workflows. One of the ways to achieve this is to allow access control to the folders created on the root (and not allowing any workflows/menus to be created without a folder)
1 vote -
Improvements in the Pick Menu for Fragments in Studio
The current Pick menu within the workflow interface presents several counterintuitive aspects that could be streamlined for a more efficient and user-friendly experience. We propose the following enhancements:
Automatic Selection of Single Versions:
When a flow with only one version is selected, the system should automatically utilize that version instead of prompting the user to choose. This reduces unnecessary steps and simplifies the process.Default Selection of Current Version:
Implement a feature that enables the automatic selection of the current version by default, allowing users to easily proceed without intervention. Users can then manually select a different version when required.…
2 votes -
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.
2 votes -
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…
2 votes -
Alternate Line Coloring in Scheduler
In the current design of the Scheduler, there is no option to alternate the color of lines. This can make it difficult for users to distinguish between tasks, especially when dealing with resources that have many lines and a long planning horizon.
We propose adding a feature to configure alternating colors for each line in the Scheduler. This "zebra striping" will enhance visual distinction between tasks, making it easier for users to navigate and manage their tasks and resources, especially over long planning horizons.
2 votes -
Improved Week Navigation in Scheduler
Currently, when changing between weeks in the scheduler, it adds a week on top of the current day, rather than moving to the start of the next week (Mon-Fri). This behavior contrasts with the functionality when stepping to the previous week, where it scrolls back to Monday.
We propose modifying the week navigation in the scheduler to ensure that moving to the next week always takes the user to the start of that week (Monday). This adjustment will create consistent behavior when navigating between weeks and align more closely with user expectations.
2 votes -
Dynamic Date Filter Configuration in Gantt Portlet
The default values of the date filter in the Gantt portlet are currently based on today's date. This setup requires manual adjustments when looking at historical data, which can be cumbersome and time-consuming for users.
We propose adding the ability to configure the end of period default value based on the start of period value in the Gantt portlet. For example, if the start of the period is set to two months ago, the end of the period could automatically be set to two weeks after that. This dynamic configuration would enable users to more quickly and intuitively navigate through…
2 votes -
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…
1 vote -
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…
1 vote
- Don't see your idea?