Tutorials

  1. Home
  2. Docs
  3. Tutorials
  4. 22. What is message type?
  5. 22.7 How to create tree hold in hierarchical message type?

22.7 How to create tree hold in hierarchical message type?

Learning Objectives

In SKYVVA, the MetaData repository is a component that manages metadata. In the context of database systems, one example of metadata is information about the database schema, which is a description of the data. Besides, the MetaData repository can manage information about the processes which create, use, or update the data, the components that host these processes or the database system.

As metadata is also data, metadata repositories offer the same functionality for metadata as database management systems (DBMS) for data, e.g., queries, updates, transactions, access control.

Introduction

SKYVVA API Service can use the V3 integrate Inbound web services, such as the REST API, allow you to interact with SKYVVA instance data using web service requests.

SKYVVA supports inbound web services using REST and SOAP. The REST style emphasizes that interactions between clients and services are enhanced by having a limited number of operations. Each operation (GET, POST, PUT & DELETE) has a specific meaning, REST avoids ambiguity.

The REST API is active by default in all instances.

RESTful web services offer administrators several advantages, including:

  • Support for different HTTP methods to perform different actions
  • Detailed response codes and header information
  • Streaming data on POST requests
Note
V3 integrate API service is based on process hierarchical message in our tool SKYVVA, it also shows the monitoring and a tree hold in the hierarchical message.

Go to MetaData Providers Tab

  • Click on New
  • Create MetaDeta Providers

  • Create IStructure Repository

  • Save
  • Create Message Type as Hierarchical

  • Create Message Type Name & Select Plain structure from Type picklist
  • Root_MSG-Test, AccountTestV3, ContactTestV3 & CaseTestV3 message type Name
  • Save

User Just Create Root_MSG-Test Message Type

  • Click on Related List

  • Click on Message Type (Child) New button

  • User Just Create AccountTestV3 Message Type
  • Click on Related List
  • Click on New Button of Message Type Field Entry

  • Create Account Number IStructure AccountNumber
  • Create IStructure Name
  • Create Account_ID IStructure Account_ID
  • Create Billing City IStructure BillingCity
  • Create Billing Country IStructure BillingCountry
  • Save

Great user Create Message Type Field Entry Successfully

Now the user has to Go to Related List

  • Click on Message Type (Child) New button
  • Save

  • User Just Create ContactTestV3 Message Type
  • Click on Related List
  • Click on New Button of Message Type Field Entry

  • Create Cont_ID Istructure Cont_ID
  • Create First Name Istructure FirstName
  • Create Last Name Istructure LastName
  • Create Email Istructure Email
  • Save

Great user Create Message Type Field Entry Successfully

Now the user has to Go to Related List

  • Click on Message Type (Child) New button
  • Save

  • User Just Create CaseTestV3 Message Type
  • Click on Related List
  • Click on New Button of Message Type Field Entry

  • Create Subject Istructure Subject
  • Create Supplied Phone Istructure SuppliedPhone¬†
  • Save

Great user Create Message Type Field Entry Successfully

Go to  Istructure Repository Details page

  • See how Hierarchical Type look in Tree
Was this article helpful to you? Yes No

How can we help?