Workspace template logic
FieldPro allows creation of child environment from one template environment, this applies mainly to clients in different countries / regions with each region working independently on their own environment. It also applies to environments created from already developed verticals i.e Retail or Agriculture.
The relationship between the parent / father and the child environment is as below:
The properties of the father template should be only set at creation (creation of the child client, or creation of new objects in the father template). Once the objects are created from father template to the child client, almost all properties should be able to be overridden except the below:
Dashboards => KPIs (existing in father template) cannot be deleted and cannot be edited (only the title can)
Workflows => steps (existing in the father template) cannot be deleted and cannot be edited
Activities => questions (existing in the father template) cannot be deleted and query cannot be edited
Lists => Attributes(existing in the father template) cannot be deleted and query cannot be edited
You can read more on the relationship here
There is little relationship between the children in the sense that any change done on one Child won't be reflected on the other children.
You can delete an attribute in the father environment and it will propagate on children environment
The properties of the father template should be only set at creation (creation of the child client, or creation of new objects in the father template). Once the objects are created from father template to the child client, almost all properties should be able to be overridden (including things like “active”).
General propagation rules:
The fathers get propagated once per day to their children. This time is defined randomly for each client, but it can be setup directly from the client setup (available for Optimetriks users only)
It is possible to force the maintenance of a workflow directly in the client setting (available for Optimetriks users only)
The propagation is possible to follow on the daily maintenance workflow (default workflow) (available for Optimetriks users only)
NB: List attribute / activity question options setup in the template can be explicitly ignored in the propagation.
In that case: they will be created during the creation of the entity (list/activity) or the creation of the sub-entity (list attribute/activity question) but they won’t be propagated anytime after.
The relationship between the parent / father and the child environment is as below:
The properties of the father template should be only set at creation (creation of the child client, or creation of new objects in the father template). Once the objects are created from father template to the child client, almost all properties should be able to be overridden except the below:
Dashboards => KPIs (existing in father template) cannot be deleted and cannot be edited (only the title can)
Workflows => steps (existing in the father template) cannot be deleted and cannot be edited
Activities => questions (existing in the father template) cannot be deleted and query cannot be edited
Lists => Attributes(existing in the father template) cannot be deleted and query cannot be edited
You can read more on the relationship here
There is little relationship between the children in the sense that any change done on one Child won't be reflected on the other children.
You can delete an attribute in the father environment and it will propagate on children environment
The properties of the father template should be only set at creation (creation of the child client, or creation of new objects in the father template). Once the objects are created from father template to the child client, almost all properties should be able to be overridden (including things like “active”).
General propagation rules:
The fathers get propagated once per day to their children. This time is defined randomly for each client, but it can be setup directly from the client setup (available for Optimetriks users only)
It is possible to force the maintenance of a workflow directly in the client setting (available for Optimetriks users only)
The propagation is possible to follow on the daily maintenance workflow (default workflow) (available for Optimetriks users only)
NB: List attribute / activity question options setup in the template can be explicitly ignored in the propagation.
In that case: they will be created during the creation of the entity (list/activity) or the creation of the sub-entity (list attribute/activity question) but they won’t be propagated anytime after.
Updated on: 22/07/2024
Thank you!