This page describes the Process object in Anjana Data Platform. It covers, on the one hand, the attributes that make up its primary key (PK) — and which form its ARI, the identifier used to uniquely represent each object in Anjana — and, on the other hand, the tabs that display the object's information in its detail view.
Primary Key (PK) and ARI
Each object in Anjana Data Platform is uniquely identified by its ARI (Anjana Resource Identifier), which is built from the attributes that make up its primary key (PK). In the case of the process, these attributes — with their internal naming shown in parentheses — are:
-
name
-
infrastructure
-
technology
-
zone
-
location or logical plugin path (
path)
The ARI also includes the object's organizational unit (organizationalUnit). For example, for a process with ID 65:
ANJA:OBJECT:ENTITY:PROCESS:65:Motor de Consolidación:Europe/SPA/Risk:Google:gcpBigQuery:devQA:/Consolidacion
where the structure is:
ANJA:OBJECT:ENTITY:PROCESS:<idProcess>:<name>:<organizational unit>:<infrastructure>:<technology>:<zone>:<path>
NOTES:
-
The name attribute must not contain the ':' character, since it is the separator used between the ARI components and would interfere with the application's internal logic.
-
To ensure that the fields making up the ARI are not editable, it is the administrator's responsibility to configure these attributes in the templates with "not editable" validations. Any manual intervention to modify these values will break the object's referential integrity.
-
If the object needs to have a different PK, the object must be cloned with different values in its PK; the original will continue to exist.
-
The values of infrastructure, technology, zone, and organizationalUnit that appear in the ARI do not necessarily match what the user sees in the template. If multi-language support has been configured, the translation key is what forms part of the ARI, while the user sees in the template the translation value of that key for the language selected in their profile.
Detail Tabs
The detail view of a process is organized into several tabs, each containing a type of information about the object. When accessing the detail view, the screen shown by default is Attributes.
The availability of the «Relationships», «Lineage», «Stakeholders», «Audit», and «Versions» tabs depends on the permissions assigned to the user's role. When access to a tab is disabled, it is displayed in gray and the user cannot navigate to it. If a user believes they should have access but do not, they should contact the Anjana Data Platform administrator.
Attributes
When a user accesses the detail view of a process, the screen shown is Attributes, 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 that particular process.
The process template must contain an attribute indicating whether the process is an engine or not; this is used to determine whether multiple instances associated with the process can be created, or only one. This attribute can be defined in any menu and section of the process template and must be of boolean type. The name of this attribute must be 'isEngine'.
Own Instances
Since a process can have one or more instances depending on whether it is considered an engine or not (a flag indicated in the template), the Instances screen displays the full list of instances, allowing access to the detail of each one.
As instances are created in Anjana (in the case of an engine-type process), they will automatically appear on this screen.
Relationships
On the relationships screen, the user can view the existing relationships between the process and other entities in the Anjana repository.
Relationships can be:
-
Direct: Relationships in which the process is the source or the target
-
Indirect: Relationships between the process's instances and other entities
Relationships can also be filtered by the name and subtype of the related entity, the relationship type (source or target), and the name and subtype of the relationship.
Lineage
On this screen, the user can view the Process's lineage, and can expand the process to see, for example, the organizational unit it belongs to, the instances associated with it, etc.
The objects shown in this graph depend on the chosen lineage layer and its relationship with the process (whether it is the source, the target, and the type of relationship). It is possible to filter which entity types, relationships, and statuses are shown.
More detail about the graph is included in the Lineage section of this Guide.
Stakeholders
On the Stakeholders screen, the user can view all the parties involved in the process.
Users are typed as:
-
Primary: the user who created or owns the process
-
Secondary: a user assigned in a template attribute (in case the object has an attribute of the Named User type)
Stakeholders can also be filtered by stakeholder type, role, or name.
Audit
On the Audit screen, the user can access Anjana's internal audit trail, which shows the evolution of the process throughout its entire lifetime in the tool: its creation, its workflow validations, the modifications it has undergone, instances created…
It is possible to filter by whether it is a search action or not, and by what, who, and when an action was performed on that process.
The origin allows distinguishing between the different sources that generate audit records: "anjana" for internal audit, and the system name for external audit.
Versions
On this screen, the user can access the list of process versions, from which the detail of each one can be accessed.
On this screen, the user can:
-
Navigate to each of the process's versions
-
Download the snapshot of each process version
-
If there is a version pending approval, navigate to its validation workflow