290 results found
-
Add proper Report Print Layout configuration to Flow
There is a need for proper Report Print Layout configuration. Must allow dynamic sizing of all cells in a table/layout, logo, formatting, conditions etc. Today's HTML is far to rigid. For some use cases the layout is so poor that we can't even use it internally, not to mention externally.
Main need is for PDF, e.g. Word would have been nice, but less important
Ideally there should be an engine on the backside, allowing to be automatically sent on E-mail or printed to predefined print.
For IFS users, similar IFS Report Designer and Print Agent. The built in IFS tools…
6 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.
-
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.
2 votes -
Enhanced Targeted Messaging Capabilities in Flow Server
Requesting an expansion of the Flow Server messaging functionality to support targeted communication beyond global message sends to Portal. While acknowledging the utility of global targeting, there's a strong need for more precise messaging options such as targeting specific Flow user IDs, user roles, and user workflows. This enhancement would significantly empower communication in multi-user setups, providing greater flexibility and efficiency in message delivery within the Flow environment.
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,…
2 votes -
Change back symbols for arrays to []
In current version of FlosScript {} symbol is used for declaring arrays(Pic A), inside IF and FOR loops(Pic B) and to showcase when Flowscript will be used(Pic C).
I think, using same symbol for everything makes it's purpose unclear and can cause unnecessary confusion. Was change from [] to {} for array declaration cause by some real need?
2 votes -
Can items remain highlighted once clicked on them?
Is there any way that when adding records for an employee, the name stays highlighted. After each record I enter, I have to re-click on the name to enter more or even see anything pertaining to the employee.
the user wants the name to be able to remain highlighted while they are doing processes for named user until the processes are completed instead of having to click on the user name each time to create additional processes for them.
2 votes -
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.
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.
-
Enable listener for Record Portlet
Please enable the posibility to listen to the Record Portlet. We offer the possiblity to change data via Workflow, but any saved changes will never trigger an update of other portal objects. This needs to be done manually. I have encountered this in at least 4 projects now where this feature would have been needed.
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 -
"Finished" Status Visibility when Offline on Flow Inbox Items
In the current Flow mobile client, when operating in offline mode, users face a restriction where items in the inbox are marked as "Finished" after being acted upon. This status change makes the items inaccessible for further review, although they remain visible in the inbox until the user reconnects to the internet. This behavior limits the ability of users to revisit completed items for verification or review purposes.
Proposed solution is to implement a feature allowing users to toggle the visibility and accessibility of items marked as "Finished" in the inbox while in offline mode. This functionality would enable users…
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.
-
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 -
Extend binary option input user step element
It would be great to have a radio button 'list' input, like Binary Option Input, but more than 2 available options.
Like a combination of Menu Selection Input and Binary Option Input: functinality from menu selection, interface like binary option input.
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 -
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.
2 votes -
Option to make a cell read-only or editable in a DataGrid
It would be nice to have a feature that can make a cell in a grid read-only or editable with a similar option to 'Cell Color'.
For example, if the contidion is true/false , then the cell is read-only or editable.
On the attached picture, yellow cells are editable, white cells are read-only.
Now, both 'Value' and 'Value List' columns are editable.3 votes -
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 (and other datagrid elements) 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,…
9 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.
-
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.
-
Allow word wrapping on scheduler cards.
Allow word wrapping on scheduler cards. If my label goes too far right, it just disappears.
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.
-
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.
3 votes
- Don't see your idea?