186 results found
-
Overview/details change when running in Analytics/Automations
In Flow Connect Hub:
When looking in Analytics/Automations you can see the status of the scheduled automations which is great.
However when a job is during "running mode" you get a lot of lines with each step. My proposal is that you only have one line in the overview for each job and display it in status "Running". Then if you want the details you can click to the right to see details. I don't think details for running jobs are very important - just to see the overview better.
See attached img. Marked lines are all the same job…
1 vote -
Infor M3 Connector (NOT REST based)
In Flow Classic, we have two connectors associated with M3. One is the REST based connector, the other is connector to older versions of Infor M3. In Flow Connect, we would like the same capabilities from Classic. Currently, only REST based connectors for Infor M3 are available.
16 votesWe are happy to inform you that development work has begun on your requested feature. Our product team has assigned resources and is actively working on implementing it. We will keep you updated on its progress.
-
Push refresh of portlet
Have an option from an app/component to send a refresh command to a portlet for a specific user.
4 votes -
Uptime dashboard
Why
As a customer, I would like to have a traffic light/dashboard to view my system's uptime and identify any outages in my region.What
This does not have to be observability in the form of who ran what app and when. Rather, I just want to get the dashboard to confirm that my system is up and running, and also to view its historical data. Similar to what AWS or Microsoft have. Or qlik: https://status.qlikcloud.com/2 votes -
Voice Step
Using voice as input when executing a task is becoming increasingly more useful and also more requested, with the use of AI.
To make this experience smooth and seamless we would need a voice step which automatically or on demand (by pressing a button) starts a recording. The recording can be paused or stopped (or auto stopped after a defined number of seconds of relative silence). The recoding is then returned to the workflow and can be processed in the following steps, using AI.
2 votes -
GET endpoint with URL params for an Automation
In many use cases we need to be able to expose a GET endpoint, using URL parameters as input to the Automation App.
One general use case is callbacks, where a callback from a service is usually made using an http GET request.
Specifically we will need this when doing online payments (using web browser) where the payment confirmation/receipt is sent using a callback GET with url params containing e.g. order id or payment reference.
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.
-
Add advanced Crypto module in FlowScript
Some secure web services (like payments) are using hashed Authorization headers.
One example is Worldline, who states: "In short, our Server API authentication mechanism uses hashes over a number of headers (called Signature Contents) and your secret API key to verify authenticity. The hash algorithm used is HMAC-SHA256."
The example can be found here: https://apireference.connect.worldline-solutions.com/s2sapi/v1/en_US/json/authentication.html?paymentPlatform=ALL
For this reason, and to be able to access highly secure online services, it would be good to add a "Crypto" module in FlowScript to do these types of encryptions.
The Crypto module could then support encryption and decryption of commonly used algorithms.
1 vote -
Public User
Similar functionality to "Public user" used in Classic. Used for external users (customers, suppliers, etc.) to book appointments, etc., using a workflow (a public link is to the workflow)
14 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.
-
'optional' mode when generating a FlowSript module via the IFS Code Generator
The IFS API documentation has many fields in it Request Body Schemas wrongly labeled as 'required' in the input type definitions. There are examples where over 20 items are wrong within one schema. Since this is not going to change any time soon, it would be better to have the code generator define all fields as optional. Since typically a type is not defined from scratch but copy/pasted from the browser debugger console, it avoids a lot of unnecessary type issues in FlowScript for which the generated code needs to be adapted.
1 vote -
19 votes
-
Numeric input with plus- and minus-buttons
Especially for mobile clients would be useful if we would have numeric input with plus- and minus-buttons. Input need to have minimum and maximum values, with possibility to set button increase value. Example for inputting hours: minimum hour registration is 15min with 15min increase and maximum hours 8
Control setup:
Min value: 0.25
Max value: 8
Step value: 0.251 vote -
Status message on http requests and script steps
It would be very nice to be able to have a status message on also http requests and script steps (in addition to External System), as http requests potentially can take some time to execute.
3 votes -
Configurable Client Timeout
I would like to be able to configure a timeout in the client such that if the client is inactive for a specified period of time, the client will logout. As an example, at Cash Checkout if the screen has not been touched for 4 minutes, the app should logout and request a re-login. This should be a configuration.
1 vote -
Allow the use of "join" syntaxes in flow script modules
I noticed that the Join are not working on the SQL query on the flow
script when I use the module.2 votes -
Allow Alias for datasources
I noticed that the Prefix are not working on the SQL query on the flow
script when I use the module.3 votes -
OAuth2 Client Credential authorization in FlowHUB APIs
There are some cases when I'd call FlowHUB API from a workflow/automation and there is no way to use interactive authentication (machine-to-machine cases).
It would be great to implement OAuth2 Client Credentials for these cases.
With this option we could develop applications to maintain FlowHUB (e.g.: fetch users by group, invite users, move apps, generate bundle, etc).
1 vote -
Show file extension in File Gallery
In File Gallery element, it would be great to show (or enable to show) the whole filename value, including the file extension.
For example, in the file gallery I have a couple of files shown, but I want to download only the excel file. Without showing files' extension, I have to download all of them to figure out whihc one is that filetype I'm looking for.1 vote -
Dynamic login/password for IFS connector
Client accessing IFS via Flow Connect wants to be able to restrict access to some tables, even for developers. In Flow Classic you could set up connector so user was simultaneously login in to IFS and Flow, so he was not using IFSAPP user to gain access, but his own level of privilege. I'd like to be able to present to client's similar functionality, since currently we can set up connector with single login/password per environment.
Moreover login with multiple flow users in single IFS user seems like license issue waiting to happen.1 vote -
Iterator field in e-mail connector machine steps
I'd like to send e-mail to multiple e-mail addresses.
To send individual e-mails, I need to create a loop in flow to iterate on the users' data (I don't want to send the same e-mail content to all users - e.g. name or company name is different for all users, etc.).It would be useful an iterator feature in the machine step similarly to machine steps where an SQL connector is selected. See attached pictures.
2 votes -
Improve screen transitions
There is an issue with screen transitions in both Flow Classic and Connect. Currently, users scan a barcode into a text input field using a scanner. After scanning and selecting "Next," the input field remains active, allowing users to continue scanning or typing even while the query is executing. This behavior is consistent across both Flow Classic and Connect.
Ideally, once a barcode is scanned and the transition or query is triggered, the input field should be locked or disabled to prevent further input until the process completes. This would help avoid confusion, as users might mistakenly believe that multiple…
2 votes
- Don't see your idea?