15 results found
-
Infor M3 Connector (Socket)
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.
-
Enhanced Logging for Import Errors of OData Connector
Users encounter an issue when changing connectors for a specific flow. Currently, when an operation result indicates a failure, it is challenging to pinpoint which step within the flow has encountered the issue. As a result, users are compelled to manually review each step to identify the failed ones, causing unnecessary delays and frustration.
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.
-
Web Service Connector in Flow Connect
Support for Web Service Connector in Flow Connect
7 votes -
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 eq and in operator on the same entity
we would like to use both the eq and the in operator on the same entity within a set and if the IN operator consist of only one “value” then the connector will crash and give the following error “Operation failed. Multiple key predicates cannot be specified for the same entity set.“ but if you set more than one “value” it will work as intended.
4 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.
-
OPC UA connector in Connect
he OPC UA connector allows Flow Connect apps to communicate with OPC UA servers
3 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.
-
Update Web Service connector with new WSDL file once connector has already been setup on Cloud
Currently a WSDL contract is necessary when creating the connector. However, once the connector is set up, it doesn't need ongoing access to the contract. On an on-premises server setup, the contract could simply be placed in the file system and accessed from there. However, on a cloud setup, direct file system hosting isn't possible.
One suggestion is using a file system connector, which would allow users to upload the file onto the cloud server and then point to it. However, this approach is somewhat unconventional and a bit of a “rouge style”. An additional layer of complexity exists if…
2 votes -
Print Connector
Generating Reports and labels in Flow seems to be an ever increasing use case.
We have some tools (e.g. HtmlToPdf, the consulting developed Document Management or external services like Convert API) to generate reports and labels, but we are missing a way to get them printed if needed.
For this use case it would be very useful to have a Print Connector, where it would be possible to send a printable file to a printer.
Please fix. Thank you.
1 vote -
Telemetry on Concurrent Sessions
As a developer or admin of an organization, I would like to see how many concurrent sessions are being utilized in a given period on each agent to determine if I need to add more agents to an agent group for better performance.
1 vote -
Better Agent Traffic Management
As a customer, I would like to be able to push a certain amount of traffic to an agent within an agent group. As an example, I can have 2 agents in an agent group for prod. When updating Agent 1, before updating Agent 2, I would like to push 75% of the traffic to Agent 1. This would allow me to see that the Agent is working adequately before updating Agent 2.
1 vote -
More Agent Traceability
As a customer, it would be nice to see exactly what APIs are called on the Agent logs. Currently, we can only see the APIs outbound and inbound in the Diagnostic mode client. But we would like to be able to see all the APIs including payloads and responses inside the Agent Logs for traceability.
The amount of days logged should be configurable and searchable.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 -
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 -
Feature to log REST calls
It would be nice if we could log somehow if an enduser run a workflow and during a REST call an error occurs, then later a developer could check these log files. Or if the issue is not reproducable in DEV environment, only in PROD/TEST env. (like a similar functionality in Flow Classic).
A use-case from partner:
"If the user experience problems occasionally and we can’t recreate it in the debug.
Another example, sometimes when I get long responetimes during testing I cannot see if that is because of M3 or not. Next time I run it it is quick…1 vote -
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
- Don't see your idea?