This page describes the Process Instance object in the Anjana Data Platform. It covers, on the one hand, the attributes that make up its primary key (PK) — which form its ARI, the identifier that uniquely represents 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 the 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 instance, these attributes — with their internal naming in parentheses when applicable — are:
-
name
-
process (name of the process it belongs to)
-
solution (name of the solution it belongs to)
The ARI also includes the object's organizational unit (organizationalUnit). For example, for an instance with ID 67:
ANJA:OBJECT:ENTITY:INSTANCE:67:Consolidación de datos de clientes:Europe/SPA/Finance:Motor de Consolidación:Analítica de SPA Finance
where the structure is:
ANJA:OBJECT:ENTITY:INSTANCE:<idInstance>:<name>:<organizational unit>:<process name>:<solution name>
NOTES:
-
The name attribute must not contain the ':' character, since it is the separator for 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 "non-editable" validations. Any manual intervention to modify these values will break the referential integrity of the object.
-
If the object needs to have a different PK, the object must be cloned with different PK values; the original will continue to exist.
-
The instance's organizational unit will be the same as that of the owning solution.
-
The process and solution used in the instance must be approved.
-
The value of organizationalUnit that appears in the ARI does not necessarily match what the user sees in the template. If multi-language has been configured, the translation key is the one that forms part of the ARI, while the user sees in the template the translated value of that key for the language selected in their profile.
Detail Tabs
The detail view of a process instance 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 and do not, they should contact the Anjana Data Platform administrator.
Attributes
When a user accesses the detail view of an instance, 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 instance.
The instance template must contain two attributes to indicate the datasets that are inputs or outputs. This attribute can be defined in any menu and section of the instance template and must be of type ENTITY_CONTAINER. The names of these attributes must be 'instanceInDataset' and 'instanceOutDataset'.
Relationships
On the relationships screen, the user can view the existing relationships between the instance and other entities in the Anjana repository.
Relationships can be:
-
Direct: Relationships in which the instance is the source or target
-
Composition: Native relationships created by being part of another object. In the case of the instance, these are solutions that contain it as a related instance
Relationships can also be filtered by the name and subtype of the related entity, the type of relationship (source or target), and the name and subtype of the relationship.
Lineage
On this screen, the user can view the lineage of the instance, and can expand the instance to see, for example, the organizational unit it belongs to, and the solutions and processes it belongs to...
The objects shown in this graph depend on the chosen lineage layer and its relationship with the instance (whether it is a source, a target, and the type of relationship). It is possible to filter which entity types, relationships, and states to display.
More detail on the graph is included in the Lineage section of this Guide.
Stakeholders
On the Stakeholders screen, the user can view all the interested parties of the Instance.
Users appear typed as:
-
Primary: user who created or owns the instance
-
Secondary: user assigned in some template attribute (in case the object has an attribute of type Named User)
Stakeholders can also be filtered by stakeholder type, role, or name.
Audit
On the Audit screen, the user can view all of Anjana's audit information, both the internal audit generated by users through the use of the application (such as creation, workflow validations, changes made, etc.) and the external audit or dynamic lineage, which traces what happens in the systems with respect to the instance (executions, for example)
It is possible to filter according to whether it is a search action or not, and what, who, and when an action was performed on that dataset.
The origin makes it possible to distinguish between the different sources that generate audit records: "anjana" for internal audit and the name of the system for external audit.
Versions
List of the instance's versions, from which the details of all of them can be accessed.
In this window, the user can:
-
Navigate to each of the instance's versions
-
Download the snapshot of each version of the instance
-
If there is a version pending approval, navigate to its validation workflow