Popular Search how tohow to useagenthowdatarestformulacustombatchstore
View Categories

3. New Feature

SKYVVA 2.42 #

SKYVVA conformity Spring 19 is here! We’ve introduced new features and enhancements over the past several conformity releases thanks to feedback from our customers. A few big announcements for this release include support for JavaScript, a new Conditions entity for branching operations with a script and support. We also introduced the ability to run external operations that is, operations from other projects and the ability to handle SOAP  fault codes received from applications.
Users can create APIs in any format, including REST, SOAP, JSON then run and analyze APIs through an intuitive interface. By having the ability to easily generate APIs based on existing data and apps, companies can reuse existing applications and business logic.
Internal and external API developers can now use the new Developer discover and consume APIs. They can not only rapidly expose any application or data as an API, but also optimize these APIs to deliver maximum performance and using OpenAPI (Swagger 2.0).
With rich security controls and user authentication, customers have access to advanced API analytics to monitor API performance and consumption trends, as well as comprehensive monitoring and alerting of API processes through enhanced API logging.

Put URL parameter to the SFDC2SAPPI adapter #

New URL parameter is created to pass the URL as string and append to the endpoint string in the adapter. User can put dynamic parameter value.

Message Layer Refactoring #

The message layer is redesign to be better performance. It is consuming less data storing. All fields in IMessage has changed to ‘JSON’ format, the field of IMessage are not store with IData anymore.

Different response pattern for inbound call #

This feature is created to support different response pattern for an inbound call as inbound Asynchronous message. We need to do a Synchronous call where the response is coming back in the same request context. The response is coming immediately to the sender while the caller process is blocked and wait for the response.

Real-time CDC using Process Builder #

This is a new feature, which is implementing to create change pointer record for CDT scheduler processing and send with process builder in real-time. The Real-time with process builder allow you to execute callout.

View chain definition in an interface as tree #

Previously, if user look to the root chain interface user will not see, its into one view as the tree structure even user open the section. As of now, we enhance this feature to be able to view it as a tree structure. On the tree, user can click and navigate to the corresponding interfaces.

Mapping of Imported WSDL request/response/fault #

Mapping is implementing for complex-type with in the WSDL, when it imported and message-types are generated. This implementation has to provide the run-time-logic based on MessageType / Ichain / Interface / Mapping to enable this possible relations between source and target-structures within hierarchies.

Add new operation type : Apex Class, Flow/Process #

This is the feature to provide the post-processing logic using Salesforce Flow & Process Builder. Therefore, we pass to the Flow/Process the sObject Id that has been created, updated or deleted by the interface operation. Note that currently, we support different interface operation for the inbound interface like following :

Upsert, Update, Insert, Delete, Apex Class, Platform Event, Flow/Process

 

Select field from parent sObject in Mapping editor should be possible like in the Query Editor #

This is an enhanced feature in which we redesigned the mapping tool using Lightning. We want to select field from parent sObject in mapping editor as we do in Query Editor.

WSDL generation based on message type #

Previously, the WSDL generation is based on sObject fields. However, in this version we change the generation logic to use base on the message type.

Mapping editor shown fields based on the field access level of the user who login #

Previously, mapping editor show only fields, which have sufficient field level accessibility. Some user have problem viewing since each have different access field level permission.

Process Interface manually #

Now user can process Interface manually since new column action ‘Process’ button is added to the interface tab in the Agent Control Board. The button is the same as Process button in Agent UI. User can execute each interfaces here.

Message reprocessing per interface group #

Previously, all message are reprocess at the same time using one global reprocessing scheduler. However, now user experience a new scheduler, which is flexible to run different interface group at different time.

Message reprocessing per integration #

Scheduler per integration is now enhanced to message reprocessing. It can schedule each integration at different time. User can also experience priority base frequency time interval, Interface is higher priority so it counts less time interval.

For outbound Call the response structure need to be the same like the request structure #

This is a new feature, which allows user to create Change Pointer using Query Editor. User can enter the SOQL statement for finding the business Id & further process the business Id’s respectively. User can detect either change based on  own SOQL statement.

For Real synchronous call no need to create message #

This is an enhanced feature, which create to speed up the migration of data for Synchronous. Its only save the pending message while Fail/Completed will be deleted.

Add new value and rename existing value for flag “Inbound Behavior” #

Some of existing picklist value like Synchronous & Asynchronous will be rename to Immediate and Future Apex. In the same way, a new value as like as ‘Batch Apex’ also added to flag ‘Inbound Behavior’.

Enhance CDC Monitor with more fields #

As long as CDC monitor shows the CDC records look like the attach screen, we have decide to enhance this feature as allow user to see more detail data such as sObject and the Name of sObject.

New message monitor based on json payload #

Since the field of IMessage is not store with IData anymore then all fields in IMessage has changed to json format. This feature is created to display new message monitor based on json payload. The Data2 section is like a board to read the value from IMessage.

Redesign Log file #

To prevent lock error while writing into log file we should separate log file based on the different processing.

Enable using bulk 2.0 relationship in mapping tool #

SKYVVA is now support direct sObject processing using bulk API through which user can load data using relationship name. To be able to support this, we need to be able to open the polymorphic relationship with our mapping tool. Our query tool support this, but not our mapping tool.

Validation check on Interface when Bulk Mode is used #

This feature is implementing to check validation on Interface when ‘Bulk Mode’ is used. When user checks the flag ‘Bulk Mode’ then the flag ‘Don’t Persist Message’ will check box automatically.

Generate WSDL, Swagger 2.0 & openAPI for metadata exchange between SKYVVA and other platform #

We are implementing this functionality to generate different file format from our interface such as WSDL, Swagger 2.0 & openAPI. We use this for metadata file, which generate through sObject type. We may get to Generation request and response structure in case of Synchronous interface.

Workflow transaction #

Our workflow engine is not able to support Transactionality. When an interface fails user do not rollback the whole execution path although committed what become successful. User cannot rollback to a save point. This task is to enhance our workflow engine to support Transactionality.

Rename CDC scheduler in CDC control board #

This feature is to do-able but user need to start the scheduler with new name in order to copy the setup info. from old scheduler setting. Furthermore, the user needs to manually delete the schedule with old name.

Create one single WSDL which contain request and response for a synchronous interface from SF -> SAP #

Users do not have to generate separate WSDL one for request (outbound interface) & another one for response (inbound interface) anymore. We have created a WSDL with both request and response in one file for Synchronous processing.

Handle request and response as a transaction for synchronous call #

This feature is create to show, how to reprocess a Synchronous interface because of, it contains two types of messages e.g. request (outbound) & response (inbound).

  • If user is the executor of the Synchronous call. In this case, the reprocessing and message monitor is not needed because of the user will resend it again.
  • If batch process is executor of the Synchronous call. In this case, message monitor and the reprocessing job are needed to do the resend of the failed callout.

Create an hint to show that the data of this field in the message monitor is very long #

When the data of IData field is very long, we create an attachment and store the data there. This is a good solution to store big data into the IData field. If message is longer than 35 character they will cut out the rest and display string.

Pass raw payload to the custom class #

Our integrate API get data and create from the data e.g. json or xml payload our messages. We can create flat & tree messages as with Integrate3. However, user can pass now the raw data and do not need to follow any format.

Enhance search filter to include transaction id and transfer id #

With the API Integrate3x we introduce two new fields:

  • Transaction Id – This is to define a unique transaction id for all messages belonging to a logical object like for example a sales order.
  • Transfer Id – This is a unique id like a DHL, Amazon tracking number to identify the transfer package.

Button on interface to export metadata #

We have the functionality for exporting metadata where we can find in the message type. We are providing Export Metadata Button on interface Detail page for easy access to user.

Show the operation type of the target interface after choosing the target interface in workflow #

When we define the workflow we have to choose first source interface. Then the target interface and further field Operation Type, we can set the operation type of an interface. But most of the time we use the same. e.g. we put again same operation. Therefore we should display the value from the target interface and the user can keep change it to a new one.

Add new filter to tab Scheduler to search by functional group #

We have different Scheduler for different function. To carry an easy overview we need to provide the user option, to search by the functional group. e.g. show me all Scheduler related to message reprocessing. We need to change to the picklist value to be able to select a combination of category.

Remove schedulers are deprecated from the List #

Some Schedulers have been change their name, they will be deprecated (stop working), So they must be removed from the list to avoid confusion. Eg. AttachmentProcess, AttachmentReprocess and MessageReprocess are deprecated in this new version.

CDC Scheduler for interface Group and Interface #

CDC have two Schedulers which is CDD & CDT Schedulers. We added Scheduler per interface and interface group. When we run three Scheduler (Integration, interface, interface group) at the particular then Scheduler per interface group is run always on priority

Make the standard scheduler behavior #

Scheduler is a feature of SKYVVA for setting time to other object run by their own time. There are many Scheduler based in  SKYVVA object, like on Integration detail, Batch Control Board or CDC Control Board ,etc. We can setup Scheduler work in the standard way.

  • Scheduler  is a global Scheduler for Interface or Interface Group , if it runs, it will be check if which Scheduler has run their own setting time it will be skip, it’s mean that it doesn’t work on that Interface but it will be work on which Interface that which is not running their time.
  • Among the Scheduler for Interface and Interface Group. If Scheduler for Interface Group starts, all Scheduler for Interface that stay on Interface Group will be stop immediately. And also it cannot start, if Scheduler for Interface Group are running.