Extended Schema

Introduction

Extended schema is a major part of the native application. It allows you to simplify the process of deploying and setting up the clients. It also lets clients efficiently locate resources like content servers effectively. The core idea of extended schema is to provide you the options to add multiple fields of the associated native actions. There are various native applications are presented in the Sapper marketplace, for which you can add multiple extended schemas based on your requirements.

Overview

Sapper allows you to use the extended schema for the native apps. With the help of an extended schema, you will be able to add various action fields for the native application. This process needs to be done from the Sapper marketplace tab. Extended schema action can be used for any native application. In the marketplace, you will get various options for modifying or adding extended schema as per the business need.

The extended schema used for the native applications is a part of the JSON schema. The Schema is a representation of JSON-based format for defining the structure of JSON data. It was written under the IETF draft which expired in 2011. It allows you to describe your existing data format.

Extended schema for Native application is associated with three core aspects i.e., Input schema, extended output schema, and evaluation configure.

With the help of the extended schema, you can add multiple child pages by allowing the extend output schema option. It will help you to add the required field for the native applications. You will also be able to customize the object field based on your requirements. This process can be done by allowing the required and popular options for the specific native applications. The role of extended schema is to add the actions based on the dependent objects based on the business requirement. You can add as many as dependent and object field based on your need. The process of using extended schema is mentioned below.

Input

Description

Input

Description

Input Schema

The Input Schema file specifies the data requirements of all the Sapper Native apps. It can act as a template to help you to create your automation easily.

Extend Output Schema

Output schema is setting up for mapping for creating a workflow for the native application. The extend output schema allow you to add a child page in the schema for adding more objects in to the native actions.

Evaluation Configure

Evaluation configure helps you to configured the criteria in the Native application. This configuration involves specifying the name of the criterion, type of stage for the criterion, description, method, URL and request types. This phase represent the flow of the input and output schema for the native application.

Steps to use Extended Schema

  1. Select the specific native app from the Sapper marketplace tab.

2. Now select the required app and click on the edit option. For example the application is ADP, now click on it and by select edit from the right hand option as shown in the image.

3. Now, click on the custom action from the application page. The form will be display on the screen.

4. Now you need to click on the add object, for adding new action field.

5. Add the objects from the dropdown. You can add the object name and model on the dropdown Label and Modle field. For example. here we have added Address field for getting the user address.

6. Now, click on the required or popular field as per your requirements. From the dependent conditions add options. We have added the country name for the first conditions, and for the second conditions we have added the country state and region.

7. Click on the extended schema for adding the specific text for the both options. For adding a extended schema you need to click on the table option from the right side of the field.

 

8. Once you click on the extended schema icon the form will be appear on the screen.

9. To add a dependent you need to click on the text icon, and the form will be appear on the screen. Here you will get the options for data type, Label, model, placeholder, dependent conditions and required/popular opt box.

 

10. Here you will get the option for string/number option for data type. You can select the required one.

 

11. You need to add the required dependent here based on your requirement. For example, here we have added the city for getting the city details of the user. Now if you want it to be required then click on the required box. On the other hand, if you want to make it optional then click on the popular box.

12. Now, save it for further process. Save it for all the fields.

 

13. Now click on save action for saving the dependent field for the native apps.

 

14. Now click on the automation tab for creating your required automation.

 

15. When you will create the automation with ADP you will get the address optional field. For example, In the address field when you will select India you will get the option field field for City. Here you can add specific city name and get the address for the users from the specific city. Click on save for saving the automation.

 

Input

Description

Examples

Input

Description

Examples

Label

The Schema labelling is a knowledge organization theory for recognition systems. In this theory, recognition constructs symbolic network descriptions of sensory data in terms of a stored knowledge base of schemas. A schema knowledge representation is formally specified.

In this context, the label is representing the object name and text position.



State and City.

Model

A schema model is a specific field, that represent the data model object for the particular field. In this context, the model is representing the object name and text position associated with the label.

State and City.

Add child

The add child button is a additional field for adding multiple field associated with the core field.

 

Data type

In this field you need to add or select the type of the data associated with the text.

String or number.

Placeholder

If you want to add a placeholder you need to fill this field.

 

Dependent condition

A dependent variable is the variable that changes as a result of the independent variable manipulation. In the dependent condition you need to mention the status of the variable.

True/False

Required/popular

The required field represent the essentiality of the objects or text. It can be decided based on the requirement. If you opt for the required option then the text or field needs to be compulsorily filed.

On the other hand, the popular field is represent the optional condition for the object or the text. If you choose popular then the data can be optional for you. These things can be use based on your need.

 

Related Article

https://sappersoftware.atlassian.net/wiki/spaces/SD/pages/286261095

https://sappersoftware.atlassian.net/wiki/spaces/SD/pages/720896010