PK Fields
The fields that make a Process Instance unique in Anjana are:
-
name
-
process
-
solution
NOTES:
-
The “name” attribute must not contain the ‘:’ character to avoid interfering with the application’s internal logic.
-
These fields are not editable (except the name). If the object needs a different PK, it must be cloned with different PK values, but the original will continue to exist.
-
The organizational unit of the instance will be the same as that of the owning solution.
-
The process and solution used in the instance must be approved.
Attributes
When a user accesses the detail of an instance, the screen shown 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 specific attributes not part of the template but included in that particular instance.
The instance template must contain two attributes to indicate the input or output datasets. 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
In the relationships screen, the user can view existing relationships between the instance and other entities in the Anjana repository.
Relationships can be:
-
Direct: Relationships in which the instance is source or destination
-
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 name and subtype of the related entity, relationship type (source or destination), and relationship name and subtype.
Lineage
In this screen, the user can view the lineage of the instance, expanding it to see, for example, the organizational unit it belongs to, the solutions and processes it is part of, etc.
The objects shown in this graph depend on the chosen lineage layer and their relationship with the instance. It is possible to filter entity types, relationships and statuses to display.
More detail about the graph is included in the Lineage section of this Guide.
Stakeholders
In the Stakeholders screen, the user can view all stakeholders of the Instance.
Users appear typed as:
-
Primary: user who created or owns the instance
-
Secondary: user assigned to a template attribute (if the object has a nominal User type attribute)
Stakeholders can also be filtered by stakeholder type, role, or name.
Audit
In the Audit screen, the user can view the complete Anjana audit, both internal (generated by users: creation, workflow validations, modifications...) and external or dynamic lineage showing what happens in the systems with respect to the instance (executions, for example).
It is possible to filter by whether it is a search action, what, who and when an action was performed.
The source distinguishes the different audit sources: “anjana” for internal audit and the system name for external audit.
Versions
List of instance versions from which each one’s details can be accessed.
In this window, the user can:
-
Navigate to each instance version
-
Download the snapshot of each instance version
-
If there is a version pending approval, navigate to its validation workflow