- 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
- Fixed Remove White Space Inside Single Quotes and Double Quotes
- Fixing Issue: Generating XML Payload with Double Root
- Error in Query Generation Due to Line Breaks in the Query
- Not Able To Delete Custom Interface Group
- Fixed Update/Delete Connection Property of Adapter (Generic Adapter List and Control Board)
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’.
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.
Fixing Issue: Generating XML Payload with Double Root #
There is an issue when performing mapping with a root, where the XML generated payload contains a double root. This issue has been fixed by implementing a solution that ensures the mapping process generates XML with a single root element, resolving the problem of duplicated root elements in the payload.
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 #
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.