24 results found
-
Evergreen IFS Rest Odata calls
In the IFS Odata Connector we would benefit from first of all identification of all Odata projections used in a a flow and secondly to scan the IFS APIBreakingChanges release files to find out and mark Flow objects if there has been a change in any projection.
There are two different APIBreakingChanges files:
- Between Service Updates within a functional Release
- Between Functional releases.
See attached examples.
8 votes -
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.
7 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.
-
Make workflow specific variables available within a workflow
Enable the workflow specific variables that are available in the workflow report through the Flow Environment connector.
The requested variables/parameters are
Workflow ID
Workflow Name
Application Name
Application Short Name
Application Short Description
Application Long Description
Monitored
Force Commit Message
Create Date
Latest Version
Commit Message
Published by
Published Date6 votes -
Additional Authentication Options for Email Connector
Microsoft is discontinuing basic HTTP authentication for Exchange on October 1st. While SMTP basic authentication, which appears to be used in our email connectors, will continue to function based on Microsoft's documentation:
Deprecation of Basic Authentication in Exchange Online
Considering this deprecation, Microsoft advises us to explore alternative options. Anticipating that similar queries may arise from various customers, we kindly request the development of a new email connector (or an update to the existing one) that supports alternative authentication protocols. This proactive approach will help address potential customer demands as they begin to inquire about this change more frequently.
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.
-
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.
-
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.
5 votes -
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…
5 votes -
Seamless OData Projection for Workflow Subscriptions Across Environments
We would like if a warning message can be implemented when you add a new projection in DEV/TEST environment and then subscribe to PROD, that has not the new/added projection. Which is to get a warning with info about it, or that the projection is added automatically when it happens. Or such a solution so that End user will not get affected.
5 votes -
Bulk API for Infor M3 REST Connector
In order to increase performance, implement a Bulk API for Infor M3 REST Connector. Instead of the iterator on a table sending individual transactions, a developer should be able to select Bulk and the restful webservice should combine transactions and send a single message, as shown in BulkPOST.png.
5 votes -
Generative AI - ChatGPT Connector
It would be helpful to have a ChatGPT Connector and templated process to use this connector. For example, using ChatGPT to create FlowScript based on natural language, personal recommendations based on Portal 2, document summarization in Portal 2. This connector should be set up to allow developers to see an example of how to use it, but be able to embed this connector into their own apps.
4 votes -
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 votes -
Enhance the flexibility to Allowing same API Key Names with Different Identifiers
In REST endpoints where some operations require an apiKey in Header and some as a query parameter. Both the query and the header key got the Api key name “apiKey” but they got different names as "apiKey Query" and "apiKey Header". But it is only one of them shows up under Authentication. The fact that it says apiKey(apiKey) shows that it doesn’t recognize that the keys have different names even if the name of the key is the same. Request an enhancement to allow the same API key name with a different identifier name.
3 votes -
Allow string value of Pipe characters into OData connector
We would like to have new feature to be able to pass the value string which includes Pipe characters (|) to the OData connector (without line breaks).
3 votes -
File System Connector - Zip File Streams into Variable
We would like to get a way to Zip File Streams directly into a variable instead of needing to a file location to store them. This could open up multiple UI options otherwise gated by filesystem access.
3 votes -
OData Connector Attribute List Ordered Alphabetically
We would like “Order of attributes“ is an example where attributes have no order to be ordered alphabetically. In Read operation keys (indicated bold already at the moment) could be first in the list and the remainder of the list should be ordered alphabetically.
3 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.
-
Implement IFS Cloud Batch Update in Odata Connector
We would like to have IFS cloud 'batch' update call feature used in IFS in the novacura OData Connector.
2 votes -
Implement the user property for different connectors
Implement the user Property for both IFS10 and Oracle connectors and update the Login value for the Novacura user by replacing the same account name with an AD property value
2 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…
2 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.
2 votes -
OData Filter an Entity Set based on Related Entities
At present, the IFS OData connector does not have the capability to filter an entity set based on related entities. Although the UI might suggest otherwise, it is important to note that any attempts to filter in this manner will not be saved in the Workflow.
The current workaround is to use the Code method included in the connector.
2 votes
- Don't see your idea?