The fields are always visible on the mapping tool #
There is an error when the users have created the custom field, and the field is not visible to the user profile. However, the field still showing on the mapping tool. This issue has been fixed.
Fixed ping connection of Google Adapter for Authorization Code #
Fixed getting an error “error:invaild_grant error_description: Bad Request” while the user has a ping connection of Authorization Code in OAuth2.0 Flow property. This issue was fixed by saving the information of the refresh token in the background in order to avoid this error.
Fixed hiding the password while entering it into the transport bridge #
When the user creates the transport route. The screen will require entering the password. Fixed to hide the password to show an asterisk (********).
Fixed to display the original name that has a dot on the mapping tool and message data #
We have covert the message type name and the message data from the “.” to the special characters “!$!” in order to identify which is the path of the mapping or the message type name. When we have the mapping with the message type name that having the dot will show the “!$!“. For example, the message type name is Account.MessageType and It will be Account”!$!“MessageType after mapping. Fixed to revert to the “!$!” to the dot “.” while showing on the screen mapping tool and the message data.
Set the message status of the inbound request message to ‘Cancelled’ when the interface runs in Transactional mode and gets an error while posting #
When the interface is a transactional interface process message, whenever it will we roll back the complete API request transaction in case we face an error (failed) then all are not saved.
