Plan/Manual/Creating ODT Report Templates: Difference between revisions
(initial) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
{{Construction}} | {{Construction}} | ||
==Description== | ==Description== | ||
ODT report templates are regular odt files that can be designed using any odt word processor like ''Calligra Words'' or ''LibreOffice Writer''. The technique used is to use variables to hold references to the information that shall be fetched from the project. The variables are called ''User Fields'' in ''Writer'' and can be found under <menuchoice>Insert->Field->More Fields->Variables->User Fields</menuchoice>. In ''Words'' they are called ''Custom Variables'' and can be found | ODT report templates are regular odt files that can be designed using any odt word processor like ''Calligra Words'' or ''LibreOffice Writer''. The technique used is to use variables to hold references to the information that shall be fetched from the project. The variables are called ''User Fields'' in ''Writer'' and can be found under <menuchoice>Insert->Field->More Fields->Variables->User Fields</menuchoice>. In ''Words'' they are called ''Custom Variables'' and can be found in <menuchoice>Text Editing docker->Variable->Custom</menuchoice>. | ||
==Variables== | ==Variables== | ||
Revision as of 12:50, 1 February 2018
Under Construction
Description
ODT report templates are regular odt files that can be designed using any odt word processor like Calligra Words or LibreOffice Writer. The technique used is to use variables to hold references to the information that shall be fetched from the project. The variables are called User Fields in Writer and can be found under . In Words they are called Custom Variables and can be found in .
Variables
Translated Labels
Translated lables enables us to produce general report templates that can be used in different languages.
| Variable Name | Variable Value |
| tr.project | Project |
| tr.Manager | Manager |
| tr.Schedule | Schedule |
| tr.BCWS | BCWS |
| tr.BCWP | BCWP |
| tr.BCWP | Project |
| tr.ACWP | ACWP |
| tr.SPI | SPI |
| tr.SPI | SPI |
Project Values
| Variable Name | Variable Value | Description |
| project.name | Name | The name of the project |
| project.manager | Manager | The name of the project manager |
| project.bcwscost | BCWS Cost | Cost based Budgeted Cost of Work Scheduled |
| project.bcwpcost | BCWP Cost | Cost based Budgeted Cost of Work Performed |
| project.acwpcost | ACWP Cost | Cost based Actual Cost of Work Performed |
| project.spicost | SPI Cost | Cost based Schedule Performance Index |
| project.cpicost | CPI Cost | Cost based Cost Performance Index |
| project.bcwseffort | BCWS Effort | Effort based Budgeted Cost of Work Scheduled |
| project.bcwpeffort | BCWP Effort | Effort based Budgeted Cost of Work Performed |
| project.acwpeffort | ACWP Effort | Effort based Actual Cost of Work Performed |
| project.spieffort | SPI Effort | Effort based Schedule Performance Index |
| project.cpieffort | CPI Effort | Effort based Cost Performance Index |
Schedule Values
Projects Table
Task Status Table
Use by placing a variable with name tableX (X=number) with value taskstatus before the table that shall be filled in. Create a table with an optional header. The header can optionally contain variables. Fill the first row of the table with variables refers the values you want to fetch from the tasskstatus table.
Example: A table with header. The header fetches column names from the taskstatus table.
Variable: Name: table1 Value: taskstatus
Variable Name: table1.name Value: Name
|
This is the header so fetches the header of the column |
Variable Name: table1.name Value: Name |
This is the values so fetches the actual column value |
Tasks Table
Chart
Gantt
Not supported.
| Variable | Description |
| Name | The name of the project |