240 results found
-
Generative AI - Flow Component and Workflow Creation (GPT)
In the ever-evolving landscape of app development, speed and adaptability are paramount. Our proposal aims to empower Flow developers with a Generative AI Copilot, capable of swiftly building components of an app and facilitating real-time modifications, all through natural language conversations.
Key Benefits:
Rapid App Component Creation:
The Generative AI Copilot enables developers to efficiently construct app components, eliminating the need for time-consuming manual coding.
End-to-End App Creation:The Copilot can autonomously generate entire applications from scratch using OpenAI and Generative AI technologies, significantly reducing development timelines.
Adaptive Modification:Developers can request real-time adjustments to the app via natural language…
1 vote -
Business Process Mining from Telemetry Data
As Flow Developers, we often find ourselves striving for optimal workflow efficiency and effectiveness. To facilitate this, we propose a feature that combines two essential elements: enhanced flow analytics and seamless Copilot integration.
Key Benefits:
Route Performance Insights:
Percentage-Based Route Usage: Flow Developers can gain valuable insights by visualizing the most frequently used routes within a workflow, presented as a percentage. This helps in identifying bottlenecks and optimizing workflow paths.
Average Time Tracking:Time Spent Between Workflow Steps: Users will have the capability to track and analyze the average time spent between each step of the workflow. This empowers developers…
1 vote -
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 -
Offline Accessibility of Offline Menus Without Internet Connection
Users have experienced issues with the Offline Menu feature. Even after downloading offline data in the morning, if a user tries to refresh the offline menu for their offline inbox while not connected to the internet, an error occurs. The error message suggests that the internet connection is offline, which is perplexing given the data has already been loaded onto the device.
Proposed solution is for the Offline Menu and its related features (like the offline inbox) should be fully accessible and operational without an internet connection once the data has been loaded. This means that even if a user…
1 vote -
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 -
Connect function key (F5) to button
I would like to be able to connect a function key (for example F5) to a button in a flow, which could be for example, the 'Refresh' button.
1 vote -
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 -
Auto Navigation between pages in portal 2
We would like to have a new function where the portal 2 pages navigate automatically within given time period
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…
2 votes -
Enhanced Label Editing for Studio Elements within Flow Element Itself
In the current system, editing the label text of a canvas element requires double clicking on the element in the canvas view. This method can be time-consuming, especially when designing intricate flows. Moreover, without immediate renaming during the design phase, elements can end up with generic labels like “Machine Step”, “Machine Step [1]”, etc.
We propose to introduce an option to edit the label text directly when in the edit mode of a canvas element. This enhancement would provide designers the flexibility to rename elements on the fly, ensuring clarity and reducing the likelihood of generic, repetitive labeling.
3 votes -
Change SQL validations in Studio
We frequently execute numerous queries on our M3 IBM DB2 iSeries database, and occasionally, I encounter issues where Flow Studio does not accept the query.
We've been able to adjust queries in the past to make them compatible with Flow Studio, but this time I'm facing difficulties. The problem specifically arises on line 7 of the query.
We make extensive use of "with" statements, so it's puzzling why I'm encountering an issue in this particular instance. It's possible that the problem is related to the brackets I'm using to dynamically insert parameters into the query, but despite the error, everything…
3 votes -
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 -
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 -
Evergreen IFS Rest Odata calls
In the IFS Odata Connector we would benefit from first of all identification of all Odata projections used in a a flow and secondly to scan the IFS APIBreakingChanges release files to find out and mark Flow objects if there has been a change in any projection.
There are two different APIBreakingChanges files:
- Between Service Updates within a functional Release
- Between Functional releases.
See attached examples.
8 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.
-
Generative AI - ChatGPT Connector
It would be helpful to have a ChatGPT Connector and templated process to use this connector. For example, using ChatGPT to create FlowScript based on natural language, personal recommendations based on Portal 2, document summarization in Portal 2. This connector should be set up to allow developers to see an example of how to use it, but be able to embed this connector into their own apps.
4 votes -
Enhanced Logging for Import Errors of OData Connector
Users encounter an issue when changing connectors for a specific flow. Currently, when an operation result indicates a failure, it is challenging to pinpoint which step within the flow has encountered the issue. As a result, users are compelled to manually review each step to identify the failed ones, causing unnecessary delays and frustration.
8 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.
- Don't see your idea?