21 results found
-
New Connector in order to work with Excel files
We would like to have a new conector in order to read and process excel sheets as part of our daily business. At the moment we can only work with .csv files using existing Novacura connectors. We would like to request to add a Connector to make it easier to work with Excel Files.
25 votes -
OData Error Format Change
We would like if the OData connector return error (Error.jpg) like in IFS structure (IFS error structure.png) as a flow structure: record error containing fields code, message and table details with code and message columns. This would remove the need to beautify the ErrorMessage in flow script. Also using the break workflow feature could show just the error.message and details.code + details.message (Error in flow.jpg).
8 votes -
Descriptive Error details in Web Service connector logs
We would like to get more information on the error when an error is thrown by the remote system when communicating through the web service connector. Sometimes there is not much information available to the user or developer for that part. It would be great if this error in full could be written to the error log file which would make debugging this a lot easier. And of course also present the correct error message in full to the user.
9 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.
5 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.
3 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.
4 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).
2 votes -
Null Date Inputs in IFS OData Connector
Currently, in the IFS OData connector, date fields can be modified but not cleared (set to null), although it's possible to clear these fields directly in IFS. Converting to a custom operation allows null inputs but is not a desired solution due to its complexity.
We propose to add functionality in the IFS OData connector to allow null inputs for date fields. This would align with the behavior seen directly in IFS and would enhance the versatility of data manipulation in the OData connector.
4 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.
2 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.
4 votes -
SOAP Connector support Password Credentials
The SOAP connector in Novacura Flow should be able to support password credentials. This would allow to connect to more data sources.
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.
3 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.
1 vote -
Resize image in oData Connector
Need the possibility to resize images fetched with the oData Connector. We currently do not have the possibility to resize images in any way. After talking to people in customer success team they said the easiest and fastest solution would be to create the possibility to resize images directly in the oData Connector when they are fetched from IFS with the oData Connector.
1 vote -
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.
2 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…
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 -
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…
1 vote
- Don't see your idea?