- Enhanced Message Monitor of Batch Queue Detail page
- Enabling DataLoader to Import XML and JSON Files with V3 Processing Without Specifying Message Type
- Added New “Reprocess In Batch” Button On Message Detail Screen
- Added Sample Data for Testing Workflow
- Allow the Mapping of Reference Fields to Nodes
- Enhanced filter message for Sub-Interface
- Enhanced the Structure Message
- Added New “GETORGID” Formula
- Upgrade API Version to 57 on the Skyvva package
- Add a New ''Re-Order Mapping" button on the Mapping Tool
- Redesign of Interface detail page, interface list view, and Interface Tab of the Integration page screen
Enhanced Message Monitor of Batch Queue Detail page #
On the Batch Queue Detail page, you can monitor messages on the ‘Messages’ section of the Batch Queue screen. In the previous version, messages were displayed as flat messages, which could be difficult to navigate, especially for complex data structures. However, in the current version, the messages have been enhanced by a hierarchical message view, allowing for easier visualization of data relationships and dependencies.
Enabling DataLoader to Import XML and JSON Files with V3 Processing Without Specifying Message Type #
In the previous version, importing data in JSON and XML format was not possible unless your interface was linked with a message type. However, with the introduction of the Interface API Version setting, you can now set it to V3 to allow for the mapping of sObject hierarchies. As a result, we have enhanced our Data Loader to support XML and JSON files with V3 processing without the need for a message type.
Added New “Reprocess In Batch” Button On Message Detail Screen #
Currently, reprocessing messages on the Message Detail page in synchronous mode by default is no longer possible due to the presence of multiple business messages in a root message. This can result in the Apex CPU time limit being exceeded. To address this issue, we have enhanced the functionality by adding a new ‘Reprocess In Batch’ button, which allows messages to be reprocessed in batches.
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.
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 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.
Upgrade API Version to 57 on the Skyvva package #
In the previous version, the Skyvva app used API version 52 for Apex classes, Apex triggers, Aura components, LWC components, and Visualforce pages. To prevent certain errors, for example, you were unable to map the Address field of the asset sObject using our current API Version. Therefore we have updated the API Version to 57.
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.
Redesign of Interface detail page, interface list view, and Interface Tab of the Integration page screen #
We have redesigned the interface screen to improve organization and provide more flexible features, including:
- Enhanced flexibility in searching for interface records on the interface list view and interface tab of the Integration page.
- Hierarchical view of sub/IChain interfaces on Interface Tab of Integration page, interface list view, and the left panel on interface detail page view.