Popular Search how tohow to useagenthowdatarestbatchcustomskyvvasap
View Categories

3. Enhancement

Enhanced Outbound Mapping V3 Allows to Map Hierarchical sObjects (without Message Type)  #

We have improved the mapping tool to support hierarchical sObject mapping for outbound processing in order to process V3 without the need for Message Type.

Enhanced Upload IStructure in Interface #

In the previous version, uploading IStructure on an interface would override the existing IStructure records. However, we have now added an alert message to prompt confirmation for overriding or merging the IStructure records of the interface.

Enhanced Screen and Create Message Type on Open Editor Function #

We have enhanced the Open Editor button function in the Repository, allowing you to select a specific API to create the desired Message Type.

Add Runtime Behavior for sub-interface Workflow #

In the previous version, the Interface Workflow Setting did not have the Runtime Behavior option. However, in the current version, this option is now available, allowing you to configure separate settings from the main/parent interface.

Enhanced Data Loader works with V3 processing without Message Type for Outbound Processing #

In the previous version, outbound mapping did not support hierarchical sObjects with V3 processing. However, in the current version, outbound mapping now allows mapping with V3 hierarchical sObjects. Therefore, we have enhanced the support for V3 processing without requiring a message type.

Enhanced ‘Generate Template’ Functionality with Message Type Option #

In the previous version, the ‘Generate Template’ functionality only supported generating SOAP and REST templates for sObjects. However, we have enhanced it to include the option of selecting a Message Type. This allows users to utilize existing message types for creating new SOAP and REST templates.

Add Processing Mode for sub-interface Workflow Setting #

In the previous version, the Interface Workflow Setting did not have the Processing Mode option. However, in the current version, this option is now available, allowing you to configure separate settings from the main/parent interface.

Enhanced Screen on Switching/Selecting Some Mode of Interface Detail Page #

  • When switching from V3 to V2 on the Interface API Version without specifying the Message Type, the MetaData Provider, Repository, and Source/Target Message Type options will be disabled for filtering.
  • When switching from Normal Mapping to External Mode without specifying the Message Type, the MetaData Provider, Repository, and Source/Target Message Type options will be disabled for filtering.
  • When switching from V3 to V2 on the Interface API Version while specifying the Message Type, an alert message will appear stating, ‘You have selected API Version ‘V2’ and have specified the message type. This is not needed because using API ‘V2’ does not require a message type. Please remove the message type or set it to ‘V3′ if you want to use a message type.’ You can confirm by clicking the ‘Ok’ button, which will automatically remove the message type. Alternatively, clicking the ‘Cancel’ button will retain the existing setting.
  • When switching from Normal Mapping to External Mode while specifying the Message Type, an alert message will appear stating, ‘You have checked External Mapping and have specified the message type. This is not needed because using External Mapping does not require a message type. Please remove the message type or uncheck External Mapping if you want to use a message type.’ You can confirm by clicking the ‘Ok’ button, which will remove the Message Type. Alternatively, clicking the ‘Cancel’ button will keep the existing mode.

Enhancements to the Data Loader #

  • Currently, outbound mapping supports hierarchical sObjects with V3 processing without requiring a Message Type. As a result, we have enhanced the Data Loader to generate the V3 payload without the need for a message type.
  • We have enhanced the export function to support V2 (old interface mapping style). For example, you can now manually create two interfaces (Parent + Child) and establish a chained interface based on their relationship.