245 results found
-
Auto-incrementing Variable in MAP AS Function
The MAP AS function has proven to be an invaluable tool for us to streamline our workflows and avoid using cumbersome for loops. Nevertheless, we have run into situations where we were forced to switch back to using for loops due to the absence of an auto-incrementing variable within the map function.
To elaborate, we frequently encounter scenarios where we need to remap filenames within a FileGallery to conform to specific naming conventions or add suffixes like "Pic 1," "Pic 2," and so on. Currently, this cannot be efficiently achieved using the map function, as there is no straightforward way…
2 votes -
OData Filter an Entity Set based on Related Entities
At present, the IFS OData connector does not have the capability to filter an entity set based on related entities. Although the UI might suggest otherwise, it is important to note that any attempts to filter in this manner will not be saved in the Workflow.
The current workaround is to use the Code method included in the connector.
2 votes -
Enhancements to Register Arrival Workflow in Novacura Marketplace App
Propose improvements to streamline the Register Arrival workflow. Key enhancements include implementing a multi-select feature for line selection to handle shipments with multiple lines, enabling the addition of received lines to an existing Handling Unit (HU), and modifying the Select Order step to display the supplier name (and optionally the supplier number) instead of the generic 'Purchase Order' label. Additionally, introduce options at the workflow's end to either continue receiving lines on the same Purchase Order (PO) or select a different PO for further processing.
1 vote -
Supplier invoice authorization
Request for a Marketplace app for Supplier Invoice Authorization.
It is quite common that customers ask for an app to authorize supplier invoices.
Basic functionality like approve/authorize, add/edit notes and change Invoice receipient.1 vote -
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 -
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 -
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 -
Material release through connected part sites other than the Work Task site
Enabling Technicians to release material not only from the task connected site, but also through other connected site warehouses.
1 vote -
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 -
Option to Suppress Subscription Notifications for Disabled Environments
In instances where a TEST environment is disabled while PROD remains subscribed to TEST, users encounter a barrage of subscription notifications, disrupting workflow in PROD Studio. To mitigate this, we propose implementing a feature that provides users with the option to suppress subscription notifications temporarily. This could include a warning prompt with the choice to suppress notifications for the current session or for a customizable duration, such as 24 hours, ensuring uninterrupted productivity during critical work periods.
1 vote -
Export Logs Directly from OData Connector to CSV or XML
We request the functionality to export logs directly from the OData connector into CSV or XML format. This feature would streamline data management processes by allowing users to extract logs efficiently and in preferred formats, enhancing accessibility and usability of logged information.
1 vote -
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.
-
Unified Interface Layout for Consistent Navigation in Inbox
Requesting the option to standardize the visual presentation of the Inbox button to match the flat layout of other interface elements. Currently, the raised "depth" of the Inbox button stands out and lacks consistency with the rest of the interface. Providing a toggle or setting to align the appearance of the Inbox button with other buttons would enhance visual coherence and streamline navigation for users.
1 vote -
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…
1 vote -
Consistent Link Widths: Improve Visual Harmony in NG WebClient
We propose a feature enhancement to address the inconsistency in link widths within the NG WebClient. Currently, varying link widths create a visual disparity, particularly when compared to mobile clients. To enhance the overall aesthetics and maintain visual coherence across platforms, we request the implementation of a feature that ensures consistent link widths in the NG WebClient. This adjustment will contribute to a more polished and uniform user interface, providing a seamless experience for users across different devices.
1 vote
- Don't see your idea?