239 results found
-
Enhanced Flow History Management
The current system lacks efficient mechanisms for managing flow history, particularly in environments with numerous flows and versions. This leads to performance issues due to the accumulation of extensive history data. Additionally, the need to update flow IDs on the portal after importing and exporting flows complicates maintenance and disrupts workflow continuity.
Proposed solution is to implement a configurable option within the web configuration file to set a limit on the number of flow history entries retained, defaulting to the latest 10 entries. This setting would allow users to manage performance by controlling the volume of historical data stored.
Furthermore,…
2 votes -
Improved Version Update Mechanism in Studio
Currently, when an error occurs in Studio, such as "Item is not linked to the latest version," clicking on the error message automatically opens the fragment. This behavior is not always helpful, especially when the needed action is to update the version rather than edit the fragment. The limitation is compounded by the fact that version updates cannot be performed while the workflow is open in edit mode.
Proposed idea is to revise the error interaction process to better align with the user's likely intent. Instead of automatically opening the fragment for all types of errors, provide a more nuanced…
2 votes -
Able to Fetch Information from Task when Creating New Work
When a field technician is involved with ongoing tasks, there could arise a need to create additional work. The existing IFS Marketplace app 'New Work' is a standalone app used for fault reporting purposes. However, in most use case scenarios, technicians tend to create new work (assignments) while performing ongoing assignments. Hence, it is beneficial to have the option to copy task information on to the new work to minimize re-entry of data.
1 vote -
SFTP Trigger in Integration Engine
It would be good if integration engine could handle incoming files via SFTP. We encountered this need in our very first integration engine project.
1 vote -
Mandatory Offline Data Update Prompt
The feature in question is the "Offline Data Update Interval" setting, which prompts users to update their offline data after a specified time interval. While this functionality is beneficial in maintaining up-to-date data, we observed that users have the option to dismiss the update prompt by clicking "No" and proceed with launching the flow without refreshing their offline data.
We have tested this behavior in the Windows 10 Flow Client, where we configured the offline data update interval to 1 hour. As expected, we received the "Offline Data Expired" notification when the interval elapsed. However, we found that clicking "No"…
20 votes -
Create WSDL File for Integrations
If we provide an endpoint capable of handling XML files customers are expecting a WSDL file documentation. IE currently cannot generate this. We need an automatic function to create this.
1 vote -
The possibility to handle errors in some connectors
In some connectors for example FileSystem we need the ability to handle errors and sometimes ignore them.
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.
-
Validation for Expense Report Header Deletion
In the app Review Expense, there is an option to delete an expense line from an expense report. If the user deletes all lines (i.e. want to cancel a report) the header is still active and is visible in the app for the user in the first user step (LOV with open reports). That can be a bit confusing. Suggestion to add a validation with a question to the user after the last line of the report is deleted “You are deleting the last line of the Expense report, do you want to cancel the Expense report?”. If YES then…
1 vote -
No pop-up message for mobile links
When a generated flow link is pressed on a mobile device, an pop-up message appears, asking the user if they want to start the flow.
1 vote -
Text and TAB alignment from Right to Left
Hi,
Thanks for this forum to share ideas.
We have an existing client engagement where client wants to explore below options.
show the tabs ,buttons in a portlet to be aligned right to left
all text to be shown and to be entered from right to leftThis requirment is very common in teh middle east region clients and as we don't have any existing feature to in-corporate teh same, can we check teh pheasibility and develop something similar.
Regards,
Bhaskar2 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 -
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"3 votes -
Facilitate Binary flow script function
We would like to have a feature to facilitate encode/decode Base64 with flow script function and be able to convert a flow variable to a binary file format.
3 votes -
Workflow Configuration
With this feature, Flow users will be able to create and configure workflows within IFS that enables more resilient assignment state management.
Workflow configuration is heavily used by field service technicians to modify a given workflow to suit their business requirements. It also helps end-users navigate through the work assignments more easily.1 vote -
Inventory Part Availability for Work Task Material Allocation
Field technicians should be able to see the available part quantity in inventory for a selected part, prior to allocating material for a work task. This would intern provide a better overview in planning and executing the task.
1 vote -
Seamless process to clean up treasure files
we would like to have schedule cleaning jobs that clean treasure files and what is now saved on the server.which would maybe feel more safer and reasonable if we’d be able to write this from the Studio
3 votes -
New Status set Manually
We want to be able to set a new status on an integration execution. That status would set manually and could be called "Handled". This means the integration execution needs no further action on our part.
2 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.
-
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 -
Progress bar UI element
When doing complex operations in Flow, either as a loop of machine steps or as a machine step with an iterator, the user is left in the dark about what is happening. It would be great to be able to present the user with a progress bar that gradually fills while Flow is processing the operations. This could be a special User step that requires no interaction from the user and disappears when the process is done. Inputs would be a counter variable, a total of the number of operations and a user message detailing what is going on.
A…
8 votes -
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
- Don't see your idea?