Summary sheets - new generation (beta 7.6)
In this version, you will be able to import a file more easily:
- attributes, for PowerPoint and Word
- hierarchical links, for Word
- project roles (project team), for Word
A summary sheet contains keys that link the data in your platform to what will be entered in the sheet.
The model sheet is therefore built by calling up these keys, in a Word or PowerPoint file.
This template file is then added to the platform. See 
Add a summary sheet template to the platform
Template files
Here are some sample summary sheets:
Key operation
For project attributes, attachments or roles to appear in a summary sheet, they must be entered in a certain way in your template file.
This code must have this form: ${CODE_ATT}where CODE_ATT can be :
- attribute code on the platform
Building a summary sheet - Available project attributes
This attribute code will be replaced by theattribute value present in your project. attribute keys can be in a text field, or contained in a table.
To find out theattribute code, access the list of project attributes via 
Administration > 
Project.
- project role code Building a summary sheet - Project team
This code will be replaced by information from the project team, such as the names of the people who have this or that role.
- code for a hierarchical structure link Building a summary sheet - Project reporting lines
This code will be replaced by information on your project's hierarchies, levels and hierarchical values.
The formatting of a rich text attribute is preserved as far as possible (colors, formatting), but may be slightly different. For example, images and tables are not included in new-generation summary sheets for the time being.
Available project attributes
attribute name | Code to enter in your model |
Wording | ${LIBELLE_PROJET} |
Code | ${PROJECT_CODE} |
Icon | ${ICONE} |
Long label | ${LIBELLE_LONG_PROJET} |
Description | ${PROJECT_DESCRIPTION} |
status | status |
Project start date | ${PROJECT_START_DATE} |
Project end date | ${PROJECT_END_DATE} |
Project creation date | ${PROJECT_CREATION_DATE} |
Update date | ${DATE_MAJ_PROJET} |
Resource scheduling date | ${RESOURCE_PLANNING_DATE} |
Date project closed | ${CLOSED_PROJECT_DATE} |
project manager | ${PROJECT_MANAGER} |
template | template |
Father project | ${PROJET_PERE} |
Project weather | ${ATT_METEO} |
Project team
To display the roles and users assigned to a project :
- Add a table to your template file.
- Complete the table with the desired data.
Here is an example of a configuration listing information on roles and users:
role | Name |
$ROLE{LABEL} | $ROLE.USER{FULLNAME} |
($ROLE{ID}, $ROLE{CODE}) | ($ROLE.USER{ID}, $ROLE.USER{LOGIN}) |
$ROLE{DESCRIPTION} | $ROLE.USER{FUNCTION}
$ROLE.USER{MAIL} |
Project reporting lines
To display attachments for a project :
- Add a table to your template file.
- Complete the table with the desired data.
Here's an example of how to configure a table listing information on hierarchical links:
structure | Value |
$HIERARCHIE{LABEL} $HIERARCHIE{CODE} | $HIERARCHIE.VALUE{LABEL}
$HIERARCHIE.VALUE{CODE} |
structure Detail | Value |
$HIERARCHIE{DESCRIPTION}
$HIERARCHIE{ID} | $HIERARCHIE.VALUE{DESCRIPTION}
$HIERARCHIE.VALUE{ID} |