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.

Bug List: #

DML limit at IServiceBatchCallOut #

This error was rising at the last step of reprocessing. when the processing try to delete MessageQueue and clear emptyRecycleBin.

Lease Migration #

This bug regards the header columns having double quotes that skyvva data loader has not supported.CSV header contain white space inside a double quote.

Error while importing interfaces #

This is a bug that happens when creating an interface group manually that didn’t generate external value to make it unique, so when we try to export and import will create one more interface group, but creating an interface group from import function is having external value. 

When Message Status is Failed or Pending Skyvva sends the Code 500 Server Error:
a new parameter is added called ‘http_error_status’ that you can use in the API query parameter to set the behavior of how you want to have the HTTP response code in your client. The possible values are ‘Failed’, ‘Pending’, ‘Partial Completed’. You can set for example all 3 or only 1 or two. In this example &http_error_status =Failed, Pending, Partial Completed it means that want to get the HTTP status code 500 internal error when the message status is ‘Failed’, ‘Pending’, or ‘Partial Completed’. When you set like this &http_error_status =Failed, Pending then it means that you want only to get the HTTP status code 500 when the message status is ‘Pending’, or ‘Failed’ but not ‘Partial Completed’. In case the message has the status ‘Partial Completed’ you will get the HTTP 200 OK.

Bug fixed in this patch:

• Link the sap business one business partner Id with Salesforce Account in an external field.
• SAP CPI Certificate Authentication Development And Testing.
• Workflow Condition: select source fields bug