Added Ping Connection for Transport Route

We have enhanced the transport functionality to let you check the connectivity first after you have created the transport route. Now a ping function is available for this purpose.

Mapping Enhancement

We have introduced a new function to support the requirement for outbound mapping when a node is needed a certain number of times. In this case, you don’t need from the source side a sObject instance to create the occurrences of the target node. You can use the data inside the same sObject that occurs multiple times e.g. you have two types of addresses in the account like billing and shipping address and you need to create the target node only two times and not n-times as the occurrences of the sObject instance. In this case, we can use the so-called ‘Copy Node’ function to copy the target node two, three, or as many times as you need to have on the target side.

Agent Cache and SAP Cache 

For the new Agent and SAP, a caching mechanism has been implemented. This is to speed up the processing when connecting to the new agent and sap using the local cache data. Thus, jumping while run-time over the internet to Salesforce to read the metadata is not required anymore.

• Rebuild Cache After Transport is used to rebuild the cache when the user transports some objects from other organizations.
• Rebuild Cache After System Refresh is used to rebuild after refresh system from production to sandbox.
• Synchronize Cache is used to push the cache again after the synchronize.
• Restore Connection After System Refresh is used to restore all connections after refresh system. For example, it stores all the endpoint that created in salesforce to connect SAP and new agent control board

Added several new adapters

Various adapters have been added:

1. Agent Kafka adapter

It is used with a new agent to connect to the event platform which is called Apache Kafka.

• It provides a streaming event bus.
• It creates a topic from the producer and pushes the message to the consumer.
• It provides publish/subscribe functionality using the queue.

2. Agent Database adapter

It is used with a new agent to connect with database types such as Oracle, SQLServer, MySQL, PostgreSQL, MsAccess, HyperFileSQL, and Informix.

3. Agent File adapter

It is used with a new agent to connect the ftp, sFTP and FTPs server and local file. It will help in interacting with the file system to read and write data to file.

4. Agent Pulsar adapter

it is used with a new agent to connect the event platform which is called Apache Pulsar. Pulsar is basically an Event-based communication. Event-based communication contains two main components: Publish (Producer) and Subscribe (Consumer). The work of a publisher is to publish messages into a queue or topic which is Pulsar and the middleware tool like Pulsar will maintain the message, they follow the principle of Publish and Subscribe. And they will deliver messages to the consumer. Then all the applications can subscribe. For example, Youtube plays the role of a publisher, and we play the role of the subscriber(Consumer).

5. SAP S/4 HANA adapter

we are moving with you and have created the S/4 HANA connector to allow you to connect to S/4 HANA on-premise or on-cloud. We are supporting all kinds of communication protocols such as IDoc, BAPI, and ABAP Proxy. For the cloud deployment all kinds of S/4 HANA APIs either soap, rest, or OData can be consumed. All API formats are supported e.g. swagger 2.0, OpenAPI 3.0, and WSDL can be easily imported to SKYVVA, create a message type, and build the request and response by using our graphical mapping. No line of code is needed to invoke and connect through any S/4 HANA API.

6. SAP ERP adapter

Integration to SAP is our strength and we provide integration to all kinds of the SAP application landscape. Now the SAP ERP connector has been enhanced to support hierarchical data to be built in one mapping. In the previous version, the hierarchical structure has to be broken up into flat structure and multiple interfaces using workflow were needed to process a nested complex object as for example an SAP Order.

7. Agent SOAP adapter

It is used to connect the new agents to the on-premise application that enables you to invoke SOAP API.

8. Agent REST adapter

It used to connect the new agent to the on-premise application that enables you to invoke REST API.

Added Adapter Monitor in new Agent Control Board

You need to know how many files are still pending in the processing folder to have an overview. For this purpose, we have added a new function to monitor the files inside the processing folder. Now at any time, you can see how many files are still to be processed if there is a stuck. You simply have now an overview and monitor of the files to be processed in the inbound direction e.g. from File, ftp, sftp, and ftps to Salesforce.

Configuration logs of the new agent

With this configuration setting, you can define your custom setting how to handle the log e.g. how granular you want to have the traces, how big a log file should be, etc. We provide you standard log profile and you can choose and set one to become active. You also can create a custom one that reflects the need for your individual logging requirement.

Added Agent Manual Processing API

The standard processing mode is to process the database record e.g. reading from database table and push to Salesforce by a scheduler e.g. job. This is the standard default processing mode out-of-the-box for the database adapter. But sometimes there is a need to trigger and push the data at anytime you want e.g. now. Then you don’t need to wait for the scheduling period. This way allows you flexible handling of processing the database record whenever you want e.g. on-demand at your convenience.

Added the import meta in New Agent Control Board

When you are using tables, views and stored procedures of a database you need their structure definition. It is quite a time consuming and a big effort to create such a structure definition manually as message type. Therefore with this function, you can import the table, view, and stored procedure to create the message type template for use in the mapping tool.

Added various message types format

• Added SAP Function/BAPI message type template to descript the type of the business message in the SAP BAPI system.
• Created SAP Table message type template to define the type of the business message in the SAP RFC system.
• Added SAP Idoc message type template to descript the type of business message in the SAP IDOC system.
• Added Database message type template to define the type of the business message in the Database system.