- Enhanced Data Loader supports new pure XML payload
- Enhanced CSV Payload of V3 File Outbound Adapter to support Hierarchy
- Creating a 'File Message' to Cover Business Messages via Integration with the Inbound Internet Drive Adapter
- Enhanced to Custom Message Name Format to support Interface V3
- Added Query Template on Generate Template Function
- Enhanced Email Adapter to Support V3 Processing
- Added a few picklists for the Operation Type of Workflow
- Added WorkFlow Status Button in Message Details
Enhanced Data Loader supports new pure XML payload #
We have introduced a new feature to generate Pure XML Payload. As a result, we have added the XML Root Tag and XML Root Tag Namespace options when selecting the XML Data type on the Data Loader screen. These additions enable the generation of Pure XML Payload as follows:
- XML Root Tag is used to add the Root Tag of the XML payload.
- XML Root Tag Namespace is used to add your own Namespace to the XML payload.
Enhanced CSV Payload of V3 File Outbound Adapter to support Hierarchy #
The outbound file adapter previously did not support Hierarchy CSV payloads. However, we have enhanced it to now support the generation of Hierarchy CSV payloads with adapters such as Google Drive, Dropbox, Microsoft OneDrive, and Google Cloud Pub/Sub. To accomplish this, we have introduced a node prefix for interfaces with multiple levels in the header field. Here’s an example of the desired hierarchy: NodeAccount.Field, NodeContact.Field, NodeN.Field.
Creating a ‘File Message’ to Cover Business Messages via Integration with the Inbound Internet Drive Adapter #
In the previous version, when pushing data using our inbound internet drive adapters such as Google Drive, Dropbox, Microsoft OneDrive, and Amazon S3, it would only create the business message. However, we have enhanced it to include the File Message as well, providing additional context to understand the source of each message. We also added the file name as the transfer ID of that message. So we can easily view which files belong to which group of messages by its root as “File Message”.
Enhanced to Custom Message Name Format to support Interface V3 #
The custom message name format is used to customize any name based on your settings in the interface. Currently, the custom name format only supports interface v2. Therefore, we have enhanced the capability to customize message names with interface V3.
Added Query Template on Generate Template Function #
We have enhanced the Generate Template Function on the repository page to create the message types specifically for querying. The Query Template is used with the V4/Query API to construct queries. This API facilitates executing search queries, specifying search criteria, and retrieving search results.
Enhanced Email Adapter to Support V3 Processing #
In the previous version, the Email adapter only supported v2 inbound processing. However, we have now enhanced it to support inbound and outbound V3 processing, including the handling of two in the body or attachments.
Added a few picklists for the Operation Type of Workflow #
We have added Upsert Auto External ID, Update Auto External ID, and Delete Auto External ID as picklist values for the Operation Type in the Workflow. This enhancement allows users to filter messages based on these operation types.
Added WorkFlow Status Button in Message Details #
We have added a Workflow Status Button to the Message Details, making it easier to view and check the workflow status, similar to the message monitoring workflow view.