Objects reference
Data objects are represented as design files where each object type is defined by specifying the _type property within its respective file. For detailed guidance on creating design files and defining objects, see Create design files.
All configuration options available for an object in the Application Builder are mirrored and accessible within the Semarchy extension for VS Code.
The table below lists the various objects that can be incorporated into an MDM project designed using the Semarchy extension for VS Code.
| Object type | Object | Description |
|---|---|---|
|
Action set |
A group of actions accessible from the |
|
Application |
A set of configurations and components for an MDM application. For detailed information about this object’s properties, see Applications |
|
Business view |
A user-friendly view of business objects. For detailed information about this object’s properties, see Business views. |
|
Collection view |
A group of business entities displayed in a list, grid, or table format. For detailed information about this object’s properties, see Collections. |
|
Complex type |
A custom data type with multiple attributes using built-in types, user-defined types, or lists of values. For detailed information about this object’s properties, see Complex types. |
|
Database view |
A configuration object that creates a physical view derived from a model. For detailed information about this object’s properties, see Database views. |
|
Display card |
A configuration object that specifies how an entity record is presented in a compact format. For detailed information about this object’s properties, see Display cards. |
|
Duplicate manager |
A configuration object that identifies, manages, and resolves duplicate records within a dataset. For detailed information about this object’s properties, see Duplicate managers. |
|
Enricher cache |
A component designed to store enriched data temporarily or permanently. For detailed information about this object’s properties, see Enricher cache. |
|
Business entity |
A core component in a data model, representing a distinct object or concept with specific attributes, a unique identity, and relationships with other entities. For detailed information about this object’s properties, see Entities. |
|
Form |
A user interface form for data entry and interaction. For detailed information about this object’s properties, see Forms. |
|
Master-record ID survivorship rule |
Rule that determines which master record ID survives in case of duplicate records. For detailed information about this object’s properties, see Master-record ID survivorship rule. |
|
Legacy workflow |
A sequence of steps for managing processes using the legacy workflow feature. For detailed information about this object’s properties, see Workflows (legacy). |
|
List of values (LOV) |
A set of predefined |
|
Logical model |
A structured representation of how data entities, attributes, relationships, and business rules are defined and organized within an organization. For detailed information about this object’s properties, see Create a new model. |
|
Model diagram |
A visual representation of the logical model. For detailed information about this object’s properties, see Model diagrams. |
|
Model variable |
An element that stores session-specific or job-specific values, used for customizing user experiences and parameterizing integration tasks. For detailed information about this object’s properties, see Model variables. |
|
Integration job |
A structured process designed to integrate and validate source data, transforming it into certified golden records. For detailed information about how to configure this object, see Integration jobs. |
|
Model privilege grants |
Access control settings for the model. For detailed information about this object’s properties, see Privilege grants. |
|
Named query |
A structured configuration that defines an integration endpoint accessible via a REST API to retrieve structured data from the data hub. For detailed information about this object’s properties, see Named queries. |
|
API enricher |
A component that uses Java plugins or REST clients to perform data transformations and enhance data quality and completeness. For detailed information about this object’s properties, see API enrichers. |
|
Plugin validator |
A process leveraging Java plugins and exectued by xDM to evaluate record data against predefined rules or criteria to ensure its accuracy, consistency, and adherence to standards. For detailed information about this object’s properties, see Plugin validations. |
|
Publisher |
An application or system that provides source data to the data hub. For detailed information about this object’s properties, see Publishers. |
|
Reference relationship |
A relationship established between two entities, indicating a connection or dependency. For detailed information about this object’s properties, see Reference relationships. |
|
Search form |
A user interface for searching data. For detailed information about this object’s properties, see Search forms. |
|
SemQL enricher |
A component that enforces rules written in the SemQL language to perform data transformations and enhance data quality and completeness. For detailed information about this object’s properties, see SemQL enrichers. |
|
SemQL validation |
A rule written in the SemQL language and executed directly within the hub’s database to evaluate record data and ensure its accuracy, consistency, and adherence to standards. For detailed information about this object’s properties, see SemQL validations. |
|
Database function |
A customized operation implemented in the database hosting the data location, declared in the model, and used to perform specific tasks within database queries or applications. For detailed information about this obect’s properties, see Database functions and procedures. |
|
Standard survivorship rule |
A rule that specifies how values for attributes in fuzzy-matched and ID-matched entities are determined for golden records. For detailed information about this object’s properties, see Survivorship. |
|
Stepper |
A user interface component that organizes and guides users through sequential authoring actions like creating, editing, or importing records. For detailed information about this object’s properties, see Steppers. |
|
Unique key |
A component that identifies a set of attributes within an entity and ensures that each combination of values across these attributes is unique for every record within that entity. For detailed information about this object’s properties, see Unique keys. |
|
User-defined type |
Custom data types defined by users, acting as an alias to a built-in type and imposing user-defined restrictions such as length or precision. For detailed information about this object’s properties, see User-defined types. |
|
Data-driven workflow |
A sequence of interconnected steps that guide the progression of tasks and operations based on data-driven conditions and user interactions. For detailed information about this object’s properties, see Data-driven workflows. |