Table of Contents
Fixed various issues in Test Mapping Function #
- When executing records with outbound interface V2 without linking the adapter, the result is not generated. This issue has been resolved by generating the result.
- When clicking the ‘Test Connection’ button on the Test Mapping, the screen did not correctly capture the adapter value. This issue has been fixed.
- An error message “ERROR List index out of bounds: 0566” is displayed when clicking on the Test Mapping button with the Interface Type set to ‘Event-Interface’. This issue has been fixed to allow test mapping with the Interface Type ‘Event-Interface’.
- The error message “Message Error: Attempt to de-reference a null objectLine Of Number: 381” occurs when selecting an existing message to be executed with interface v2. However, this issue has been resolved.
- Added error message “Test Mapping in Sub-Interface is not allowed. Please come to the Main-Interface” while attempting to click the ‘Test Mapping’ button.
Fixed minor bug #
- When clicking on the sub-interface link to view the interface details, the tree interface was not displayed. This issue has been resolved by implementing hierarchical viewing.
- When using the query editor on sub-interfaces, the interface did not display the hierarchy. This issue has been fixed.
- On the query editor, while you have selected all fields, the root node did not select. This issue has been resolved.
- Remove the warning without setting external ID for REST Query, REST Query All, BULK Query, and BULK Query All operations.
Fixed various issue IWorkflow #
- There is an issue when attempting to save a workflow without a condition, causing the condition to generate as ‘undefined’. We have fixed this issue and now it is no longer possible to save an empty condition.
- There is an issue of duplicate sequencing of workflow records when saving them. As a result, the last workflow is executed multiple times due to the same sequence.
- The target interface of the workflow was set randomly. However, we have now set the default target interface to match the selected source interface.
Fixed various issues in the Mapping Tool #
- There was an issue when mapping the parent field from the source to the child in the target while doing the inbound mapping. These mapping records were still located in the parent block. However, this issue has been resolved by relocating them to the child block.
- We encountered an issue while mapping the attribute and copying the node. After mapping it, we were unable to remove these records. However, this issue has been fixed
- We encountered a problem while performing inbound mapping in V3 without a Message Type when you uploaded the IStructure for the Interface. This resulted in additional fields being added under the Name sObject field in the source. This issue has been resolved.
- Added “fx Functions” to do formula for Hybrid Mapping.
- While creating a formula with the fx(Functions) field map, we encountered an issue where the formula mapping would save with the wrong field assigned to another node of fields. However, I am pleased to inform you that this issue has been resolved.
Missing Some Messages After Search Message Again #
There is an issue when searching for messages and clicking on ‘Show More’ to view additional messages. After performing a search and clicking ‘Show More’ again, some messages are missing. This issue has been fixed.
Missing Not able to Delete Integration on Integration Detail Page #
There is an issue when the user deletes the integration on the Integration Detail Page. The integration does not get deleted. However, this issue has been resolved.
Not able to do Manual Processing #
There is an issue when expanding the main interface in order to view the interface tree. When attempting to select the main interface for manual processing, the “Manual Process” button is disabled. However, this issue has been fixed.