- SKYVVA 2.42
- Put URL parameter to the SFDC2SAPPI adapter
- Message Layer Refactoring
- Different response pattern for inbound call
- Real-time CDC using Process Builder
- View chain definition in an interface as tree
- Mapping of Imported WSDL request/response/fault
- Add new operation type : Apex Class, Flow/Process
- Select field from parent sObject in Mapping editor should be possible like in the Query Editor
- WSDL generation based on message type
- Mapping editor shown fields based on the field access level of the user who login
- Process Interface manually
- Message reprocessing per interface group
- Message reprocessing per integration
- For outbound Call the response structure need to be the same like the request structure
- For Real synchronous call no need to create message
- Add new value and rename existing value for flag “Inbound Behavior”
- Enhance CDC Monitor with more fields
- New message monitor based on json payload
- Redesign Log file
- Enable using bulk 2.0 relationship in mapping tool
- Validation check on Interface when Bulk Mode is used
- Generate WSDL, Swagger 2.0 & openAPI for metadata exchange between SKYVVA and other platform
- Workflow transaction
- Rename CDC scheduler in CDC control board
- Create one single WSDL which contain request and response for a synchronous interface from SF -> SAP
- Handle request and response as a transaction for synchronous call
- Create an hint to show that the data of this field in the message monitor is very long
- Pass raw payload to the custom class
- Enhance search filter to include transaction id and transfer id
- Button on interface to export metadata
- Show the operation type of the target interface after choosing the target interface in workflow
- Add new filter to tab Scheduler to search by functional group
- Remove schedulers are deprecated from the List
- CDC Scheduler for interface Group and Interface
- Make the standard scheduler behavior
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.
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 #
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 :
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.