3. Enhancement
Added Define External Key Button on the Mapping tool
In the previous version, you can set the external key by checking the field of mapping. Currently, you define one field as a key or multiple fields as a combined key. Therefore we enhanced our mapping tool to handle many possibilities to define the complex keys. We added the Define Exernal Key button on the Mapping tool in order to define the key with AND, OR clause, Customize the logic, or create a custom class to build your own key logic.
We provide these three options to build the external Key.
- All of the conditions are met (AND) means this is the default we currently have as the only available solution.
- Any of the conditions are met (OR) means you want to provide. With this option, we can have 3 fields f1, f2, and f3 defined as key fields. But when the sender sends only f1, we use f1 as the key. If the sender sends f1 and f2 we use these two fields, and if it sends all three fields f1, f2, and f3 we use these 3 fields and chose one of them.
- Customize the logic means the user has to define the logic like 1 AND (2 OR 3)
- Custom Class means you can build your own key logic by creating your apex code.
Allow the mapping to map with the Salesforce formula field as the external ID
In the previous version, you can not map the salesforce formula field, because this field reads only. Now, we will allow you to map this salesforce formula field as the external id in order to make the key for upsert, delete, insert, and update the records.
Mass Find & Replace function for failed/pending message
If you have a large number of failed messages that need to be edited, you can use the Find & Replace function to perform mass editing and replace data. With this function, you can search, edit, and replace the text in the IData of failed/pending messages. The Find & Replace function can be accessed from the Integration page.
Added a new field to support GETCORRELATIONID
In the previous version, GETCORRELATIONID() only supported three fields: SKYVVA_EXTERNAL_ID__c, TransferId__c, and TransactionId__c. We have added a new field called "system_external_id__c" in order to generate a correlation ID based on it. This ID is used to reference the request and response so that you can identify which request corresponds to which response in asynchronous mode communication.