135 results found
-
FTP Connector in Connect
To be able to communicate with FTP servers in Flow Connect. The FTP Connector can be used to upload and download files from an FTP server. It can also perform other operations such as creating remote directories and list files and directories on the FTP server
8 votes -
AD Sync (SCIM) for Flow Connect
System for Cross-domain Identity Management (SCIM) is a set of application-level protocols that use JSON, REST, and several different authentication methods to automate the task of user provisioning. This will allow Admins to configure Azure to create, update, and delete users seamlessly from Azure AD to Novacura Flow Connect without the need of manually doing this within the Hub.
15 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.
-
SFTP Connector in Connect
To be able to communicate with SFTP servers in Flow Connect. The FTP Connector can be used to upload and download files from an SFTP server. It can also perform other operations such as creating remote directories and list files and directories on the SFTP server
11 votes -
Scheduler Portlet in Connect
Support for the Scheduler Portlet in Novacura Flow Connect
9 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.
-
Generic Database connector with ODBC
A generic database connector that can connect to any database for which an ODBC driver is available
Databases that we can Connect to via ODBC
IBM Db2 (all variants)
MySQL / MariaDB (MySQL Connector/ODBC, MariaDB Connector/ODBC)
PostgreSQL (psqlODBC driver)
SQLite (SQLite ODBC driver)
SAP HANA (SAP HANA ODBC driver)5 votes -
Liquid & XLST Transformers for automations
All ow automations to perform transformations on input and output for webhook triggers so we can support current classic customers in connect
6 votes -
2 votes
-
On-Premise (onprem) Runtime
Some customers need to run Flow Connect on their premises (on-prem) for different reasons.
Data requirements – Strict data security/privacy/legal requirements where the data is not allowed to leave the premises. For these types of customers, it is essential that everything runs on-prem since they don’t want any connection to the outside networks.
Some examples:
• Aerospace & defense
• Defense manufacturing
• Healthcare
• Government and public sectorLow-latency requirements - Some customers have low-latency requirements with systems handling a high volume of transactions/executions. Typically, their existing infrastructure/external systems are already on-prem due to the exact reason. For these…
22 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 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.2 votes -
Public User
Public user is used in Classic for external users (customers etc) to book appionmetns using a workflow (a link is sent out in email/sms)
2 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 -
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 -
Bring Your Own Identity Provider
In Flow Connect, we would like to be able to use other identity providers to login. For example, we would like to be able to login via OKTA instead of Microsoft.
2 votes -
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 -
'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 -
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.
1 vote -
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 -
Manual re-compile all enabled projections in OData connector
In the context we hae customers like Elvia and soon DSB where flow is having a usage of 300+ projections. With frequent updates in IFS ( ever green with new releases every 6 month and service updates in addition). The projections needs to be recompiled one by one. This is timeconsuming and have a risk of not handling it correctly.
I would be great and useful to add an option/button/way to easily re-download the metadata of all enabled projections and re-compile them in OData connector.
Especially, after an update of IFS, it would be great to do it manually.
Even…
11 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.
- Don't see your idea?