Backup and restore IWorkflow record #
In the previous version, IWorkflow was not able to be backed up and restored. We are now offering those functions for IWorkflow.
Batch and Bulk using file #
In the previous version, Batch and Bulk stored data in the attachment. We have changed this to storing in a file instead.
Mapping is not mandatory for outbound processing #
The GET operation no longer requires a requested body payload, so mapping is no longer mandatory. For example, when using the operation GET with adapters like SAP Business One.
SAP CPI adapter now supports CSRF #
We have enhanced our SAP CPI adapter to support the enablement of CSRF protection. You will now see the “Generate CSRF token?” property, which you can check if you wish to use this feature.
Enhanced Change Data Transfer (CDT) Scheduler #
In the previous version, the CDT scheduler had the option to set Send Mode(CDT) on Set Scheduler Time. We have removed this option from the scheduler and added “Data Send Mode” fields to the interface instead. All fields picklist means to send all fields based on mapping (query), and the Changed fields picklist means to send only fields whose value has changed.
Generate sObject Message Type for Soap and Rest Template in SAP Control Board #
We have added the ability to generate REST and SOAP templates with sObject message type on the SAP Control Board.
Don’t Export NULL value for outbound processing #
We now offer an option “Don’t Export Null value” for outbound processing. If you check this option, null values from sObject fields will not be exported into the payload.
Description of Formula and Expression #
In the previous version, you could not write documentation for your formulas. We have added a Description field for inputting text to describe your formula’s work.
Support for a business response on integrating v3 and v4 #
We have enhanced support for a business response, so you can now do mapping on the response interface (outbound) with the business response and build the payload structure using the mapping tool. This allows you to return more data and format the structure differently than the standard response, which is supported in sync mode only.
Hyperlinks on the Message Name of Comment #
You know already with the failed message while you have pushed the record failed. When you push the failed again with the same external id, the new message will create and set the status equal pending. You will get the comment to have the first failed name in the comment as the text. Therefore we have enhanced the message name on the comment will become to the hyperlink and link it to the first failed message details page after clicking.
Enable the External Mapping and Internal Mapping to get sObject Hierarchical #
In the previous version, external mapping did not allow for mapping and Internal mapping displayed only the flat structure. Now external mapping allows for mapping with sObject hierarchy and Internal mapping will display the flat structure.
Unlink the Menu of the message type #
We added the Unlink list Menu of the message type in order to unlink the parent node of the message tree.
Create outbound and inbound messages for the response and request business using the API V4/integrate #
We have enhanced the message structure with the request and response of business messages. There are three structures as following below:
[su_box title=”Structure” style=”glass” box_color=”#00d9a6;” title_color=”#00000″]
Here is a structure for the Request Business message:
- API message
- Request Message
- Business Message
- Request Message
Here is a structure for the Response Business Message:
- API Message
- Response Message
- Business Message
- Response Message
Here is the message have the request and response together:
- API message
- Request Message
- Business Message
- Response Message
- Business Message
- Request Message
[/su_box]
Added “Delete fields, not in the payload” Mode on the Interface Setup Section of Interface #
SKYVVA has provided the new “Delete fields not in the payload” mode on the Interface Setup Section in order to Delete the value of fields in salesforce that are not included in the payload after send.
Update the parent record while processing the child #
We have enhanced our inbound processing feature to be able to navigate using the mapping tool to the parent and map some parent fields. With this enhancement, you can update the parent records. For example, You can update the contact record and also its parent (Account). In the previous version, you must build a hierarchical interface or two separate interfaces to handle this requirement. Now you do not need to do this anymore.
SAP CPI and SAP PI/PO adapter support the error handling for the Synchronous #
We have enhanced our SAP CPI and SAP PI/PO adapter to support error handling referring to the response. You can make the response error by adding the SKYVVA system fields such as __SKYVVA__Response_Code and __SKYVVA__Message in your response payload.
For example, the application response
[su_box title=”Response” style=”glass” box_color=”#00d9a6;” title_color=”#00000″]
- XML:
…
<__SKYVVA__Response_Code>500</__SKYVVA_Response_Code>
<__SKYVVA__Message>Error Info</__SKYVVA_Message>
- JSON:
….
“__SKYVVA__Response_Code” : “200”,
“__SKYVVA__Message”: “Success Info”
…
[/su_box]
[su_box title=”Note” box_color=”#2a8af0″ title_color=”#000000″] These fields cannot be repeated in response (JSON/XML)[/su_box]
Generate a new XSD format for handling the response of V4/integrate using SAP-PO #
We have enhanced Generate MetaData on XSD schema file format to handle the response of V4/integrate and it will generate based on the interface configuration. There are two responses such as standard and business.
Handling Error for the synchronous API call with fault interface #
We have enhanced the Error Handling fault interface feature to support many adapters with synchronous API as follows:
SAP CPI, SAP PI/PO, SAP ERP, SAP S/4HANA, SAP Business One, SAP Business ByDesign, REST, SOAP, OData, Microsoft Azure ESB, Google API Gateway, Amazon API Gateway, SAP BTP API Management, Agent Rest, Agent Soap, Agent SAP ERP, Agent SAP S/4HANA, Agent Microsoft Dynamics NAV, Agent Microsoft Dynamics 365 xx, Agent Microsoft Dynamics AX xx.
Enhance the data selection when creating the message to pass to the target interface in a workflow #
The mapping will able to allow the user to add the parent field and SOQL Condition on the child node in order to read data from the parent message. The idea is to allow the user to select the parent data that should be used on the target interface workflow filter to be passed through to the target interface without having to do the trick with the mapping.
Read HTTP Header and Query Parameter fields into the message #
We have enhanced our inbound APIs, V3/integrate and V4/integrate, to allow users to fetch data from the HTTP header and the Query Parameter into the message. This will help to eliminate naming conflicts and provide more flexibility in reading the data.
Set conditions for nodes that we bring up to the higher level #
We have added the ability to define the conditioning path by path to go from one node to the next by using the node’s value. This will help users to set the context for skipped nodes more easily.
Enhance the copy node function to allow copying element fields #
We have enhanced our copy node function to allow the copying of element fields as well as structure nodes. This new feature will make it easier to repeat elements with attributes many times.
Customize the SOAP template to support custom namespaces #
We have added the ability to edit custom namespaces manually on the message type, IStructure, and Message Type field Entry. This will give users more control over their SOAP templates.
Array fields of inbound and outbound JSON payload map to the multi-picklist field #
Currently, we cannot support the array value of fields in JSON inbound and outbound payload. Therefore, we have enhanced it to get the array values in JSON payload into the multi-picklist fields, and it also gets value from multi-picklist to JSON payload. We also added the new formula “GETVALUEBYINDEX(text, index)” to retrieve the value by index. For example, Types have Customer – Direct and Customer – Channel, and the users have the formula GETVALUEBYINDEX(Types,1). So now the users will get Customer – Channel.
Outbound (InterfaceExecution) scheduler support with parameter expression based on Last Run Date #
We have added two parameter expressions such as {!_SKYVVA__RecordCreationDate} and {!_SKYVVA__RecordModificationDate}. The {!_SKYVVA__RecordCreationDate} is used for the latest records creation datetime. {!_SKYVVA__RecordModificationDate} is used for the latest records modification datetime. It will check the last records changed to be sent by InterfaceExecution scheduler. For example, SOQL as SELECT Id FROM Account WHERE LastModifiedDate > {!
_SKYVVA__RecordModificationDate}.
Send the response asynchronously for the asynchronous inbound call using the CDT job #
We have enhanced the working on request (Inbound processing) and response(Outbound Processing) with asynchronous mode. This allows users to respond back at a later point in time by linking the request and response interface to each other and then setting the adapter into a response (outbound interface) that is required.
Send the response asynchronously for the asynchronous inbound using the platform event #
We have added platform events to support the request (Inbound processing) and response(Outbound Processing) with asynchronous mode. This allows users to create even messages for response (outbound processing) after requesting (inbound processing).
