Enhanced filter message for Sub-Interface #
We have enhanced the message monitor to filter specifically on the sub-interface. After selecting a sub-interface, the results will show only the messages belonging to its child that are linked to the selected sub-interface. This enhancement will enable faster searching for specific messages at a deeper level.
Enhanced the structure message #
We have the API Monitoring mode present in our Message Monitoring in order to filter the API Message. Therefore we have improved our message structure of sObject Message to cover by API Message while callout failed. If you use this option to filter, you will be able to get an API Message and its child.
For example, the filter option will retrieve messages such as the following:
- API Message (Request Failed/Request Success)
- sObject Business Message
- API Message (Have Request and Response)
- API Request Message (Request Success)
- sObject Message
- API Response Message (Response Success/Fail)
- sObject Business Message
- API Request Message (Request Success)
Added Sample Data for Testing Workflow #
We have enhanced the workflow to allow you to create sample data for testing workflow conditions. This provides an easy way to test formulas in the workflow without having to update the IStructure for sample data in the interface or the message type field entry. Additionally, we can handle message types of type Salesforce sObject without message type field entries. The option to create sample data will appear on both the ‘Create New Workflow Condition’ and ‘Edit Workflow Condition’ screens.
Allow the Mapping of Reference Fields to Nodes #
In the previous version of outbound processing, mapping reference fields to a node was not allowed. However, we have now enhanced the mapping functionality to allow for reference mapping to a master node on the target side for the Outbound Interface. This will result in the generation of an object node in the payload after the callout.
Added New “GETORGID” Formula #
We have added a new formula function called GETORGID to retrieve the org ID. This function can be used, for example, to determine which Salesforce instance a request message is coming from to the receiver. The org ID information can then be used to send the response message back to the caller via a synchronous call.
Add a New ”Re-Order Mapping” button on the Mapping Tool #
We have added a new button called ‘Re-Order Mapping’ to the Mapping Tool, which allows users to reorder mapping records by sequence. This change also prevents users from reordering records in Data Mapping. When the button is used, the sequence field is reorganized during the callout of the record, and the resulting payload records are sorted in ascending sequence numbers. These improvements result in a more efficient and organized data payload sequence structure.