- Oracle Cloud ERP Adapter
- AmazonAPIGateway Adapter
- GraphQL Adapter
- Webhook Adapter
- BigMessage
- SAP BTP Graph Adapter
- SAP BTP Graph Adapter
- Microsoft SharePoint Adapter
- Add Custom Authentication Class property of Adapters
- New method InboundExecuter.executeInbound()
- New apex action for Salesforce flow for invokeCalloutV3()
- Import MetaData support EDMX format
- New Formula function to get the date and time from a date time field
- New Processing Mode for the Basket
- New tab 'Pending Event Basket' to reprocess event basket
- Reports & Dashboards Monitoring
- Applying Beautify Editor to Various Skyvva Functions
- Public SKYVVA Event To Execute Inbound and Outbound Processing
- Notification when the Scheduler Does Not Run for a Certain Time
SAP BTP Event Mesh Adapter
The SAP Event Mesh adapter is used to connect Salesforce to the SAP Event Mesh, which is a cloud-based messaging service provided by SAP. The Event Mesh enables real-time event-driven communication, allowing systems to exchange messages and data seamlessly. With the Event-Mesh adapter, you can publish and consume messages to and from the Event Mesh Queue or Topic.
Oracle Cloud ERP Adapter #
We have added the Oracle Cloud ERP adapter, which is used to establish a connection between Salesforce and Oracle Cloud ERP (Enterprise Resource Planning). Oracle Cloud ERP encompasses various modules that cover different areas of business operations. With the Oracle Cloud ERP adapter, you can seamlessly integrate and synchronize data between Salesforce and Oracle Cloud ERP, enabling efficient management of financials, procurement, supply chain, human resources, and other critical business processes. This adapter enhances interoperability and streamlines the flow of information between the two platforms, empowering organizations to optimize their operations and make informed decisions based on consolidated and up-to-date data.
AmazonAPIGateway Adapter #
The Amazon API Gateway is a tool used to build, deploy, and manage APIs. We have added the Amazon API Gateway Adapter to seamlessly connect Salesforce with the Amazon API Gateway service. With this adapter, you can integrate data by making requests and receiving responses from the API. It simplifies the integration process, allowing you to securely expose Salesforce data, integrate with external systems, and leverage the capabilities of both platforms effectively.
GraphQL Adapter #
We have added a GraphQL adapter to integrate Salesforce with other systems that support GraphQL API. GraphQL is a query language used for APIs, which provides a schema of the data available in the API and empowers clients to request only the specific data they require. GraphQL acts as a mediator between the clients and the backend services.
Webhook Adapter #
We have added a Webhook adapter for use with our Skyvva ‘V3/integratewebhook’ API for sending raw data. You can provide your own API key to access our API without authentication.
BigMessage #
We have added a BigMessage adapter to handle the sending of big messages to receivers, in order to avoid Salesforce CPU or head size limitations. This adapter creates a big message record and sends a notification to an external system, which then pulls the necessary records and creates the XML and JSON payload.
SAP BTP Graph Adapter #
We have implemented the SAP BTP Graph adapter, which enables us to use the SAP Graph service on the BTP platform. This adapter provides access to a connected business data graph of SAP-managed data, regardless of where this data is located.
SAP BTP Graph Adapter #
We have implemented the SAP BTP Graph adapter, which enables us to use the SAP Graph service on the BTP platform. This adapter provides access to a connected business data graph of SAP-managed data, regardless of where this data is located.
Microsoft SharePoint Adapter #
We have added the Microsoft SharePoint Adapter to integrate the exchange between Salesforce and SharePoint Drive. You will be able to push and pull data from SharePoint documents to Salesforce. There are four File types supported for this adapter such as XML, JSON, CSV, and Binary.
Add Custom Authentication Class property of Adapters #
We have introduced a new feature called the ‘Custom Authentication Class’ for authentication. With this feature, you can configure a custom class to build your own authentication logic. If you have unique or specific authentication requirements that are not supported by our default authentication, you now have the ability to modify, extend, or enhance our provided class to cater to your specific needs. This grants you the flexibility to implement specialized authentication logic that aligns with your specific use case, ensuring a tailored authentication experience.
New method InboundExecuter.executeInbound() #
We have added a new method, InboundExecuter.executeInbound(), for executing inbound processing. This means that you no longer need to use other tools to execute our inbound interface. You can customize your apex script and execute the inbound interface via the developer console.
skyvvasolutions.InboundExecuter.InboundControl ctrl=new skyvvasolutions.InboundExecuter.InboundControl();
ctrl.integrationName=null; // input your integration name
ctrl.interfaceName=null; // input your interface name
//xml,csv,json or imessage(message tree)
ctrl.requestPayloadFormat=null; // input your data format
//can be string or list of message tree(imssage)
ctrl.payLoad=null; // input your data
//Synchronous or ASynchronous
ctrl.mode=null; // input your mode e,g Synchronous
//if payload is csv then this field is mandatory
ctrl.csvSeparator=null; // input your separator if you data is csv
//ctrl.systemExternalId=null;
//ctrl.transferId=null;
//ctrl.runtimeParams=new Map<String,String>();
skyvvasolutions.InboundExecuter.InboundResult result=skyvvasolutions.InboundExecuter.executeInbound(ctrl);
System.debug('>hasError:'+result.hasError);
System.debug('>errorMessage:'+result.errorMessage);
System.debug('>groupMessage:'+result.groupMessage);
New apex action for Salesforce flow for invokeCalloutV3() #
The new apex action feature provides a response to the flow for invokeCalloutV3(), including the HTTP status code, response payload, HTTP header data, and interface response mapping result for the flow. For example, if you want to use the invokable method from the flow to pass data from a screen in the ScreenFlow during outbound processing, you can call the invokeCalloutV3() from the apex. This will read the data from the screen and put it into the data map. This feature is directly available in the flow, allowing you to pass the ScreenFlow field as a map and use it with our invokeCalloutV3() invokable method.
Import MetaData support EDMX format #
We already have the OData adapter in place to work with the OData API. OData has a specific data format that describes the API, called the EDMX format, which uses XML to define the API. To support this format, we have enhanced our import Metadata function.
New Formula function to get the date and time from a date time field #
We add two new formulas to extract the date and time from a date-time format of the source.
- GetDateFromDateTime(<date time>,<source format>,<target format>) returns the date from source data
- GetTimeFromDateTime(<date time>,<source format>,<target format>) returns the time from source data.
For example:
- GetDateFromDateTime(“2023-02-27T10:56:08.000+0000”,”YYYY-MM-DDThh:mm:ss”,“DD.MM.YYYY”) => The date of return is ‘27.02.2023’.
- GetTimeFromDateTime(“2023-02-27T10:56:08.000+0000”,”YYYY-MM-DDThh:mm:ss”,“hh.mm.ss”)
Note: Pattern for data must be upper case and time must be lower case
Date pattern: Y (Year), M (Month), D (Day of the month) i.e.: YYYY-MM-DD, DD.MM.YYYY
Time pattern: hh (hour), mm (minute), ss(second). i.e: hh:mm:ss, or hh:mm
New Processing Mode for the Basket #
We have added a new picklist called ‘Event Processing Based on Record Size’ to the Batch Mode Switching Behavior Mode. This picklist allows users to switch the record processing mode based on the size of the record. For example, if you keep the default setting for ‘Records Size to be Switched’ and the record you’re processing has less than 50 records, the batch will be processed immediately using event processing.
New tab ‘Pending Event Basket’ to reprocess event basket #
The new tab, ‘Pending Event Basket’, is only used for the manual reprocessing of the event basket. In this view, we only show the event basket, which was created by the event and has an event ID. You could look at the ‘Elapsed Time’ column to see how long the basket has been waiting. A long value indicates a high probability of a dying event due to hitting the governor limit. If the event cannot process the basket, the status will be either ‘worker’ or ‘processing’. Note that when the event is created, the status is set to ‘worker’. When the basket is processed, the status is set to ‘processing’. However, if the event is killed due to an unknown error or by hitting the governor limit, the status will remain at ‘worker’ or ‘processing’. If the event runs without any errors, the time in the ‘Elapsed Time’ column will be a small number, just a few seconds. If we see a few minutes, the probability is high that the event has been killed and is already dead. In this case, the user can select the basket and reprocess it. This new tab, ‘Pending Event Basket’, exists for this reason.
Reports & Dashboards Monitoring #
Reports and dashboards allow you to monitor your messages by interface or interface group. Reports present collections of data in table form, while dashboards provide visualizations that display data in chart diagrams. This feature is very helpful for analyzing messages such as:
- Which interfaces have the most volume of messages or the most failed messages?
- What is going on with the status of messages per interface, like how many failed messages, pending messages, etc.
- How many data pushes to Salesforce per hour, per day, etc.
Applying Beautify Editor to Various Skyvva Functions #
We have successfully applied the editor to several Skyvva functions, including Test Mapping, Test Connection, and View Raw Logging Payload in IMessage, and create message type. This integration of the editor enhances the payload editing like XML/JSON experience within these functionalities, providing advanced features such as syntax highlighting, code completion, and improved readability.
Public SKYVVA Event To Execute Inbound and Outbound Processing #
We have added ‘skyvvasolutions__Processing__e’ to our system, allowing for the triggering of SKYVVA Events. This update enables the seamless execution of both inbound and outbound interfaces for public events. With this feature, users can trigger two types of public events: ‘Event Data’ and ‘Notification Event’. By triggering the ‘Event Data’ event, the system executes the inbound interface, while the ‘Notification Event’ triggers the outbound interface. This new feature is highly beneficial as it eliminates the need for users to manually create events in Salesforce in order to trigger our inbound and outbound processing.
Notification when the Scheduler Does Not Run for a Certain Time #
We have implemented a new feature that alerts users when the scheduler unexpectedly stops running. This functionality is beneficial as it provides users with alerts or notifications, informing them that the scheduler has not been run since xxx. This ensures that users are promptly notified of disruptions in the scheduler’s operation.