4. Bug Fixed

Fixed Deletion of Partial Messages without Child Message

There is an issue when using the 'Delete Failed Message' function on the Integration Setting, where messages may be partial due to failed and new child messages. The 'DoMaintenance' scheduler runs and deletes these failed and new messages, but it may leave partial messages without a child. This issue has been fixed by implementing a trigger to delete partial messages without a child.

Missing CSV Records While Process V4 Integrate

An issue occurred during the ‘V4 integrate’ process in CSV format. For example, you may have pushed many records, but only one was pushed into Salesforce. This issue has since been fixed.

Fixed Test Mapping

There are several fixes on the Test Mapping function as follows:

• Fixed execute while no message is to be executed by an added alert warning message “Please Create iMessage”
• The issue occurred when clicking the 'Refresh' button, but it didn't clear the previously executed result.
• Get an error message “Attempt to de-reference a null object” alert while clicking Execute XML Data format.
• Get an error message “No implementation for file type:json. The possible types are CSV and XML.Line Of Number: 487” while clicking Execute JSON Data format.
• Getting “Message Error: List index out of bounds: 0Line Of Number: 26” while clicking Execute XML Data format.
• If you select the message and then click the Execute button, You will get an error message “Message Error: Invalid payload format for the interface a0d1X000002faKcQAILine Of Number: 395”.

Fixed Find & Replace Function

There are various issues that have been fixed on Find & Replace as follows

• The issue of the message status displaying as gray even if it has failed and is pending under Find & Replace has been resolved.
• Fixed cannot replace the null value
• Fixed cannot find middle text for replacement.
• Added a column to display the status of the message under Find & Replace
• Cannot update the manual value

Not able to be saving the mapping

An error occurred while attempting to save the mapping records, which resulted in the following error message: '928 >> System.DmlException: Upsert failed. The first exception occurred on row 7, with the following error: DUPLICATE_VALUE. A duplicate value was found for the skyvvasolutions__ExtID__c field on a record with the ID xxxxxxxxxxxxxxxx. This was due to mapping the same attribute fields to the same target/source fields multiple times. However, this issue has now been fixed.

Getting Issue Cannot Update Standard comment

There is an issue while you have used the Operation Type Apex class function in order to override message comments. Since it still uses the standard comment instead. This issue has been fixed.

The Formula Cannot Retrieve the Field Value

The formula function was unable to retrieve the value from the 'Field' due to white spaces at the start and end of the field, while there was another field inside the formula that had a relation with a dot. For example, in the formula IF(FieldA = 'xxx', FieldB.FieldC, FieldD), FieldA was unable to trim the white spaces, resulting in an issue. However, this issue has been resolved.

Fixed the Issue of Duplicate Name Creation for Connection Destination in the New Agent

There is an issue when the user creates multiple connection destinations with the same name, as it will only display one connection destination even if there are multiple. Therefore, we are no longer allowed to create duplicate names.

Fixed Various Issues on Mapping Tool

• The fixed outbound mapping now allows fields to be mapped directly without a parent node
• Previously, there was an issue re-generating sequence when mapping a source node to multiple target nodes in outbound mapping. However, this issue has been resolved.
• The problem of deleting a mapping record and unintentionally deleting other sibling records has been fixed.
• Fixed the ordering of mapping records based on the Target Node records in outbound mapping.
• The issue of the mapping tool generating an incorrect tree mapping view of the outbound mapping has been fixed.