Process

PK Fields

The Process fields that form part of the PK are:

• name

• infrastructure

• technology

• zone

• location

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.

Attributes

When a user accesses the detail of a process, 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 process.

The process template must contain an attribute to indicate whether the process is an engine or not, used to allow creating multiple instances associated with the process 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 (flag indicated in the template), the Instances screen displays the complete list of instances, allowing access to the detail of each one.

As instances are created in Anjana (for an engine-type process), they will automatically appear in this screen. 

Relationships

In the relationships screen, the user can view existing relationships between the process and other entities in the Anjana repository.

Relationships can be:

• Direct: Relationships in which the process is source or destination

• Indirect: Relationships of the process instances with other entities

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 Process, expanding the process to see, for example, the organizational unit it belongs to, its associated instances, etc.

The objects shown in this graph depend on the chosen lineage layer and their relationship with the process. 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 process.

Users appear typed as:

• Primary: user who created or owns the process

• 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 access the internal Anjana audit where the evolution of the process throughout its entire lifecycle in the tool can be seen: creation, workflow validations, modifications, instances created, etc.

It is possible to filter by whether it is a search action, what, who and when an action was performed on that process.

The source distinguishes the different audit sources: “anjana” for internal audit and the system name for external audit.

Versions

In this screen, the user can access the list of process versions, from which the details of each one can be accessed.

In this window, the user can:

• Navigate to each process version

• Download the snapshot of each process version

• If there is a version pending approval, navigate to its validation workflow