20 results found
-
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 -
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 -
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 -
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 -
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 -
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 -
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.
-
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.
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.
-
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 -
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 -
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 -
Add scale function for ODATA document management
New scale function was developed for media items. But most customers use document management also for images. This idea is to also make it possible to scale documents stored in document management. It could be configured to be up to the developer what kind of documents is scaled, but of course also if making a general functions so that if a word document is sent in to the function, then the document should not be scaled.
1 vote -
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 -
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 -
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.
-
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 -
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?