Managing Required and Default Fields

In ProgressionLIVE, Property Configurations define the rules that apply to fields within a task. These configurations determine whether a field becomes required when a task reaches a specific status or whether a default value is automatically assigned when the task is created.
​

For example, requiring a photo or a signature when a task is completed is a very common configuration.

Navigate to the Configuration tab and then open the Property Configuration module.

​

Important: If you do not see this module, please contact our team to request access.

This screen offers two views:
​

A Property Configuration assigns Property Rule Configurations to specific roles.

Although uncommon, it is possible to apply different property rules based on user roles. In most cases, the property configuration and rule configuration share the same name.
​

For example, a photo may not be required when the status transition is performed by an administrator.
​

​

The Property Rules view displays a table showing each property and its associated rules.
​

Three types of rules are available:
​

If the field is empty, the task cannot be saved.
​

The field becomes mandatory at a specific step in the workflow (for example: Assigned, Started, Completed, Invoiced, etc.).
​

The field is required only during specific status transitions.

For example:

Warning: This functionality is available on the web version only.
​

A value is automatically entered when the task is created.

In the example shown:

Navigate to the Configuration tab and then open the Task Types module.
​

From there, you can view all your task types and see the value displayed in the Property Configuration column.
​

The property configuration AS/MA is assigned to the task type Service Call.