24 results found
-
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 -
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?