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