243 results found
-
Distinctive Column Naming in Flow Studio Variable List
In Flow Studio, users encounter a challenge where some column names appear twice in the variable list without any indication of their originating table. This lack of distinction can lead to confusion and potential errors in selecting the correct variable.
Proposed solution is to enhance the variable list display to include the source table's name along with the column name. This will enable users to easily distinguish between variables with the same name but from different tables, thereby reducing confusion and improving accuracy in variable selection. Implementing this feature could involve a format like "TableName.ColumnName" or a similar approach that…
2 votes -
Concurrent Login Capability for Admin Users Across Multiple Platforms
As a consultant/developer, managing multiple clients often requires logging in and out frequently due to the limitation of one user/license per session. This process is time-consuming and inefficient.
Proposed solution is to enable admin users to be concurrently logged into multiple platforms - namely the Portal, Flow Client, and Flow Portal - without the need for separate licenses for each. This will streamline workflow management for consultants and developers who regularly need access to multiple clients or sessions simultaneously, significantly enhancing productivity and user experience.
2 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])"
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.
-
Portal2 Gantt schedule sorting
Portal2 Gantt sorting by click on one of the columns presented. Example: Standard sorting is to sort by work task number. One of the columns shown is equipment object id or department and the user wants to sort by Equipent object by click on that column. (or date, or department, or priority etc)
2 votes -
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…
2 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…
2 votes -
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 -
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 -
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.
-
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 -
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,…
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 -
Ability to disconnect quickly from environment in Client
When we need to switch in the NG Client from one environment to another (ex : from prod to test) we have to do the following:
click three dots
click sign out (why make this two steps?)
click yes to confirm logout
click disconnect
click yes to confirm disconnect
then click prod link
In previous versions of flow, we could just click a favorite and go to the other server.
There needs to be a much quicker way to a) signout and b) disconnect and get to the main page.
Ideally, there would just be a disconnect link within flow…
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
- Don't see your idea?