Context

<< Click to Display Table of Contents >>

Navigation:  Bizagi Studio > Process wizard > Data Modeling > Entity types > Process entity >

Context

Overview

The context is the starting point of the data model that determines how the user navigates through the set of attributes and how the information is built.

 

Therefore, for the user interface, business rules, and notifications it is very important to observe the context of the Process and that of the item you are creating.

 

One of the entities in the data model will always the context and according to it the user will be able to move from one entity to another and obtain the information.

 

The context of a process is defined by the Main Process Entity. Remember that the Process Entity is the starting point through which a user accesses the rest of the data model entities. The context is determined by the Process and so, according to the Process, the information will be stored and presented differently.

 

For example in a Purchase Request Process, the context is Purchase Request. It is the main Process Entity through which the rest of the data model can be reached.

 

Context is business rules

 

 

Context in Forms

Forms that are built from the third step of the Process Wizard will have the Process Entity as Context.

Forms that are reusable are built in specific entities. Their context is the Entity in which they are developed.

This topic is discussed in further detail in the Context in Forms section.

 

Context in Business Rules and Expressions

Business Rules are created with the context of the Main Process Entity when they are built from the Process Wizard (the fourth step).

 

If you are building a visibility rule the context is the entity where the rule is evaluated, that is the entity of the Form.

This topic is discussed in further detail in the Manage user interface section.

 

When expressions are built to validate table information, the context of this rule will be the collection Entity, or Many entity in a one-to-many relationship.

Remember you need a one-to-many relationship to define a collection and relate a table in a Form.

 

Context in E-Mails

The To field defines the context in E-Mails. The context changes in E-Mails apply to one-to-many relationships, when the To field contains a collections of E-Mail addresses.

 

When the To field contains a fixed e-mail address or it is taken from a Related-entity relationship of the Data Model, the context will always be the Process Entity.

When the To filed contains a collection,  you can choose between the Process Entity or the Many Entity as the context.