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
Memo characters used:
$represents information that will be replaced by a value of
Project Monitor.POPrepresents a population key for displaying information about certain objects.SOUSPOPThe point allows you to target a specific subpopulation.{attribute}Braces are used to display a attribute[FILTER=1]the cRocksets allow you to add filters with operators.;The semicolon is used as a separator to add multiple filters.
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 information
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 information
Projects
For projects, it is possible to display:
- Label:
PROJECT_TITLE - Code:
PROJECT_CODE - Icon:
ICON - Long label:
LONG_PROJECT_TITLE - Description:
PROJECT_DESCRIPTION - status
status - Project start date:
PROJECT_START_DATE - Project end date:
PROJECT_END_DATE - Project creation date:
PROJECT_CREATION_DATE - Date of update:
PROJECT_UPDATE_DATE - scheduling date:
RESOURCE_PLANNING_DATE - Project completion date:
PROJECT_CLOSED_DATE - project manager
PROJECT MANAGER - template
template - Parent project:
FATHER PROJECT - Project weather forecast:
ATT_WEATHER
and all attributes with codes
Project roles
For project roles (project team), it is possible to display:
- The wording of the role
LABEL - role identifier role
ID - The role code role
CODE - role description role
DESCRIPTION
Users
For users, it is possible to display:
- Login:
LOGIN - First name:
FIRSTNAME - The name:
LASTNAME - First name and last name:
FULLNAME - Description:
DESCRIPTION - The function:
FUNCTION - The email:
EMAIL
Hierarchies and level values
For hierarchies and level values, it is possible to display:
- The wording:
LABEL - The identifier of the structure structure value
ID - The structure code structure structure value
CODE - Description of structure structure value
DESCRIPTION
Key populations available
A population is what an object can contain: for example, a project has hierarchical relationships or roles.
You can call within an array.
To get a list of an object's population, you must first insert a table into the PowerPoint template slide or Word template file.
The content of the table must comply with the following format:
- The first line must be the table header . The text formatting is retained.
- The second line contains the populations and keys to be displayed in the table.
The keys must be in the form $POP{ATT_CODE}where CODE_ATT is theattribute codeattribute the platform and POP the name of the object.
For example: $PROJECT{LABEL} to display the names of the projects.
You can target a subpopulation by combining keys.
For example: $ROLEUSER{FIRSTNAME} to display the first names of users who have a role project.
Populations available for each type of object
Subject/Population | Object/population keys | Available subpopulation | Subpopulation keys |
structure | HIERARCHY | structure value | VALUE or .VALUE |
role | ROLE | User | USER or .USER |
Filters
It is possible to filter what you want to display in a list using a code/value combination.
A filter materializes as follows. It is located [in brackets] and after the population key.
For example: $ROLE[CODE=ROLE1] to display all roles that have a code equal to "ROLE1"
It is also possible to combine multiple filters using a separator: ;.
For example: $ROLE[CODE=ROLE1;DESCRIPTION=CDP] to display all roles that have a code equal to "ROLE1" AND that have the description "CDP."
To target a subpopulation, you can combine filters:
For example: $ROLE[DESCRIPTION=CDP]USER[CODE=CDP]{LABEL} to display tAll role labels with the description "CDP" and users with the code "CDP."
Filter operators
Several filter operators are available:
Equal to | = |
Different | ≠|
Strictly less than | < |
Strictly greater than | > |
Less than or equal to | <= |
Greater than or equal to | >= |
Check for nullity | IS_NULL , IS NULL , IS WORTHLESS , EST_NULL , IS NULL , EST_NULL , =NULL, = NULL , =NULL , = NULL , = NULL , =NULL , =null, = null |
Check for non-nullity | IS_NOT_NULL, IS NOT NULL, IS NOT NULL, NOT_NULL, IS NOT NULL, NOT_NULL, =NOT_NULL, = NOT NULL, =NOT_NULL, = NOT_NULL, = NOT_NULL, =NOT_NULL, ≠null, ≠null |
Check that a list is not empty | IS NOT EMPTY, IS NOT EMPTY, IS_NOT_EMPTY, NOT_EMPTY |
Check that a list is empty | IS EMPTY, IS EMPTY, IS_EMPTY, EST_EMPTY |
Examples
Project attributes
To view different attributes assigned to a project:
- Add a table to your template file.
- Complete the table with the desired data.
Project | ${PROJECT_TITLE} |
Code | ${PROJECT_CODE} |
Icon | ${ICON} |
Long label | ${LONG_PROJECT_TITLE} |
Description | ${PROJECT_DESCRIPTION} |
status | ${status} |
Duration | From ${PROJECT_START_DATE} to ${PROJECT_END_DATE} |
Project creation date | ${PROJECT_CREATION_DATE} |
Update date | ${PROJECT_UPDATE_DATE} |
Resource scheduling date | ${RESOURCE_PLANNING_DATE} |
Date project closed | ${PROJECT_CLOSED_DATE} |
project manager | ${PROJECT MANAGER} |
template | ${template} |
Father project | ${FATHER PROJECT} |
Project weather | ${ATT_WEATHER} |
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 $ROLE{LABEL} | User: $ROLE.USER{FULLNAME} |
( $ROLE{ID}, $ROLE{CODE}) | ( $ROLE.USER{ID}, $ROLE.USER{LOGIN}) |
$ROLE{DESCRIPTION} | $ROLE.USER{FUNCTION}
$ROLE.USER{EMAIL} |
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 |
$HIERARCHY{LABEL} $HIERARCHY{CODE} | $HIERARCHY.VALUE{LABEL}
$HIERARCHY.VALUE{CODE} |
structure Detail | Value |
$HIERARCHY{DESCRIPTION}
$HIERARCHY{ID} | $HIERARCHY.VALUE{DESCRIPTION}
$HIERARCHY.VALUE{ID} |