236 results found
-
Offline WADACO (Warehouse Management) Functionality
IFS WADACO application and Novacura WM application does not work in offline mode.
It will be great if Novacura could include some of the WM apps with offline functionality.
Eg: Certain WADACO transactions such as Counting, Moving, Execute transport tasks etc.2 votes -
Chat User-Step Element
It would be ideal to have a chat user-step element that could be configured in Flow. This would allow us to more easily use GPT in a dynamic way inside of the Novacura Flow Client.
3 votes -
Request for Enhanced Timestamp Resolution in Logpoint Data
Requesting an upgrade to the timestamp resolution in logpoint data beyond seconds to milliseconds. Currently, the timestamp value retrieved from logpoints is limited to seconds, hindering detailed analysis and synchronization with higher resolution systems. Expanding the resolution to milliseconds would align with modern data processing requirements and enable more precise temporal analysis within the system.
1 vote -
Improving API Execution: Scanner Event Optimization
We utilize scanner events to scan barcodes, extract item numbers, and retrieve item descriptions, locations, and stock balances. While this process generally works fine, we've noticed that Flow attempts to execute the API for connector steps even before scanning.
In the screenshot provided, you can see that there are three APIs that utilize the scanned item number to collect data. These APIs are triggered when the user step is displayed for the first time, even if the item number is blank. This leads to issues and longer response times.
If we bypass scanner events, the APIs should still run. However,…
1 vote -
Add timeout error Handling for REST APIs
Currently, while flow 6 connectors handle REST-API errors based on status codes, they fall short in handling timeouts. A feature that handles timeouts would greatly improve our application's error management.
1 voteThank 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.
-
Unlock locked user accounts in Flow with API
I would like the possibility to unlock locked user accounts in Flow environment via API.
As of now, our Servicedesk needs to have Studio installed and reserve one admin licence just to be able to support our organisation.
Thanks!
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.
-
Enhanced Marketplace app attachments
Two things to report regarding attachments when creating an Expense Report.
The attachment type is set to MEDIA, that limits us to certain file types. Sometimes the user wants to add a PDF document, but that is not possible.
One of the final steps in the app is to attach a document (if that exists) to the expense row that was just created. Here step “Get Expense Details” fetches all expense rows, and the next assignment step fetches the first row {FirstOrEmpty(ExpenseDetailResult.Results)}. This first row is then used to create a keyref in the next step. The problem is that…
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.
-
Make it easier to write "Text"
To present relevant information our users, we type a lot of conditions and display variables practically everywhere. On arrows, in headers, in texts, in prompts and so on. Those fields can not be "opened" like a script-field (Condition To Hide) and when you try to navigate left or right in that field, it jumps around a lot.
Development is overall fast in Flow but those finishing touches that makes a good applikation great takes time.
Can we get the possibility to open these fields up to speed up development?
Thanks!
And I guess you already got a request to make…
2 votes -
Enhanced Data Visualization: Color-Coding for Data Grid Portlet Columns
We request the implementation of a new feature that enables users to apply color-coding to columns in data grid portlets based on a comparison against neighboring column values. This enhancement will provide users with a visual representation of data variances, facilitating quick and intuitive analysis within the platform.
5 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.
-
View Data Grid columns without being in edit mode
It would be nice to be able to view data grid columns without first having to be in edit mode in studio. As it stands, when you select a datagrid element while not in edit mode, it only previews the column names in that boxed area, and depending on the length of the names, only shows a few of them. It would be super helpful if we could go a layer deep to view each column, it's data source, and perhaps just the entire edit screen in general without having to officially open it up for editing.
10 votes -
SOAP Service OAuth2 Password Credential Type in Design Time
Currently, the SOAP Webservice connector supports OAuth 2 Password Credentials Type in Design Time. However, there are instances where you need to authorize to an HTTP GET endpoint to get the WSDL definition. The workaround for this issue is to currebntly put the WSDL file on the server so authentication is not required to generate the connector. But it would be ideal to apply the current OAuth2 Password Credential Authorization to the WSDL retrieval GET operation.
1 vote -
Update dependency for fragment: Add Fragment comment to updated versions
When changing a fragment and updating dependencies it can be VERY confusing to follow the changes in Flows that have been changed.
In complex flows using a lot of fragments, some flow specific and some used in a lot of flows, when i do changes and want to update PROD i can frequently see that between my changes and the last shared version to PROD other changes have been made, but i cannot see a comment other than "Auto updated version dependencies". If there is a comment in the changed fragment, please use that comment in all dependencies as well,…1 vote -
Connect pins in Map Portlet
When I have multiple pins in the map portlet, it would be great to select a group of them or being able to connect two pins. These two pins could then be the input for a machine flow that calculates the time of travel via rest call.
This would help to use the portal for planning.3 votes -
Group Connectors in Machine Steps
When you have a considerable amount of connectors it is not that easy to locate the connector you are looking for. If connectors can be grouped based on the type and then sorted alphabetically within the group will add immense value to the flow developers.
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.
-
Add scale function for ODATA document management
New scale function was developed for media items. But most customers use document management also for images. This idea is to also make it possible to scale documents stored in document management. It could be configured to be up to the developer what kind of documents is scaled, but of course also if making a general functions so that if a word document is sent in to the function, then the document should not be scaled.
1 vote -
Checkbox Selection in Data Grid on Flow Mobile Clients
Users of the Flow mobile application face a limitation when interacting with data grids that contain checkboxes. Currently, to select a checkbox within a data grid column, users must navigate into each individual row and then set the checkbox. This process is seen as cumbersome and inefficient, especially for tasks requiring multiple selections across several rows.
The proposed solution is to introduce the functionality that allows users to directly select checkboxes from the main view of the data grid, without the need to navigate into each row. This enhancement should apply to all Flow mobile clients, streamlining tasks that involve…
5 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.
-
Remove warning messages
we would like to get rid of unnecessary and misleading warning messages when updating flows up the dependency chain
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.
-
colors/branding in studio to distinguish connected server
Please allow us to brand/color the studio based on the connection.
I frequently work in different flow environments and it is really easy to switch to the wrong studio window.
If I could either
1)set the branding on the server level so all studio logins for that server had the same color/branding whatever
2) or set the branding locally in studio...that would be great
My thoughts are
1) Allow for the studio header/border to be a different color
2) Make the SERVER I'm connected to more prominent, like in the same area as "Application/Environment/Monitoring"4 votes -
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.
2 votes -
Enhanced Warning Message for Application Exit in Flow
Currently, the warning message displayed when a user attempts to quit an application in Flow may not be sufficiently informative or persuasive in communicating the potential consequences of exiting, such as unsaved changes being lost.
1 vote
- Don't see your idea?