Just as Anjana allows creating as many entities as needed, it is also possible to configure as many relationships as applicable.
A relationship must contain a source and a target in order to identify the two entities involved, but the rest of the metadata is fully configurable.
PK Fields
The fields that make a relationship unique in Anjana, by subtype, are:
-
name
-
source
-
target
NOTES:
-
The “name” attribute must not contain the character ‘:’ to avoid interfering with the internal logic of the application.
-
The source and target fields are only editable through the administrative API. If the object needs a different PK, the object must be cloned with different values in its PK, but the original will continue to exist.
Attributes
When a user accesses the detail of a relationship, the screen displayed is the Attributes screen, where the user can access the different functional, technical, operational, etc. attributes 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 relationship.
Lineage
On this screen, the user can consult the lineage of the non-native relationship. Unlike lineage in entities, in relationships it starts with the source and the target, and those entities are the ones that are expanded.
The objects displayed in this graph depend on the chosen lineage layer and their relationship with the relationship (whether it is source, target, and what type of relationship). It is possible to filter which entity types, relationships, and statuses are to be shown.
More detail about the graph is included in the Lineage section.
Stakeholders
Within the Stakeholders screen, the user can consult all interested parties of the relationship.
Users appear typed as:
-
Primary: the user who created the relationship
-
Secondary: a user assigned to some attribute in the template (in case the object has any attribute of type Nominal User)
Stakeholders can also be filtered by stakeholder type, role, or name.
Audit
Within the Audit screen, the user can access Anjana's internal audit, where the evolution of the relationship throughout its entire lifecycle in the tool can be viewed: its creation, workflow validations, modifications 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 origins that generate audit entries: “anjana” for internal audit and the system name for external audit.
