In Anjana Data it is possible to generate entities that represent concepts belonging to the Business Glossary (term, report, indicator, policy…) or assets related to the Data Catalog (schemas, databases…) that fit the needs and scope of the organization.
These entities have their own metadata and their morphology must therefore be configured.
PK Fields
The field that makes a non-native entity unique in Anjana is:
-
name
NOTES:
-
The “name” attribute must not contain the character ‘:’ to avoid interfering with the internal logic of the application.
Attributes
When a user accesses the detail of an entity, the screen displayed is the Attributes screen, where the user can access the different functional, technical, operational, etc. attributes that have been defined in the template, within the corresponding menus and sections, as well as the specific attributes that are not part of the template but have been included in the particular entity.
Relationships
On the relationships screen, the user can view the existing relationships between the entity and other entities in the Anjana repository.
Relationships can be:
-
Direct: Relationships in which the entity is the source or destination
-
Composition: Native relationships created by being part of another object. This is possible if the entity is contained within a DSA
Relationships can also be filtered by the name and subtype of the related entity, the type of relationship (source or destination), and the name and subtype of the relationship.
Lineage
On this screen, the user can view the lineage of the non-native entity, and can expand the entity to see, for example, the organizational unit it belongs to, the objects it is related to, etc.
The objects shown in this graph depend on the chosen lineage layer and their relationship with the entity (whether it is source, destination, and what type of relationship). It is possible to filter which entity types, relationships, and statuses are to be displayed.
More detail about the graph is included in the Lineage section.
Stakeholders
Within the Stakeholders screen, the user can view all stakeholders of the entity.
Users appear typed as:
-
Adherents: user who has adherence to a DSA that contains the entity
-
Primary: creator or owner user of the entity
-
Secondary: user assigned to an attribute in the template (if the object has any attribute of type Nominal User)
Stakeholders can also be filtered by stakeholder type, their role, or name.
Audit
Within the Audit screen, the user can access the internal audit of Anjana where the evolution of the entity throughout its entire lifecycle in the tool can be viewed: its creation, the validations of its workflows, the modifications it has undergone…
It is possible to filter by whether it is a search action or not, what, who, and when an action was performed on that process.
The source allows distinguishing between the different sources that generate audit records: “anjana” in the case of internal audit and the system name in the case of external audit.
