A project template is a model containing key information: 
Project
It is possible to create a project from this template : projects will be created in a harmonized way. Certain information entered in the project template is copied into the project created via this template.
Once created, the template can be used to create a new project and/or insert new elements into an existing project.
A template can be applied to several projects at once.
The template is useful for managing the project lifecycle, in particular via the 
Workflows and 
Automations
In a project, it is possible toSave as as a project template . The properties and structure of this project will be transferred to a new template.
List of project templates
Filter the list of project templates
Click on 
In this list, you can view: the 
Wording of the project template , its Codeits usetemplate creation/insertiontemplate ), its status.
It is possible to impose the use of templates. To do this, the user must only have the right to 
Using templates in projects and not Project creation
Clicking on the template label redirects you to the template settings.
A view can be set for this screen: 
Actions
Rights required :
Button name | Description |
|---|---|
Accesses the form for creating a project from a template, in this case the template hovered over. |
.svg)
Creating a project template
Here are the fields found in this screen:
Code If multilingual configuration is enabled, an additional field must be filled in a section Multilingual.
This field corresponds to the object label in the other language.
Creating a project template is divided into two parts:
- template creation form with general information
- template setup and structure definition
Rights required :
- Viewing project templates
- Creating a project template (creation)
- Viewing attributes in the project (creation)
- Updating attributes in the project (creation)
Shares (at inception)
Modifying a project template
When the template is created, three elements appear: documents + Reports + Settings.
Here you can modify the project template settings.
The template settings are divided into 5 tabs:
- Project - General tab
- Project - Team tab
- Project - Attachments tab
- Project - Themes tab
- Project - Workflow tab
Button name | Description |
|---|---|
With a single click, this button saves a copy of the project template currently being modified. It will appear in the list of project templates.
A window opens, allowing you to define a |
Rights required to modify a template :
Actions (upon modification)
Deleting a project template
General tab
Here are the fields found in this screen:
Code If multilingual configuration is enabled, an additional field must be filled in a section Multilingual.
This field corresponds to the object label in the other language.
Team tab
Rights required :
In this tab, you can see which roles are part of the project team (checkbox). Users can be assigned to these roles. They will therefore have more or less rights, depending on the role.
Even if roles are set as mandatory in the team, assigning roles to users will be optional here. However, once the project has been created, roles will reappear as mandatory.
Attachments tab
This tab is divided into two parts:
- template information
- Information copied when creating a project from this template.
Attachments here concern the selected project template and the projects that will be created using this template.
Even if hierarchies are set up as mandatory for project templates or projects, template links will be optional here. Once the project has been created, however, hierarchies will reappear as mandatory.
It is possible to link the project template or the project to hierarchies, if their structure link to the object project template or Project is defined on Optional or Mandatory.
Themes tab
Rights required :
The Reports theme can be viewed in the project space menu of the project template . It is possible to add certain reports that will be executable from the project. (Additional rights required: View reports in the project area)
In this tab, you can activate or deactivate themes for this template , and therefore for projects created using this project template :
- Planning: you can use the same functions as in the project area: add phases and milestones, change dates...
- Budget : Here you can prepare the budget, adding the various expense items you wish to see allocated. It will only be possible to enter target data, as the template does not include execution data.
- Resource: access the Resource overview. It is possible to create a team according to the scope of the future project. It will therefore be possible to assign named or generic resources, and to enter a target load.
- revenue : access to the
- risk : you can assign risks already identified in the template and modify their severity.
- task : it is possible to add tasks according to the needs already identified, especially for projects with a defined and binding methodology.
- exchange : The template will not containexchange data, so theexchange theme will not appear in the project space menu.
Workflow tab
Here are the fields found in this screen:
In this tab, you can define a workflow process. This is a process that determines validation steps.
I can, for example, add a standard process for a status project in the pipeline.
Button name | Description |
|---|---|
This button is used to add a workflow to the project template . |
Automation tab
In this tab, you can define an automation. Automations
It's a process that determines the validation stages.
For example, I can add an automated request validation or milestone validation function if the associated tasks have all been completed.
Button name | Description |
|---|---|
This button is used to add automation to the project template . | |
If projects were created from this template before automations were added, for example, then it is possible to apply all automations to these projects. |
Parameterization according to automation
The field Variable code is read-only: once the Single object selected, 
Project Monitor will tell you which code it refers to.
Filter on object orattribute value | Description | Trigger on last element | ||||
Apply a template |  Administration > Model settings > Templates > Project template code Project | No status (manual)
projectstatus
status document
status task
status phase
status milestone
attribute value | projectstatus : list of project statuses
status document document status : list of document statuses
status task task status list
status phase phase status list
status milestone Done" checkbox
attribute value: list of list-type project attributes | projectstatus : /
status document : /
status tasktask
type task
status phasephase or milestone
type milestone
status milestonephase or milestone
type
attribute value: list of values according to the selectedattribute | Adds the following elements of the selected template to the project:
- Attachments
- Roles
- Themes
- Forms
- Attributes
- Planning
- Resources
- Reports
- Budgets
- Automations
Replaces the following elements of the template selected on the project:
- Logo
- summary sheet
- Home page template
- Project header
- Workflow
Does not allow elements to be removed from the project in relation to the template applied. For example, if the resources theme is activated and valued in a project, when a template is applied which does not have the resources theme activated, it will remain activated in the project after the template has been applied.
If the project's current template is reapplied, the information will not be duplicated. | Not available
|
Close child tasks when parent task is closed | Administration > Field settings >  Lists > status task > task status code Lists (to meta status completed) | status task | status task list of task statuses (at completed status ) | task type: all types or one type in particular | Allows you to link the status of parent tasks to child tasks. For example, if a parent task is completed, then all child tasks will also have completed status . | The automation will be executed when the last element of the trigger type setphase, milestone, task or document) in the project is at the trigger value. |
Insert a template | Administration > Model settings > Templates > Project template code Project | No status (manual)
projectstatus
status document
status task
status phase
status milestone
attribute value | projectstatus : list of project statuses
status document document status : list of document statuses
status task task status list
status phase phase status list
status milestone Done" checkbox
attribute value: list of list-type project attributes | projectstatus : /
status document : /
status tasktask
type task
status phasephase or milestone
type milestone
status milestonephase or milestone
type
attribute value: list of values according to the selectedattribute | Adds the following elements of the selected template to the project:
- Attachments
- Roles
- Themes
- Forms
- Attributes
- Planning
- Resources
- Reports
- Budgets
- Automations
Does not allow you to remove elements from the project in relation to the inserted template . | Not available |
Change task status when milestone status changes | Administration > Field settings > Lists > status task > task status code Lists | status phase
status milestone | status phase phase status list
status milestone Done" checkbox
| status phasephase type or milestone
status milestonephase or milestone type
| When the status a schedule elementphase or milestone) is changed, all its associated tasks must change status according to what has been set in the automation.
The automation can be triggered by a certain type of phase or milestone (e.g. a scoping milestone ).
If there is no task linked to the modified phase or milestone , then the automation is not triggered. | The automation will be executed when the last element of the trigger type setphase, milestone, task or document) in the project is at the trigger value.
For example, when the last milestone in the project that has a task in dependency is "Done", then the associated tasks will change their status to Completed. |
Change project status | Administration > Field settings > Lists > project status > Project status code Lists | No status (manual)
status task
status phase
status milestone
attribute
value
status document | status task list of task statuses
status phase phase status list
status milestone Done" checkbox
attribute value: list of list-type project attributes
status document document status list | status tasktask
type task
status phasephase or milestone
type milestone
status milestonephase or milestone
type
attribute value: list of values according to the selectedattribute
status document : / | Modifies the project's "status " technicalattribute with a value from the "projectstatus " list. | Not available |
Modifying the status of the parent task | Administration > Field settings > Lists > status task > task status code Lists | status task | status task list of task statuses | task type: all types or one type in particular | Allows you to link the status of child tasks to parent tasks.
For example, if a child task changes status to current, the parent task automatically changes status to current or another status of your choice. | The automation will be executed when the last element of the trigger type setphase, milestone, task or document) in the project is at the trigger value. |
Change milestone status when task status changes | Administration > Field settings > Lists > status phase or milestone > phase or milestone status code Lists | status task | List of task statuses | task type: all types or one type in particular | When the status of a task is modified, all associated schedule elements must change status according to what has been set in the automation. The automation can be triggered by a certain type of task (e.g. a Technical task ).
If there is no milestone linked to the task, the automation is not triggered when the task changes status .
If there are several tasks linked to a planning element, then automation is triggered when the last task linked to the same phase or milestone reaches trigger status . | The automation will be executed when the last element of the project's trigger typephase, milestone, task or document) is set to the trigger value.
For example, when the last task in the project that has a phase dependency is completed, the associated phases will also be set to Completed status . |