Overview
The Configuration → Types section is used to manage the forms associated with your entities in ProgressionLIVE (tasks, customers, equipment, products, human resources, and more).
This is where you can:
Create or modify custom fields
Organize fields into property groups (sections)
Manage permissions (who can view and edit fields)
Reuse or duplicate fields to save time
Identify which task types use a particular base task type (form)
⚠️ Important: Modifying a form can impact multiple task types if they share the same base type.
⚠️ Important: Avoid storing sensitive information (credit card numbers, social insurance numbers, etc.) in ProgressionLIVE.
Accessing the Menu
Open Configuration.
Click Types.
⚠️ Until an entity type is selected, the page will remain disabled (greyed out).
Understanding the Interface
The screen is divided into three sections:
Type
The available forms for the selected entity (e.g., customer types, task types, etc.).
Property Group
The sections within the form (e.g., General Information).
Property Definition
The fields contained within the selected group (e.g., Technician Notes).
Simple Rule
Selecting an item on the left displays its contents on the right.
1) Type
The Type section (left column) displays the different form templates available for the entity selected in the upper-left corner.
A type represents one of the customizable entity templates available in ProgressionLIVE.
General Columns
Name: Display name
ID: Internal identifier
Entity-Specific Information
Base Task Types
A column displays the task type prefixes that use this base type (form).
Example:
Multiple task types can share the same form.
Other Types (Customers, Equipment, etc.)
Default Type: Indicates which type is automatically selected when creating a new record.
💡 When creating a new type, it is recommended to duplicate the type with the most similar form rather than building everything from scratch.
2) Property Group
A Property Group represents a section within a form (e.g., General Information, History, Requester).
After selecting a type in the left column, its groups appear in the center column.
Important Columns
Index: Controls the display order of sections (top to bottom)
Group Configuration
When opening a group, you can configure:
Name / Identifier
The Name can be changed without significant impact.
The Identifier is used by the system. Avoid changing it after creation.
Read Only
Makes the entire group non-editable, even if a role normally has write permissions.
Multiple Values
Converts the group into a data table.
Unique option:
Prevents duplicate entries.
Group Permissions
For each role, you can configure:
None: The group is hidden from the role.
Read Only
Read and Write
⚠️ If a group is hidden, none of its properties will be displayed, even if some fields would otherwise be visible individually.
3) Property Definition
A Property Definition represents a field within a group.
After selecting a group in the center column, its fields appear on the right.
Important Columns
Index: Display order of fields
Name / Identifier
Data Type
Permissions
Available Data Types
Below are the most commonly used data types.
⚠️ Note: Avoid storing sensitive information (credit card numbers, social insurance numbers, etc.) in ProgressionLIVE.
Text and Formatting
TEXT: Single-line text
TEXTAREA: Multi-line text (1024-character limit, except for the standard Description field in tasks)
PASSWORD: Hidden field (web only; not supported on mobile)
Contact Information
PHONE: Phone number (clickable on mobile)
EMAIL: Email address (clickable on mobile)
💡 Tip: Depending on your use case, you can sometimes enter multiple email addresses separated by commas. This is not supported for phone numbers.
Date and Time
DATE: Calendar with date and year selection
DATETIME: Calendar with date, year, and time selection
TIME: Time picker
Numbers
INTEGER: Whole number (decimals are ignored)
FLOAT: Decimal number (up to 6 decimal places)
CURRENCY: Monetary amount (up to 2 decimal places)
Selection Lists
LOCALIZABLE_LIST: Multilingual list (recommended)
LOCALIZABLE_OPTIONS: Multilingual list with free-text option (recommended)
LIST / OPTIONS: Legacy field types (not recommended)
✅ Best practice: Always prefer LOCALIZABLE_* field types for proper multilingual support.
Links and References
LINK: Website hyperlink
TASK_LINK: Link to another task (clickable on web, displayed as text on mobile)
ENTITY: Selection of another entity (customer, human resource, equipment, etc.)
Fixed Lists
COUNTRY
STATE
History Option (TEXT Fields Only)
The History option stores the last five entered values.
Important Notes
Stored in the browser's cookies
Not shared between users
On mobile devices, history is retained only for the current session
Creating a New Form by Duplicating a Type
To save time, you can duplicate an existing form into a new entity type.
Steps
Select an existing type (e.g., Service Call).
Click Duplicate.
Rename the type immediately to avoid duplicates.
Add or adjust groups and fields as required.
Why Use This Method?
Faster than building from scratch
Reduces the risk of forgetting important sections
Starts from an already functional form
Adding a New Property Group
Go to Configuration → Types.
Select the entity (e.g., Base Task Type).
Select the form to modify.
Click the + button (Group).
Complete the following information:
Name (FR / EN / ES as needed)
Identifier (no spaces, no capital letters)
Role permissions
Click Save.
Adding a Field to a Group
Select the desired group.
Click Add.
Complete:
Name (FR / EN / ES)
Identifier (keep permanent once created)
Data Type
Permissions
Click Save.
Permissions: Practical Reminder
Group permissions can block access even if a field itself has write permissions.
For a user to modify a field:
The group must have at least Read and Write access.
The field must also have Read and Write access (if field-level permissions are enabled).
There are therefore two permission levels:
Group permissions
Field permissions
Editing vs. Removing a Field
Removing a field deletes it, which can result in data loss or unintended side effects.
Best Practice
Instead of deleting a field, set its permissions to None to hide it while retaining its historical data.
Reassigning a Form to a Task Type
After modifying or duplicating a base task type:
Open Configuration → Task Types.
Open the task type (e.g., Service Call).
Change the Base Type field.
Save the changes (providing a reason for change).
Refresh your browser.
Without refreshing, the changes may not appear immediately.
Best Practices
Duplicate a form if the changes should apply only to specific task types.
Be consistent with identifiers. They must be unique and represent the value stored in the field.
Use specific data types (PHONE, EMAIL, INTEGER, etc.) whenever possible to simplify automations.
If you are unsure about the impact of a change—especially when reusing a base type—consult Support before proceeding.




