5. Bug Fixed
The deselect All function did not work with the child Message
When child messages have been selected and you attempt to deselect them using the 'Deselect All' button, the child messages are not deselected. However, this issue has been fixed.
Unable to Search All Message Records When the Reset Function is Applied
An error occurred when you clicked the reset button to reset the values you selected or entered in Message Monitoring. However, the Mode selection was not reset. This is why the existing search Mode remained unchanged. Fortunately, this issue has been resolved.
The spinner did not stop while selecting Parent Reference in the Source Tree
An issue occurred when you were mapping for the first time without saving it yet with V3 sObject mapping. Then, you attempted to map a child field to create a formula for retrieving the parent reference field using Source Tree in the child mapping record. After selecting the parent reference sObject, a spinner appeared but did not stop. Fortunately, this issue has been fixed.
Missing Root Namespace
There is an issue when you perform a V4/Query with a root message type namespace. The mapping tool does not save it. Therefore, when you query it with our V4/Query, the business payload does not have the namespace in the root business. However, this issue has been resolved.
Getting an Error 'Attempt to de-reference a null object' while integrating with External Mapping
There is an issue when you perform external mapping with a set external ID field and pass the value as “0010000496:0010” format. It will raise an error message “Attempt to de-reference a null object”. Because our integration tries to search existing records by this value 0010000496:0010, the record is not found in the search result then integration checks a value that is 15 chars and an instance of ID, then integration casts it to ID's value to get the completed Id-value (18 chars) to search result again if record existing by 18 chars, but casting error due to value is not correct form if record Id.
Did Not Return Salesforce ID into the Response of SOAP Adapter
There was an issue when choosing the Salesforce Authentication Provider and wanting to return the Salesforce ID in the response of the SOAP adapter. It would not include the Salesforce ID in the response payload. However, this issue has been resolved.
Fixed Various Issues with Mapping Tool
There are various issues related will the sObject V3 Mapping in the Mapping Tool as follows:
- When you set the context level while using sObject V3 for mapping, for example, setting the context from 'contact' to 'account' and mapping 'account' to the 'Account' node, then mapping the 'contact' field to the 'Account' field, a message will alert you to confirm to do the filter. If you set the filter and then click the Save or Cancel button, the screen may become unresponsive. However, this issue has been fixed.
- The issue happens when you have to do the formula of the set context field, it will lead to to select the Source Tree and Source Fields. After selecting the alert message will ask you to set a coditon to filter the data. Then Click OK, the screen set condition filter popup screen will not pop up and the existing expression will clear. This issue is Fixed.
- The issue with saving the mapping record which has a mapping that includes a set context field has been resolved. Previously, an alert message would appear saying, 'Warning! Mapping from a lower level to a higher level is not allowed!'. This issue has been fixed by allowing the mapping to be saved.
- We have also added the missing 'Add/Edit Filter' functionality, allowing you to edit and add filter conditions to refine data filtering, similar to the V3 Message Type.
Fixed the issue of missing child records when selecting 'Delete + Upsert' on the 'Init Operation' option
An issue occurred when attempting to delete a child record before performing an upsert. For example, if you created a relationship between an iChain Contact and an Account and selected 'Delete + Upsert' on the Init Operation, pushing the records would fail to upsert the child record because Salesforce cannot delete existing child records in some cases. As a result, the upsert operation will not work. This issue has been resolved by upserting child records even deleting child failed.
Fixed The Issue of Job Information not displaying on the interface of the Agent Control Board
We have an 'Interface' tab in the Agent Control Board to view a list of interface information. However, it did not display the details of the job information running on this interface. This issue has been fixed.
Fixed missing interface scheduler on Agent Control Board
This issue occurred when you updated the Connection Destination on the adapter. After the update, the Agent interface scheduler was missing. However, this issue has been fixed.
Not Able To Restore IStrcutrue To Interface
On the Related Page of the Interface, you will be able to Backup and Restore IStructure. However, an error message alert stating 'import the wrong file' appears even when you restore an existing file that has been backed up. This issue occurs because of the white space at the first line of the backup file. However, this issue has been fixed by removing the white space in the Backup IStrcutrue function.