Manage values in production or development environment
From Business Process Management, BPM and Workflow Automation Wiki | BizAgi BPMS
Contents |
Manage values in production or development environment
For all parameter entities it is necessary to define how users will interact with them. According to the use given to each one it is important to define if they are:
- Manageable in the production environment or
- Manageable in the development environment
This property is defined in development when the parameter entity is being created: Manage values in production environment only.
IMPORTANT: If users do no define the entitie's behavior it will be set by default to manageable in development.
Manageable in Production only
To be manageable in the production environment means that the entity’s values can be edited by end users via the Admin menu.
The parameter table Documents Requested, that contains all the documents that are requested to every client opening a bank account, can vary significantly over time. Required documents can be added or deleted, according to regulations. Therefore this table should be editable by end users and thus be Manageable in the production environment.
Manageable in development
Parameter entities that are manageable in development will not be displayed for edition in the production environment. That means that end users will be able to work with their data in a case but that data will not be available to be changed.
This is very useful for parameter entities that define the process flow or have a finite list of possible values.
An example of a parameter entity that should NOT be manageable in the production environment (so it is manageable in the development environment) is Gender. This table has two and only two possible values: male and female. Then, it must not be edited by end users.
Define where to manage a parameter entity
In Bizagi Studio parameter entities will look different according to their property, as shown below.
If you have trouble deciding wether an entity is manageable in production or development environment, follow these recommendations:
1. If the entity's values are used in any kind of rule like an expression, or assignment rule or in a form in validations, actions or behaviors, that entity should NOT BE MANAGEABLE in production environment.
2. If the entity's values are used to define a process flow, that entity should NOT BE MANAGEABLE in production environment.
3. If the entity needs constant updating because its values are changing often, that entity should be MANAGEABLE in production environment.
4. If the entity has a relationship the WFUser table, that entity should be MANAGEABLE in production environment.
Considerations
|
Alert: A parameter entity should be marked to be managed in Production if it is meant or planned to have new values added in the Production environment for that entity on a frequent basis. Nonetheless, it is recommended to go through the definition for all parameter entities with the Client or owner of the process who may have a better foresight on this, and give an accurate decision for this concept. |
It is necessary to take into account some considerations when defining your parameter entities:
- Values of all entities manageable in production will be available to edit in every environment independently. These values will be taken to the production environment ONLY in the first deployment.
- Values of entities manageable in development will always be taken to the production environment and will overwrite existing records or insert new ones.
- Entities manageable in production must not have collections to entities manageable in development.
- Entities manageable in development must not have any kind of relationship with entities manageable in production.
- You can convert an entity from manageable in development to manageable in production if the above conditions are met.
- You can convert an entity from manageable in production to manageable in development if: the entity has no forms associated, it is not replicated or virtualized, it has no collections, it has not been deployed and it meets the above conditions.
- The image below will describe how parameter entities can relate with each other.
<comments/>
