Outbound Mapping

It is a feature or functionality related to data mapping in the context of working with sObjects, which typically refers to Salesforce objects in the Salesforce platform. SKYVVA application provides a user-friendly way for users to map data from a source sObject to a target data structure, and the user considers the use of a query editor to facilitate this process. Here's a breakdown of your description:

Outbound Mapping: This feature works with data integration or data transformation, where users are taking data from a source (in this case, an sObject) and mapping it to a target data structure.
Source sObject: In Salesforce, a sObject is a generic term used to represent any standard or custom object. It seems the user using a sObject as the source of data for the mapping.
Mapping Result in Table Tree View: The user experience displays the mapping result in a table tree view on the target side. This table tree view would show how the data from the source sObject maps to the target structure, making it easier for users to understand the data flow.
Query Editor: The user provides a query editor to allow users to select a sObject record. This query editor would enable users to choose a specific record from the source sObject.
Modify Data: Users can modify the data retrieved from the source sObject if needed. This suggests that the mapping process is not entirely automated and allows for manual adjustments to the mapped data.

[su_box title="Outbound Mapping " box_color="#C0C0C0" title_color="#000000"]feature is user-friendly and practical for business scenarios where users need to map data from one structure to another, especially when working with complex data integration tasks, such as when integrating with Salesforce.[/su_box]

Case2: Test Mapping with Outbound Interface

It is a feature within an SKYVVA application with outbound interfaces and testing mappings. This feature appears to be related to data transformation or integration testing. Here's a breakdown of what you've described:

Outbound Interface: This is a component of an SKYVVA application system that is responsible for sending data or messages from the system to external systems or services. Outbound interfaces are used in integration business scenarios to exchange information with other systems.
Test Mapping: This feature is used for testing purposes, specifically for mapping data from one format or structure to another. Mapping is often used in integration business scenarios to transform data from one schema to another so that it can be properly processed by the receiving system.
Two Boxes: Here are two boxes, a left box for querying data/messages and a right box for viewing test mapping results. This suggests that the Test Mapping feature has a user interface with two input areas:

Left Box (Query): This is where the user specifies the data or messages want to use for testing. You may enter queries or select data/messages from a source, such as a database, file, or previous system interactions.

Right Box (Results): This is where the user can see the outcomes or results of the test mapping process. It displays how the data/messages will be transformed based on the mapping rules the user has defined.

In essence, this feature allows you to set up test scenarios for your outbound interface by selecting or specifying data/messages in the left box and then observing how they will be transformed using the mapping rules in the right box. This can be helpful for ensuring that your integration processes are working correctly and that data is being properly transformed before it is sent to external systems.

[su_box title="Expectation:" box_color="#2a8af0" title_color="#000000"]For the outbound interface, the Test Mapping feature allows you to query messages and records to obtain the payload for testing with mapping. There are two boxes: the left box is used for querying data/messages, and the right box is used to view the results of the test mapping.[/su_box]

Required step:

Create an Integration
Create an Adapter e.g., Adapter SOAP

Create an Outbound Interface -> link with Message Type Template and Adapter

Do Mapping

Go to Interface -> click on Button Test Mapping

After click on the Test Mapping -> we can see the pop-up screen Test Mapping as below:

[su_box title="Note" box_color="#2a8af0" title_color="#000000"]

The left box is used to execute SOQL queries and query messages for the current interface. After executing, you will receive records and then you can select them to test your mapping result/payload.
The right box is used to check the mapping results/payload after the records have been executed from the left box.
The left box is used to execute SOQL queries and query messages for the current interface. After executing, you will receive records and then you can select them to test your mapping result/payload.
The right box is used to check the mapping results/payload after the records have been executed from the left box.

[/su_box]

The user interface with three buttons related to executing SOQL queries and querying data from a database. Let us explain the functions of each button based on the information provided:

Execute Button: This button is used to execute SOQL (Salesforce Object Query Language) queries and query messages. Its primary purpose is to test the results or payload mapping the queries. When the user clicks this button, it sends the SOQL query to the database and retrieves the corresponding data, which can then be used for testing or analysis.
Open Query Editor: This button is used to open a query editor interface. In this editor, the user can specify the specific objects and fields user wants to query from the database. It helps to build and customize the query statements before executing them using the Execute Button. The query statements created in the Query Editor can be sent for execution when the user is ready.
Refresh Button: The Refresh Button is used to refresh the Query Editor and possibly other components of the interface. It ensures that any changes or updates made to the query editor or the data are reflected in the interface. This can be helpful when the user working with dynamic data or making adjustments to your query.

Before clicking the Refresh Button, the user may want to make sure that the user completed necessary changes or updates in the Query Editor or other parts of the interface, and the user has to ensure that the displayed data is up-to-date. Clicking the Refresh Button will refresh the interface to reflect the current state of the data and any changes the user has made.

In summary, these three buttons are part of designed for querying and testing data using SOQL in a database, with the Execute Button for running queries, the Open Query Editor for customizing queries, and the Refresh Button for updating the interface's displayed data and status.

The section with Outbound Interface has 3 buttons:

Execute Button: is used to execute SOQL queries and query messages to test the results/payload mapping
Open Query Editor is used to query specific objects and fields from the Database to get query statements into the Query Editor on Test Mapping

When click on Open Query Editor, it alerts pop-up screen for filer query statements then click Save SOQL

After clicking Save SOQL, it gets query statements into the Query Editor on Test Mapping

Before Execute test mapping result you need to Execute SOQL for the query records you want to test Execute

After clicking Execute SOQL -> Select the Records -> then click Execute Button to test Mapping Result/Payload

Refresh Button: is used to refresh the Query Editor and the

Before clicking the Refresh Button

After clicking the Refresh Button

It is a feature or functionality in a SKYVVA application that involves testing the connection and configuration of an adapter. Here's a breakdown of the information you provided:

Test Connection Button: This button is used to initiate a connection test and check the configuration of an adapter. It is specifically designed to work with Interface V3.
Functionality: When the "Test Connection" button is clicked, it triggers a page reload that takes the user to the "Adapter Test Connection" page.
Adapter Test Connection Page: This page is divided into four sections:a. Adapter Detail: This section likely provides information about the adapter being tested, such as its name, type, and version.b. Property: This section allows users to view and possibly edit the properties of the adapter configuration.c. Existing Test Case: This section may display information about any previously saved test cases related to this adapter. It shows test case results.d. Test Connection: This is where the actual testing of the adapter's connection and configuration takes place. Users can initiate the test from here and check whether the adapter is functioning as expected.
Saving Test Cases: The users have the option to save the test cases they've performed on this page. Saving test cases can be helpful for reusing test business scenarios in the future for reference.

This functionality is part of a SKYVVA application that allows users to test and manage the configuration of adapters, specifically those using Interface V3. The "Adapter Test Connection" page provides a comprehensive interface for performing these tasks and managing test case records.

Test Connection: is used to Test Connection and check Configuration Adapter. This button just supports only the Interface V3.

When clicking on the Test Connection, it will reload the page to the Adapter Test Connection

On the 'Adapter Test Connection' page, you can see four sections: Adapter Detail, Property, Existing Test Case, and Test Connection. It allows you to test and check the Adapter configuration and also provides the option to save the Test Case that you have checked previously.

[su_box title="Result:" box_color="#2a8af0" title_color="#000000"]The Test Mapping allows you to query messages and records to obtain the payload for testing with mapping. There are two boxes: the left box is used for querying data/messages, while the right box is used to view the results of the test mapping. It also provides the payload view, giving you an idea of what the payload looks like during the callout.[/su_box]

[su_box title="Note" box_color="#2a8af0" title_color="#000000"]

Interface API Version V2/V3 (without a message type): The Test Mapping feature does not support generating the Payload; it only displays the Results Mapping.
Interface V2 for Outbound: The ‘Test Connection’ button is not supported. Instead, we display two buttons: 'Execute' and 'Refresh'.
Interface V3 with a message type: If you link an Adapter to the Interface, the Payload will be generated based on the Adapter

[/su_box]