The header of an asset provides a summary view of its most relevant information and allows the user to quickly contextualize the object within the governance model. This area is present in all detail views and its content may vary slightly depending on the type of asset being viewed.
In general, the header shows:
-
Asset name.
-
Object subtype, represented by its icon. To check the exact subtype, the user must hover over or click on the icon.
-
Version, only available for entities that support native versioning in Anjana Data Platform (datasets, dataset fields, processes, instances, solutions and DSAs).
-
Associated organizational unit, when applicable.
-
Triplets, infrastructure, technology and zone values when applicable. These are what allow the logical segmentation for plugin usage.
-
Location or path, the logical path used by the plugin to uniquely identify the object as part of the integration with the technology.
-
Relevant dates, such as creation and approval, whenever available for that type of object.
-
Governance status of the object (for example, draft, pending validation, approved, rejected, deprecated, expired, etc.).
.png?cb=9c6dbb2d7b2880198c4fc4b08fec49d1)
|
No. |
Metadata |
Description |
|---|---|---|
|
1 |
Version |
Indicates the version of the asset being viewed. It allows identifying whether the user is working on the current version or viewing a specific version from the history (when the object supports versioning). |
|
2 |
Organizational unit |
Shows the organizational unit (OU) to which the asset belongs. This data contextualizes the responsibility and governance scope of the object within the organization. |
|
3 |
Infrastructure |
First level of the technical location "triplet". Internally called |
|
4 |
Technology |
Second level of the triplet. Internally |
|
5 |
Zone |
Third level of the triplet. Internally |
|
6 |
Location or path |
Internally called |
|
7 |
Creation date |
Reflects when the asset was created in Anjana Data Platform. It is a key reference for traceability and auditing. |
|
8 |
Modification date |
Indicates the last update date of the asset. It allows knowing whether the object has been recently modified and is useful for tracking changes. |
|
9 |
Status |
Indicator of the governance status the object is in (for example: Draft, Pending validation, Approved, Deprecated, Expired, etc.). It determines which actions are available and reflects its position in the governance workflow. |
|
10 |
Asset version indicators |
Inform about the existence of other versions of the asset, for example, the existence of a more recent draft version. |
Additional information depending on the asset type
In addition to the common elements, the header may include specific information:
Datasets
For assets of type dataset, the header includes the technical information defined at creation, such as:
-
Infrastructure: First level of the triplet, internally called infrastructure. It corresponds to the first logical level in the segmentation carried out for plugin usage.
-
Technology: Second level of the triplet, internally called technology. It corresponds to the second logical level in the segmentation carried out for plugin usage.
-
Zone: Third level of the triplet, internally called zone. It corresponds to the third logical level in the segmentation carried out for plugin usage.
-
Location or path: Internally called path. This is the logical path used by the plugin to uniquely identify the object as part of the integration with the technology.
These attributes allow quickly identifying where the physical asset resides and in which environment it operates.
Dataset fields
For assets of type dataset field, the header includes the technical information defined at creation, such as:
-
Infrastructure: First level of the triplet, internally called infrastructure. Corresponds to the infrastructure value of the dataset it belongs to.
-
Technology: Second level of the triplet, internally called technology. Corresponds to the technology value of the dataset it belongs to.
-
Zone: Third level of the triplet, internally called zone. Corresponds to the zone value of the dataset it belongs to.
-
Location or path: Internally called
path. Corresponds to the path value of the dataset it belongs to.
These attributes allow quickly identifying where the physical asset resides and in which environment it operates.
The header also includes information about the dataset it belongs to, shown as an icon and a navigable link.
Processes
For assets of type process, the header includes the technical information defined at creation, such as:
-
Infrastructure: First level of the triplet, internally called infrastructure. It corresponds to the first logical level in the segmentation carried out for plugin usage.
-
Technology: Second level of the triplet, internally called technology. It corresponds to the second logical level in the segmentation carried out for plugin usage.
-
Zone: Third level of the triplet, internally called zone. It corresponds to the third logical level in the segmentation carried out for plugin usage.
-
Location or path: Internally called
path. This is the logical path used by the plugin to uniquely identify the object as part of the integration with the technology.
These attributes allow quickly identifying where the physical asset resides and in which environment it operates.
Instances
For assets of type instance, the header includes information about:
-
The solution it belongs to, that is, the technical contract that covers the data processing carried out by the process instance
-
The process to which the process instance belongs
This information is shown as a pointer to those entities, with an icon and a link to navigate to the object.
Solution
For assets of type solution, no additional information is included beyond the rest of the native entities.
DSA
For assets of type solution, no additional information is included beyond the rest of the native entities.
Non-native entities
The headers of non-native entities do not include additional information
However, even though the header does not show information about the triplets (infrastructure, technology and zone) or the path, these attributes may be part of the template if plugin integration has been enabled.
Relationships
The headers of relationships display the organizational unit of the source entity and target entity respectively, as well as links to the source entities and target of the relationship. This information is shown as a pointer to those entities, with an icon and a link to navigate to the object.
