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
List of project templates
We can have a filter All projects or a filter that works with criteria.
This button makes it easy to find the items you're looking for. You can use an already saved filter (private or public) or specify specific filter criteria.
Click on Register to apply the filter and
Close to return to the list.
Create a new project from this template
Accesses the form for creating a project from a template, in this case the template hovered over. Projects
In this list, you can view: the Wording of the project template , its
Codeits usetemplate creation/insertiontemplate ), its
status.
Rights required : Viewing project templates
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
A view can be set for this screen: Template management
Allows you to create a new template . Project - Creation of a template
Rights required :
Viewing project templates
Creating a project template (creation)
Viewing attributes in the project (creation)
Updating attributes in the project (creation)
Allows you to modify an existing template . Project - Modification of a template
Rights required to modify a template :
Creating a project template
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)
Here are the fields found in this screen:
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.
Validates your changes. This may redirect you to the previous page on some screens.
Modifying a project template
When the template created, three tabs appear: Documents + Reports + Setting.
You can add more themes to your project, and the added elements, such as tasks, will then be copied into your project. To see how to add elements to your template Projects
Here, we will focus on the tab Setting of template project template .
The template settings template divided into five tabs:
Project - General tab
Project - Team tab
Project - Attachments tab
Project - Themes tab
Project - Workflow tab
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 Wording to copy this template.
To save, click on OK or cancel Cancel
It will be possible to directly modify the new project template .
Rights required to modify a template :
Displays the list of changes made to this template by all users.
Stocks are sorted from the most recent to the oldest date.
General tab
Here are the fields found in this screen:
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 : structure link users to a project
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 checked. Hierarchies - Hierarchy card tab
Themes tab
It is possible to view the theme. Reports in the project space menu template . It is possible to add certain reports that will be executable from the project.
Rights required : View reports in the project area)
Rights required : Project modification
In this tab, you can activate or deactivate themes for this template , and therefore for projects created using this project template :
Planning: it is possible to have the same features as in the project space: add phases and milestones, change dates, etc.Budget: it is possible to prepare the budget and add the various expense items that you want to allocate. It will only be possible to enter the target the template contain any execution data.Resource: you can access the Resource summary. You can create a team based on the scope of the future project. You will then be able to assign named resources or generic resources and enter a target workload.revenue: it is possible to access quotes and invoicesrisk: it is possible to assign risks already identified on the template modify their severity.task: it is possible to add tasks based on already identified needs, particularly for projects with a defined and restrictive methodology.exchangeThe template will template includeexchange data, which is why theexchange theme exchange in the project space menu.
Workflow tab
In this tab, you can define a workflow process. This is a process that determines validation steps. For example, I can add a standard process for a status in progress.
Here are the fields found in this screen:
This button allows you to add a workflow to 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.
This button allows you to add automation to template .
Apply to projects created from this 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 | Templates > Project template code | 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
- dashboard
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 | status task > task status code | 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 | Templates > Project template code | 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 | status task > task status code | 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 | Lists > project status > Project status code | 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 | status task > task status code | 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 | status phase or milestone > phase or milestone status code | 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 . |