- SAP Business ByDesign Adapter
- Test Adapter
- Not required to check flag 'External Mapping' when using an inbound interface without a message type
- Enhanced Send asynchronous response for the inbound call
- Set the status for the empty message
- Read changed data based on the last API call date
- Process the raw data basket using the event consumer
- Added a New Formula function to convert the timezone
- Enhanced Email Adapter to Support V3 Processing
- Enhanced Rest Adapter support form-data and x-www-form-urlencoded request payload
- Don't process the interface in parallel in batch processing
- Interface Data Button and Action Button
- Enhanced Outbound Adapters for Internet Drive to Exporting Binary Files
- Active and Deactivate on Workflow
SAP Business ByDesign Adapter #
We have enhanced SAP Business ByDesign by adding the Pagination property for the response. Pagination is a technique used to limit the number of records returned by an API response. For example, if you have a thousand records in SAP Business ByDesign and you need to retrieve all records without encountering a limit error, you will need to use pagination. You can set the ‘top’ parameter to twenty records and retrieve a response of twenty records per response by checking the pagination flag.
Test Adapter #
Currently, the Test Connection is a tool used to test the adapter endpoint. We have now enhanced the Test Connection by allowing users to create records for testing their APIs. This enhancement also provides a Request Path, Request Header, and Request Query for inputting invoke callout parameters, and allows users to add Test Cases to test as many use cases as needed. The Test Connection can retrieve the request body via the test mapping result or allow for the upload of XML and JSON payloads into the request body. This enhancement is currently only available for the SAP ERP adapter.
Not required to check flag ‘External Mapping’ when using an inbound interface without a message type #
In the previous version, in order to use V3 processing, you needed to add a message type or check the ‘External Mapping’ mode. However, we have enhanced our V3 processing to support using it without a message type or setting the ‘External Mapping’ flag. If no message type is specified, we assume that the structure of the message is the same as the sObject that the user has set in the ‘Source/Target Name’ field.
Enhanced Send asynchronous response for the inbound call #
There are two options for enhancing the sending of asynchronous responses for inbound calls, as outlined below:
- Create Platform Event: This is a custom event that requires you to write Apex trigger code to perform the desired action. For example, you can use the invokeCalloutV3() method to send a response interface, and the event will be consumed by the external client.
- Use CDT Job to Send Response: This option does not provide a real-time asynchronous response. Instead, it creates CP records and waits for the CDT to pick up the CP record and send it to the receiver.
Set the status for the empty message #
Our default behavior is to set the status of an empty message to ‘Failed’. However, we have added a new enhancement that allows users to set the status of a message when it is created, even if it does not contain any IData. This improvement is aimed at enhancing monitoring for users who want to set the status and be notified when a message does not contain any IData. This setting is flexible and can be customized according to user preferences. Therefore, you can define the status of an empty message to be displayed in the monitoring.
Read changed data based on the last API call date #
We have enhanced our reading to only include the latest change records based on their modification and creation dates. To achieve this, we will pass the last scheduler run date as a query parameter that needs to be added to the API, e.g., ‘LastRunDate’. This will allow us to read only the data that has been changed since the last call, i.e., the last run. The API call will compare the last run date with the modification and creation dates of the records.
Process the raw data basket using the event consumer #
This enhancement will enable you to process raw data asynchronously in real-time. You can use this function by setting the ‘Inbound Processing Behavior’ to ‘Event Trigger Apex’ for IntegrateV4, or for IntegrateWebhook. It will create an event, and our Skyvva Trigger will subscribe to it to process raw data baskets synchronously in real-time.
Added a New Formula function to convert the timezone #
We have added a ConvertTimezone formula that allows you to convert your DateTime to any other timezone you may need, based on your business requirements. For example, if you want to convert a time from Moscow to Phnom Penh timezone, you can use the formula: ‘ConvertTimeZone(“2023-07-05T07:25:00”, “YYYY-MM-DDThh:mm:ss”, “GMT+03″,”GMT+07”)’. The result will be ‘2023-07-05 11:25:00’.
Enhanced Email Adapter to Support V3 Processing #
In the previous version, the Email adapter supported only v3 inbound processing and V2 Processing. However, we have now enhanced it to support outbound V3 processing, including the handling of two in the body or attachments.
Enhanced Rest Adapter support form-data and x-www-form-urlencoded request payload #
In the previous version, the Rest adapter only supported the application/xml and application/json request formats. However, we have made significant enhancements to the Rest adapter in the latest version. It now includes support for additional request payload formats, specifically application/form-data and application/x-www-form-urlencoded. This means that you can now utilize these formats when sending requests through the Rest adapter, providing greater flexibility and compatibility with various data formats and systems.
Don’t process the interface in parallel in batch processing #
In EO Group, the BatchProcessPerInterface scheduler processes the basket in parallel by default. However, suppose your business requires updates to the same records to be processed sequentially. In that case, you can use the new picklist option, ‘Don’t process the interface in parallel’, available in the Batch Processing Runtime behavior. This option ensures that only one job is used per interface processing, preventing any potential issues that may arise from parallel processing.
Interface Data Button and Action Button #
The ‘Interface Data’ button is located in the Interface Detail, while the ‘Action’ button can be found in the Interface List under the integration section. When you click on the ‘Interface Data’ button, a popup window will appear, providing access to view Reports and Dashboards. This feature allows you to monitor your messages and gain insights into the performance and status of your interfaces. It provides valuable information and analytics to help you track and evaluate the data flowing through your interfaces.
Enhanced Outbound Adapters for Internet Drive to Exporting Binary Files #
In the previous version, the outbound adapters for Internet Drive only supported the export of CSV, XML, and JSON files. However, in this new version, we have expanded the capabilities of the outbound adapters. Now, you can utilize outbound adapters for Google Drive, Amazon S3, Dropbox, and Microsoft OneDrive to export not only CSV, XML, and JSON files but also binary files.
Active and Deactivate on Workflow #
We have enhanced the functionality that allows you to activate and deactivate workflows. When ‘Active’ is set, the workflow will trigger the workflow rule. If the ‘Deactivate’ option is set, your workflow will not run at all. This feature is very helpful because it enables you to keep the workflow for future use without the need to delete it when you’re not using the workflow rule.