279 results found
-
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.
3 votes -
Update the version of the SqlParser
Update to the latest version of the SqlParser For Special SQL Server Functions such as string_agg([Column], [separator]) function in combination with "WITHIN GROUP (ORDER BY [Column])"
3 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.
-
Duplicate a Component in Hub
I want to be able to duplicate both package and organization components. If a component with sub components is duplicated, it should keep the existing references.
3 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.
-
Native Data Layer
Our users seek more flexibility and independence in their application development, it becomes crucial to provide them with a native data storage solution that is seamlessly integrated into the Flow environment. This feature would empower users to set up and manage their own databases directly within Novacura Flow, offering a level of control and customization that aligns with their specific application needs.
Key Benefits:
Simplified Data Management: Users can create, modify, and manage their databases without the need for external database systems, simplifying the entire data management process.
Enhanced Security: By providing an integrated data layer, Novacura Flow can ensure…
3 votes -
Selective Column Search in Data Grids
In the current implementation, the data grid search functionality searches through all columns, including those that aren't displayed in the data grid or are not set up under "Edit columns."
Proposed solution is to introduce a customizable search functionality in data grids where users can selectively choose which columns to include in the search. This can be achieved by adding a checkbox option under "Edit columns" labeled as "Searchable". By default, all columns can have the "Searchable" checkbox marked to ensure compatibility with the existing behavior. Users can then choose to deselect certain columns if they don't want them to…
3 votes -
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…
3 votes -
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…
3 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.
3 votes -
Allow developer to connect one flow to multiple buttons in Portal 2
We would like to use the same flow for multiple buttons in Portal 2. We use the input table to drive what the buttons do. Therefore, we would like to have that functionality in Portal 2 to connect one workflow to multiple buttons. Today, I need to duplicate the workflow to connect one button to one workflow. This adds unnecessary maintenance.
3 votesThe feature request has been approved and is now scheduled for development. Our product team has determined that it aligns with our product roadmap and will bring value to our platform. We will keep you updated on its progress.
-
Enhance 'checkpoint' workflow element
We use at lot of Assertion Steps in our Flow to alert users that something went wrong. On typical example is that we usually compare the the input to a list of items. If it don’t match, the user gets a error.
The problem with Assertion Steps is that the user have to click to remove the popup window. To be more efficient, a temporary popup would sometimes be enough.
We can accomplish this using the Checkpoint-step and write text that covers the whole screen, as seen in the picture.
But it would be nice to make this popup red,…
3 votes -
Include previous entries as suggestions in text input fields
Our goal is to enhance the filterportlet by adding text input fields that offer auto-suggestions in the form of a drop-down list, displaying previous entries. This feature is already available in portal1. Users will experience a more user-friendly and efficient filtering process, as they can conveniently select from past entries suggested by the drop-down list.
3 votes -
Personal Saved Searches in Filter Portlet
Users desire a feature that allows them to save personal search parameters within the Filter Portlet, similar to the functionality provided in IFS. This will enable users to quickly reuse complex filters and searches, enhancing their productivity and efficiency.
3 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.
3 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.
3 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.
-
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…
3 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.
3 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.
3 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…
3 votes -
Improve 'Menu Selection Input' Workflow element to limit screen touches
When there is a menu selection in a user step, we need to click on it to enter text. Previously, we could simply type to make our selection.
3 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
- Don't see your idea?