244 results found
-
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.
-
Improving Datagrid Row Addition
After appending a new row to a datagrid, the new row insertion occurrs at the concluding section of the DataGrid, even though my current view is confined to page 1. This outcome holds the potential to bewilder users, as it contrasts with the anticipated experience. When a user undertakes the action of appending a new row to a DataGrid, it is a logical expectation that the newly added row should be prominently visible upon transitioning to the creation interface. To align with this user-centric principle, it is recommended that a design modification be implemented to guide users to the end…
1 vote -
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 -
Show Password Icon
Currently, when logging into the mobile Flow application, users input their passwords into an obscured field. This feature request proposes the inclusion of an option to show the password while typing to aid users who may struggle with entering their passwords correctly when they can't see the input.
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 -
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.
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 -
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.
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 -
Custom Timeline in Scheduler
Currently, the Scheduler lacks the ability to create a custom timeline, making it difficult for users to plan orders starting in one week/month and ending in the next week/month. This lack of functionality can lead to a lot of clicking and scrolling and difficulty in visualizing the total order.
We propose adding a feature that allows users to define a custom timeline in the Scheduler. For example, this could be a timeline starting from 'today + 1 week' or other similar custom periods.
This will allow users to have a more efficient and streamlined planning process, minimizing the need for…
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 -
Configuration Changes to "Work Start" and "Work End" in Scheduler
In the current scheduler, the work hours are differentiated with a white background color (class e-work-hours), while the rest of the cells are light grey. The work hours seem to be hard-coded to 08:00 - 20:00, and no configuration settings are found to change them. Though there are settings for "Work start" and "Work end," they only control the display of columns and not the differentiation of work hour cells.
We suggest enhancing the scheduler by allowing the "Work start" and "Work end" settings to define which cells are given the class e-work-hours (and thus, the white background). This will…
2 votes -
Enable Copying of Error Messages
The aim of this feature request is to enhance the user experience and debugging efficiency by allowing users to copy error messages. Currently, when an error occurs, the message is displayed in a pop-up or inline notification. However, the text of these error messages is not selectable or copyable.
2 votes
- Don't see your idea?