2. Bug

Cannot use Query Parameter Properties

• Query/PATH Parameters are different, this issue is about PATH Parameter that has been manage incorrect template.
• The template must be correct case i.e. X.URL.PATH Parameter.paramx that is implemented for other adapters (REST template), not X.URL.Path Parameter.paramx.

Completed messages created despite setting

• By creating an interface with custom apex class (Custom processing) and checked flag < Delete completed Message but Keep Other >, the completed message were not deleted. It is a bug in apex module of handling interface with apex class

Dynamic Header, Dynamic Query Parameter and Dynamic Path Parameter issue

Here fix with Old Way: (key and value both are replacing) to New Way: (replacing only value key is static when we are using dynamic query and header parameter).

• Adapter PropertyHeader : authorizationCodeValue is coming from the mapping. Replacing only value in apex side base on mapping
• REST URL Query Parameter: Field Value is coming from the mapping. Replacing only value in apex side base on mapping

SKYVVA Callout in batchable context

• That is a bug while updating the message failed message.
• Fixing issue of updating message record while doing integration.

Issues with DataLoader

• condition__c and condition2__c before we view on screen condition__c and now we view and condition2__c problem with client set new value to old field.