- Resolved: Null Message Name Issue Fixed
- Not Refresh Log Profile After Save Log Configuration of Agent Control Board
- The Message Remains in 'New' Status Even After Related Record of the Message Has Been Deleted
- Incorrect Message Structure Generation When Using The Agent SAP ERP Adapter to Invoke BAPI
- Fixed Remove White Space Inside Single Quotes and Double Quotes
- Error in Query Generation Due to Line Breaks in the Query
- Not Able To Delete Custom Interface Group Completed
- Fixed Update/Delete Connection Property of Adapter (Generic Adapter List and Control Board)
- Fixing the issue of Test Mapping Generation without a Child Header in the CSV Hierarchical Structure
- Fixed parent and child messages with different status
Resolved: Null Message Name Issue Fixed #
We have a problem while we are doing custom message name format with V3 processing. The formula was not correctly retrieving the value from the field. It consistently returned a null value for the message name, despite the field being passed in the payload. Fortunately, this issue has now been resolved.
Not Refresh Log Profile After Save Log Configuration of Agent Control Board #
The Log Configuration on the Agent Control Board helps us set the logging profile for an application. This allows you to control the types of log messages that will be recorded in a log file. We also have an option to save the default Log Profile. However, we encountered an issue where, after saving the Log Profile, the screen did not refresh properly and displayed a different profile name instead of the one that was saved. Fortunately, this issue has been fixed.
The Message Remains in ‘New’ Status Even After Related Record of the Message Has Been Deleted #
When you use the invokeCalloutV3() method with the ‘message_only’ mode during a callout, new messages will be created. These messages can be retained and reprocessed at a later time, either through a scheduler or manually. However, we have encountered an issue where, after the scheduler or manual reprocessing of the message, if the related record of the message is deleted, the message remains in the ‘New’ status. To address this issue, we have fixed it by updating the message status to ‘Completed’ and adding a comment stating ‘Related record (Id=xxxxxxxxxxxxxxxx) deleted’ or ‘Related record (Id=xxxxxxxxxxxxxxxx) not found (child message) ‘.
Incorrect Message Structure Generation When Using The Agent SAP ERP Adapter to Invoke BAPI #
When we use Agent SAP ERP to call a BAPI, we encounter an issue with the message structure view in the new V3 format. We only see two separate messages for the request and response, without the root message that should enclose both. The expected message structure should be as follows:
- API Message
- API Request Message
- Business Messages
- API Response Message
- Business Messages
- API Request Message
Fixed Remove White Space Inside Single Quotes and Double Quotes #
We have a problem with our formula in the white space inside a string (Single/Double Quotes). For example, you have added “Laptop – Screen”. After the mapping is executed, it gets the result Laptop-Screen. We notice that the white space has been removed. This issue has been fixed.
Error in Query Generation Due to Line Breaks in the Query #
When there is a line break between the ‘From’ and ‘Where’ conditions in your query, it would result in the generated query being incorrect after saving the new field mapping. This issue has been fixed through the implementation of a solution that ensures proper query generation, regardless of line breaks between the ‘From’ and ‘Where’ conditions. With this fix in place, users can now confidently save their field mappings without encountering any inconsistencies in the generated queries.
Not Able To Delete Custom Interface Group Completed #
An issue arises when attempting to delete the custom interface group, resulting in an error message indicating ‘Invalid Id: Delete Record’. However, this issue has been successfully resolved by implementing the capability to delete custom interface group records.
Fixed Update/Delete Connection Property of Adapter (Generic Adapter List and Control Board) #
There is an issue when updating or deleting the connection destination of the adapter within the same organization. For instance, if you delete the connection destination, it results in the connection destination being removed from the adapter. When accessing the Any Control Board, you may notice that the connection still appears on the adapter screen. However, when viewing the details of the adapter, the connection destination property is missing. This issue has been fixed by adding a warning and setting the Connection Destination Name highlight as a yellow color.
Fixing the issue of Test Mapping Generation without a Child Header in the CSV Hierarchical Structure #
The identified issue occurs during the testing of mapping to validate the generated payload using CSV hierarchical structure. It was observed that the headers for the child fields were not being generated. However, I am pleased to inform you that this issue has been successfully resolved.
Fixed parent and child messages with different status #
There is an issue with the Internet Drive adapter during the callout process, resulting in a warning message. Consequently, the child and parent messages have different statuses. For example, the parent message may be marked as ‘pending’, while the child message may be marked as ‘failed’. This issue has been resolved by setting all messages to a pending status.