19 results found
-
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 -
Facilitate Chinese language in HTML2PDF connector
When incorporating Chinese characters into a document flow in Novacura cloud, some corruption issues arise, often due to missing fonts.
6 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.
-
Implement Timeout Parameter Support in Novacura's IFS10 Connector
The IFS .NET Access Provider is expected to support a timeout parameter, allowing users to configure how long a task should wait before timing out. However, this functionality is not currently implemented in Novacura's IFS10 connector. As a result, all long-running tasks time out after one minute, with no available option to extend this limit.
This limitation hampers the execution of tasks that take more than one minute to complete, making it impossible to include them in flows. This leads to inflexibility in designing complex workflows and might impede the completion of important business processes.
We propose implementing the timeout…
6 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.
-
As a user, I want the Batender connector to support the 64-bit version of BarTender, as it currently only works with the 32-bit version of
As a user, I would like the Bartender connector to add functionality for the 64-bit version of BarTender, as it currently only supports the 32-bit version of BarTender 2016 R8 (Automation or Enterprise Automation Edition).
3 votes -
Enhanced Log Analysis Tool for REST M3 API Connector
We urgently request an upgrade to the existing log analysis tool for the REST M3 API connector. Currently, the tool lacks the essential capability to efficiently search for specific transactions or data within the logs. With each call and response generating individual log files, the volume of transactions quickly becomes overwhelming, rendering effective analysis nearly impossible. In contrast, the previous socket-based M3 API connector generated a consolidated API text file that enabled easy data search and facilitated comprehensive analysis, including input and response times. The current limitation significantly hinders error diagnosis, making the troubleshooting process arduous and time-intensive. We propose…
3 votes -
Automatic Decompression for GZIP and DEFLATE Content-Encoding in REST Connector
Currently, when using the REST connector, if a stream is gzip or deflate compressed, the data received is successful with a StatusCode of 200, but the body content is garbled due to the Content-Encoding being gzip'd at the source. This requires additional manual effort in transforming the data to be usable.
3 votes -
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.2 votes -
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…2 votesWe are happy to inform you that development work has begun on the telemtry feature which will allow for such logs. Our product team has assigned resources and is actively working on implementing it. 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 -
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.
-
Need clarification regarding File System Connector functionality
From what I gathered File System works(getFiles, getDirectories, createDirectory etc. ) only on Server where corresponding Agent was installed. How it works when for redundancy we install Agent Manager with same Agent Group on multiple servers? Where will connector "look" for files and directories?
1 vote -
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 -
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 -
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 -
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?