CDT's are kind of representation of table structure.
Application Designers can create or import their own custom data types (CDTs). CDTs organize data into a structure that represents a logical grouping of related data, such as Doctor and Patient.
Careful attention must be paid to data types when passing the values from one variable to another (also called mapping data).
These variables can be mapped into process variables, enabling Process Modelers to access the variables in other nodes within the process model and pass the data to other processes and sub-processes.
Data types also apply to rule inputs and constants, but data from a node input or a process variable cannot be mapped to a rule input or a constant.
#) We can create CDT in 4 types/ways.
1.Create from scratch
2.Duplicate existing CDT
3.create from data base table or view (Best way)
4.Import XSD (XML Schema Definition)
Example: Employee structure is a CDT, and the best is XML Schema Definition (XSD), using this we can create /update CDT in Appian.
#) Difference between nested CDT & flat CDT ? explain with example.
Creating CDT with in a CDT is called Nested CDT.
Flat CDT will contain Primitive data type.
#) Few annotations we can use in XSD :
@ID to Primary key
@Generated Value to Auto Generation
@Table to define table name
@Column to define column
#) Relationships:-
Flat Relationship
One-to-One Relationship
Many-to-One Relationship
One-to-Many Relationship
Many-to-Many Relationship
#) primitive system data types :-
A system data type is a required format for data stored in Appian and includes primitive types and complex types. Each system data type can be used to store either a single value or a list of values.
The following primitive system data types are available
- Boolean
- Date
- Date and Time
- Encrypted Text
- Number (Decimal)
- Number (Integer)
- Text
- Time
#) Complex System Data Types :-
The following complex system types are made available in the system to support smart services.
These types cannot be edited or deleted. Their XML structure is not guaranteed to remain the same from release to release.
- ApplicationTestResult
- DataSubset
- EntityData
- EntityDataIdentifiers
- HealthCheckOutput
- IntegrationError
- LabelValue
- LabelValueTable
- ListViewItem
- Facet
- FacetOption
- ObjectTestResult
- PagingInfo
- ProcessInfo
- Query
- Save
- SortInfo
- TestCaseResult
- TestRunResult
- Writer
#) Appian Object Data Types :-
An Appian Object data type is a required format for objects specific to the Appian system. Similar to primitive and complex system types, each can be used to store either a single value or a list of values.
Appian Object data types are only recognizable within the Appian system.
- Application
- Connected System
- Data Store Entity
- Document
- Document Management Community
- Document or Folder
- Email Address
- Email Recipient
- Folder
- Group
- Knowledge Center
- Process
- Process Model
- Record Action
- Record Data
- Record Field
- Record Identifier
- Record Relationship
- Record Type
- Report
- SafeURI
- Task
- Task Report
- User
- User or Group
- User Filter
#) Record Data Types :-
This data type holds the data definition for all of the fields in a record type (or a subset of fields defined by your record type configuration), as well as the data values for the record.
When you make changes to the record type object, the record data type is also updated and stays current with any configuration changes you make.
For example, if you change the name of a record field on a record type, the change is also captured on the record data type.
The record data type allows you to easily pass record data to your interfaces, records-powered components, and expression rules.
For More Info :- Click here (Appian Site)
Note : Source of the information posted is from www.appian.com , Wikipedia and from internet.
No comments:
Post a Comment