DataRaptor Loads write data to Salesforce objects from JSON or XML input.
Discover DataRaptor Types Unit | Salesforce Trailhead

In addition to functionally specific clouds such as Sales, Service, Marketing, and Commerce, Salesforce gives customers this speed and agility by offering industry-specific clouds such as Financial Services, Health, Government, Manufacturing, Consumer Goods, Communications, Media, and Energy & Utilities. These cloud solutions combine the Salesforce cloud and specific industry models, processes, and solutions tailored to the best practices of each industry.

The user is typing in Name, so this must be what is in the DataRaptor Extract. They want the Phone returned so this must be the Type Ahead Key
Design a Simple OmniScript Unit | Salesforce Trailhead

There are three types of Calculation Matrices, and their uses vary.
Standard Calculation Matrix: Used when your matrix doesn‘t need to be a part of a group or versioned row by row.
Grouped Calculation Matrix: Used to group similar matrices with the same Input and Output headers together.
Row-Versioned Calculation Matrix: Used if you have a matrix with many rows and may need to change small portions of the data at a time. Each row has its own start date and time
All Calulation Matrices are lookup tables, so “when you need to perform a lookup“ does not help you decided which calculation matrix to use.

Use the Service Management Layer Unit | Salesforce Trailhead
Calculation Procedures and Matrices
Use Calculation Procedures to run a detailed set of mathematical steps when more complex calculations are required. They are typically used for pricing. When there are a number of factors, values, and calculations, a Calculation Procedure can call one or more Calculation Matrices, which are lookup tables.

Meet OmniStudio Unit | Salesforce Trailhead
To achieve the best results (read: happy customers) in a limited amount of time, these interactions need to be efficient, accurate, and personal. They also need to be completed via a channel of the customer’s choosing.

For This Data Input Source | Use This OmniScript Action Element
Salesforce Org—One field only | Lookup
Salesforce Org—Many fields | DataRaptor Extract Action
API | HTTP Action
Anything that Apex can access | Remote Action
User | Any Inputs Element
https://trailhead.salesforce.com/content/learn/modules/omnistudio-omniscript/create-a-simple-omniscript?trail_id=get-to-know-omnistudio

Display Data and Actions on a FlexCard Unit | Salesforce Trailhead

FlexCards summarize contextual information at a glance.
FlexCards are the beginning and ending points for customer transactions.
FlexCards are viewable on any device or channel.
FlexCards can display data from multiple data sources.
FlexCards are built quickly using drag-and-drop elements.
FlexCards have a what-you-see-is-what-you-get (WYSIWYG) editor for controlling their layout and style.
FlexCard actions are relevant to the context of the card.
FlexCards are embeddable in other FlexCards.
FlexCards are embeddable inside an LWC OmniScript.
FlexCards display more detail on demand with flyouts.
FlexCards have multiple states that display based on conditions.

Meet OmniStudio Unit | Salesforce Trailhead

FlexCards summarize contextual information at a glance.
FlexCards are the beginning and ending points for customer transactions.
FlexCards are viewable on any device or channel.
FlexCards can display data from multiple data sources.
FlexCards are built quickly using drag-and-drop elements.
FlexCards have a what-you-see-is-what-you-get (WYSIWYG) editor for controlling their layout and style.
FlexCard actions are relevant to the context of the card.
FlexCards are embeddable in other FlexCards.
FlexCards are embeddable inside an LWC OmniScript.
FlexCards display more detail on demand with flyouts.
FlexCards have multiple states that display based on conditions.

DataRaptor Extract, DataRaptor Load, and DataRaptor Transform also do the following.
Trim, map, restructure, and transform data in JSON, XML, or Custom Schema.
Use formulas and functions to transform data.
Discover DataRaptor Types Unit | Salesforce Trailhead

The OmniScript Designer lets you create the structure of an OmniScript using “clicks, not code.” It has a drag-and-drop interface with what-you-see-is-what-you-get (WYSIWYG) editing.

A FlexCard can also have None as its data source. A child FlexCard doesn’t need a data source if a parent FlexCard is set up to push data from its source to that child. A parent FlexCard may not need a data source if the child FlexCard has one.
Custom (not None) uses sample JSON to set up a FlexCard with temporary data that will eventually be replaced with another data source.
Meet the Data Source Wizard Unit | Salesforce Trailhead

Meet OmniStudio Unit | Salesforce Trailhead

For each Object in the Input JSON, the DataRaptor Load looks at each field.If the field is marked Is Required For Upsert, the DataRaptor Load checks to see if the field has data.All Is Required For Upsert fields must have data. If not, the DataRaptor Load skips that record.
Build a DataRaptor Turbo Extract and DataRaptor Load Unit | Salesforce

OmniStudio Foundation (salesforce.com) Page 5(21)

Objective | DataRaptor Type
Get data from a single Salesforce object | DataRaptor Turbo Extract
Get data from one or more Salesforce objects | DataRaptor Extract

1. The Digital Experience Layer
The Digital Experience layer includes two primary user interface (UI) components.
OmniStudio FlexCards: Cards that display contextual information and actions in an at-a-glance format for customer account data
OmniScripts: A guided path to complete a business process
These declarative tools provide rich user interaction experiences that are easily understandable. They’re built on Salesforce Lightning web components (LWC), which run inside Salesforce and improve UI performance.
2. The Service Management Layer
The Service Management layer includes data services that read, write, transform, calculate, and track data within and outside of Salesforce.
OmniStudio DataRaptors: Configurable services for retrieving, transforming, and updating data
OmniStudio Integration Procedures: Declarative, server-side processes that execute multiple actions in a single server call
DataRaptors and Integration Procedures deliver data to and from UI components. They orchestrate calls to Apex classes, calculation engines, and external application programming interfaces (APIs) to execute whatever business logic is required by the process.
The layer also includes calculation tools to look up data and configure complex math on top of the Salesforce Platform.
3. The Developer Experience Layer
The Developer Experience layer is an application lifecycle layer of tools for developers to manage and move OmniStudio component changes between environments. These developer tools are:
IDX Build Tool: Command-line automation tool that packages and migrates OmniStudio Datapacks in a source-control-friendly format
IDX Workbench: Desktop application that enables developers to migrate Datapacks and Salesforce metadata from one org to another or from an org to a Git repository

When placed outside a step, Actions execute automatically in the order they appear. When placed inside a step, an Action appears as a button that must be clicked before it executes.
Create a Simple OmniScript Unit | Salesforce Trailhead

To convert to/from Child Card the FlexCard must be cloned and then the setting toggled. It cannot be done from the header.

For This Data Input Source | Use This OmniScript Action Element
Salesforce Org—One field only | Lookup
Salesforce Org—Many fields | DataRaptor Extract Action
API | HTTP Action
Anything that Apex can access | Remote Action
User | Any Inputs Element
https://trailhead.salesforce.com/content/learn/modules/omnistudio-omniscript/create-a-simple-omniscript?trail_id=get-to-know-omnistudio

DataRaptor Extract, DataRaptor Load, and DataRaptor Transform also do the following.
Trim, map, restructure, and transform data in JSON, XML, or Custom Schema.
Use formulas and functions to transform data.
Discover DataRaptor Types Unit | Salesforce Trailhead

What It Is | What It Does
Cache Block | Saves the output of the steps within it to a session or org cache for quick retrieval.
Stores frequently accessed and infrequently updated data, which saves round trips to the database and improves performance
Allows data updates without caching
Allows different cached data to expire at different times
Conditional Block| Executes if a specified condition is true or treats the steps within it as a series of mutually exclusive alternatives
Supports branching workflows, which function like conditional views in an OmniScript
Loop Block | Iterates over the items in a data array, enabling the Actions within it to repeat for each item rather than requiring separate Action elements for each item
Try-Catch Block | Lets you “try” running the steps inside the block and then “catch” the error if a step fails
https://trailhead.salesforce.com/content/learn/modules/omnistudio-integration-procedures/explore-omnistudio-integration-procedure-designer?trail_id=get-to-know-omnistudio

OmniScripts
An OmniScript gives customers a guided path for completing a business process and serves as a configurable way of creating a seamless customer experience (which is always a good thing).
For example, consider if a customer wants to:
View and update their contact information, which is stored in Salesforce.
View their service plan, which is stored in a legacy database.
View their bill, which is stored in a billing system; choose to pay it; and select a specific way to pay it.

Full list can be viewed here: Explore the FlexCard Designer Unit | Salesforce Trailhead

The Designer’s Fantastic (and Fast) Features
With OmniScript Designer’s features, you can:
Build your OmniScripts on a wide and adjustable canvas, and instantly view changes made to element properties.
Search for and drag elements onto the canvas from the Build panel.
Reposition, clone, and adjust the width of elements with a 12-column snap-to-grid.
Configure elements from the Properties panel.
Configure script-wide settings from the Setup panel.
Access inactive elements and navigate between them in high-level and detailed views from the navigation panel.
Preview, test, and debug your script in Preview.
View contextual in-product help to discover and learn about elements and properties without leaving your script.

The Developer Experience Layer
The Developer Experience layer is an application lifecycle layer of tools for developers to manage and move OmniStudio component changes between environments. These developer tools are:
IDX Build Tool: Command-line automation tool that packages and migrates OmniStudio Datapacks in a source-control-friendly format
IDX Workbench: Desktop application that enables developers to migrate Datapacks and Salesforce metadata from one org to another or from an org to a Git repository
For simple migrations, developers can export and import the component as a Datapack, a collection of OmniStudio components packaged together for exporting and importing purposes. For example, developers can export and import a FlexCard with a specific Integration Procedure.
For large or complex migrations, developers use either IDX Build Tool or IDX Workbench.
IDX Build Tool preserves dependencies, validates data, and verifies the success of migration.
IDX Workbench includes a Test Console where users can run Test Procedures and view Gantt charts of their step-by-step performance. A Test Procedure is an Integration Procedure that performs a unit test of almost anything an Integration Procedure can invoke, such as a DataRaptor, a Calculation Matrix, an Apex class, or even another Integration Procedure

Use the link below, refer to Build an Integration Procedure to Save Data section.
Build Simple Integration Procedures Unit | Salesforce Trailhead

Saves data to one or more Salesforce sObjects by:
Updating Salesforce records
Creating Salesforce records
Migrating CSV data into Salesforce records
Discover DataRaptor Types Unit | Salesforce Trailhead

Integration Procedures only send and receive the data you need. An often overlooked performance factor is the amount of data being sent between the browser and the server. The Integration Procedure’s Response action allows you to trim the data returning to the browser from the server. This minimizes client/server data transfer, which is a key factor if you’re on a slow network or using a mobile connection.
Get Started with OmniStudio Integration Procedures Unit | Salesforce

Refer to Build, Properties, Style, and Setup Panels: Explore the FlexCard Designer Unit | Salesforce Trailhead

You can configure icons to perform actions when clicked. Image, Block, and Toggle elements also have this capability.
The Menu element creates a menu from a list of actions on a FlexCard.
Display Data and Actions on a FlexCard Unit | Salesforce Trailhead

Refer to Build, Properties, Style, and Setup Panels section: Explore the FlexCard Designer Unit | Salesforce Trailhead

A matrix will only run if the current date and time is between the Start Date/Time and End Date/Time. A matrix with a blank End Date/Time still runs; it is merely set up to run indefinitely.

Features of the Style Panel
You configure the look and feel of a FlexCard by styling individual elements and the fields within elements. Using the Style panel, we design backgrounds, text, and borders, and adjust heights, widths, and the spacing inside and between elements. There are also specific style options available for the following elements.
Action
Datatable
Field
Icon
Menu
Toggle

Display Data and Actions on a FlexCard Unit | Salesforce Trailhead

Display Data from Multiple Data Sources
An OmniScript can display both internal data from Salesforce and external data from a website or a third-party legacy system.
OmniScript’s data-oriented Actions elements call application programming interfaces (APIs), OmniStudio Integration Procedures, and other tools to access data from anywhere. You integrate data from multiple sources (Salesforce or third-party), manipulate the data, and send it back to its source, all from within the OmniScript. The data is captured in the standard JSON format.
Learn the Fundamentals of OmniScripts Unit | Salesforce Trailhead

Toggle between Design view and Preview, create a new version of your FlexCard, and clone, activate, or deactivate your FlexCard.
There is no such thing as freezing a FlexCard.

OmniScript <->IntegrationProcedure<->DataRaptor Extract<->Salesforce
and
OmniScript <->IntegrationProcedure<->DataRaptor Post<->Salesforce
Incorrect.  DataRaptor Load is required – not Extract or Post.
IntegrationProcedure –>OmniScript <->DataRaptor Load<->Salesforce
This option is incorrectbecause OmniScript must be before the Integration Procedure in the data flow.
Create a Simple OmniScript Unit | Salesforce Trailhead

The Service Management Layer
The Service Management layer includes data services that read, write, transform, calculate, and track data within and outside of Salesforce.
OmniStudio DataRaptors: Configurable services for retrieving, transforming, and updating data
OmniStudio Integration Procedures: Declarative, server-side processes that execute multiple actions in a single server call
DataRaptors and Integration Procedures deliver data to and from UI components. They orchestrate calls to Apex classes, calculation engines, and external application programming interfaces (APIs) to execute whatever business logic is required by the process.
The layer also includes calculation tools to look up data and configure complex math on top of the Salesforce Platform.

View basic metadata about your FlexCard, such as Author, Version, Status, the FlexCard it has been Cloned From, whether it is a Child Card, Last Modified date, and Theme.
Explore the FlexCard Designer Unit | Salesforce Trailhead

Element Type | What Is It For?
Actions | For calling on other tools to perform various actions: getting or saving data, calculating, sending an email, and so on
Display | For displaying text and images on the screen to enhance the usability of the UI
Functions | For performing calculations within the OmniScript, showing conditional messages, and providing geolocation
Group | For grouping elements together on the UI
Inputs | For system or user input or selection
OmniScripts | Reusable OmniScripts to insert and use

Lightning: This references the Salesforce Lightning Design System.
Newport: This references Vlocity‘s style guide.
Newport is the CSS framework that allows customers to re-theme all the Vlocity components in one place. It is intended as a tool for both designers and web developers to easily re-style all the Vlocity components in a single place and generate custom, optimized CSS files that can be used consistently across all components and pages.

OmniStudio Foundation (salesforce.com) Page 5(21)

The name and author must only contain underscores and alphanumeric characters. It must be unique, begin with a letter, not include spaces, not end with an underscore, and not contain two consecutive underscores.

When you’re ready to configure DataRaptors, you use the OmniStudio DataRaptor Designer. You can access it via the OmniStudio DataRaptors tab in the OmniStudio app. The designer has tabs too. Use the following designer tabs to specify what you want the DataRaptor to do.
Extract tab
Formulas tab
Output tab
Options tab
Preview tab

A Calculation Matrix adds to the functionality of OmniScripts and OmniStudio Integration Procedures. As you know if you’ve completed other OmniStudio modules, an OmniScript is a tool to design and create guided business processes for users, and OmniStudio Integration Procedures is a tool that retrieves, saves, and manipulates data behind the scenes. You can call a Calculation Matrix from either tool using the Matrix Action.

Save styles in a FlexCard to reuse on other elements in the FlexCard. Save the style as a custom style in the Style panel, then apply the saved style to other elements of the same type.
Saved styles are only available within the FlexCard. You can only save the styling that you’ve done within the Style panel, not any styling done in the Properties panel of the element.
Style FlexCard Elements Unit | Salesforce Trailhead

Via a Computer Telephony Integration (CTI) screen, the call center agent launches into a console page that shows information about the caller and their account. The page displays a set of FlexCards, which present relevant information and actions for a specific context and render data received from multiple sources

Complete list can be viewed Explore the FlexCard Designer Unit | Salesforce Trailhead

Display Data from Multiple Data Sources
A FlexCard can display a combination of internal information from Salesforce and external information from a website or a third-party legacy system. The FlexCard displays this information uniformly, even if it has come via multiple sources. For example, Sophia Fournier’s profile FlexCard displays internal data from her account details and external data related to the weather.

Select Source Type
From the following options, indicate which type of datasource you would like to use.
None
SOQL Query
Use the Salesforce Object Query Language (SOQL) to search your organization’s Salesforce data for specific information.
SOSL Search
Use the Salesforce Object Search Language (SOSL) to construct text-based search queries against the search index.
Apex Remote
Apex Remote data source is used to make a Apex Remote call.
Apex REST
Apex REST data source is used to make a Apex REST call.
DataRaptor
DataRaptor data source is used to make calls to Vlocity DataRaptors.
REST
Uses the standard REST API call.
Integration Procedures
Integration Procedure data source is used to make calls to Vlocity Integration Procedures.
Streaming API
Streaming API enables streaming of events using push technology and provides a subscription mechanism for receiving events in near real time.
Custom
Uses the sample JSON provided.

Salesforce Lightning Web Components
When activated, FlexCards and OmniScripts become Lightning web components. Thanks to this UI technology, users launch LWC-enabled OmniScripts as flyouts to display additional information when they click an action on a FlexCard

OmniStudio Integration Procedures are applications used to read and write data from Salesforce and from external systems. An Integration Procedure can be called from an OmniStudio component such as an OmniScript or FlexCard, an API, or even from an Apex method.
Get Started with OmniStudio Integration Procedures Unit | Salesforce

OmniStudio Calculation Procedures allow you to perform multiple mathematical operations and transformations at the same time. They take inputs as formatted JSON data and use lookup matrices, algebraic operations, and aggregation operations to calculate new data. They output specified data in formatted JSON and they can have conditional steps.
Perform Complex Math with Calculation Procedures Unit | Salesforce

Display Data and Actions on a FlexCard Unit | Salesforce Trailhead

What It Is | What It Does
Cache Block | Saves the output of the steps within it to a session or org cache for quick retrieval.
Stores frequently accessed and infrequently updated data, which saves round trips to the database and improves performance
Allows data updates without caching
Allows different cached data to expire at different times
Conditional Block| Executes if a specified condition is true or treats the steps within it as a series of mutually exclusive alternatives
Supports branching workflows, which function like conditional views in an OmniScript
Loop Block | Iterates over the items in a data array, enabling the Actions within it to repeat for each item rather than requiring separate Action elements for each item
Try-Catch Block | Lets you “try” running the steps inside the block and then “catch” the error if a step fails
https://trailhead.salesforce.com/content/learn/modules/omnistudio-integration-procedures/explore-omnistudio-integration-procedure-designer?trail_id=get-to-know-omnistudio

For This Data Input Source | Use This OmniScript Action Element
Salesforce Org—One field only | Lookup
Salesforce Org—Many fields | DataRaptor Extract Action
API | HTTP Action
Anything that Apex can access | Remote Action
User | Any Inputs Element
https://trailhead.salesforce.com/content/learn/modules/omnistudio-omniscript/create-a-simple-omniscript?trail_id=get-to-know-omnistudio

The Digital Experience Layer
The Digital Experience layer includes two primary user interface (UI) components.
OmniStudio FlexCards: Cards that display contextual information and actions in an at-a-glance format for customer account data
OmniScripts: A guided path to complete a business process
These declarative tools provide rich user interaction experiences that are easily understandable. They’re built on Salesforce Lightning web components (LWC), which run inside Salesforce and improve UI performance.

States do not have priorities.
Only one state will display at a time. The first state to evaulate to true (from top to bottom) will display.
Discover the Key Capabilities of FlexCards Unit | Salesforce Trailhead

Element Type | What Is It For?
Actions | For calling on other tools to perform various actions: getting or saving data, calculating, sending an email, and so on
Display | For displaying text and images on the screen to enhance the usability of the UI
Functions | For performing calculations within the OmniScript, showing conditional messages, and providing geolocation
Group | For grouping elements together on the UI
Inputs | For system or user input or selection
OmniScripts | Reusable OmniScripts to insert and use

There are three types of Calculation Matrices, and their uses vary.
Standard Calculation Matrix: Used when your matrix doesn‘t need to be a part of a group or versioned row by row.
Grouped Calculation Matrix: Used to group similar matrices with the same Input and Output headers together.
Row-Versioned Calculation Matrix: Used if you have a matrix with many rows and may need to change small portions of the data at a time. Each row has its own start date and time
All Calulation Matrices are lookup tables, so “when you need to perform a lookup“ does not help you decided which calculation matrix to use.

Setup Panel
You configure multiple settings when you create a FlexCard using the data source. For existing FlexCards, go to the Setup panel (1) to update these settings or configure more settings.
Update your Data Source.
Apply custom permissions to limit access to your FlexCard.
Track Custom Data on elements with tracking enabled.
Enable Multi-Language Support, set Session Variables, and create Event Listeners.

In addition to these benefits, replacing Apex classes with Integration Procedures has several perks. For example, Integration Procedures:
Are much easier to maintain and update.
Take up to 97% less development time.
Get Started with OmniStudio Integration Procedures Unit | Salesforce