ProjectTRACKER Help - Reports - Configuration

Note: Only users with “Report” access rights can see and use the reports configuration functionality!

ProjectTRACKER can create reports in the following formats:

A normal user can only call these reports - authorized users can also create reports. The report creation is done via a command script, which is described in the following sections.

For report automatizing individual reports could be called / generated via HTML parameters:

http://.../Report.php?ReportName={Name}&ReportType={Type}&PrintReport=1

Reports a configured via a command script in the format:

| {Command1} | {Para1} | {Para2} | ... | {ParaN} |
| {Command2} | {Para1} | {Para2} | ... | {ParaN} |
     ...

Lines could be also formatted by using continuation lines with '..', e.g.:

  | {Command2} |..
    {Para1} |..
    {Para2} |..
    {Para3} |

Note: All spaces after '..' up to the next command in the next line are deleted. Don't forget to add at least one space character in front of '..' when needed!

Comments /* */ within command parameter cells are also allowed, e.g.

| {Para} /* Comment */ |

Possible commands and parameters are described in detail in the following chapters.

The following placeholders in the command script section will be replaced with the below defined replacement strings or the current settings of the Report Parameters.

In case the CALL function is used, the {Variables} values from the calling script can be also used in the command script section of the called report script via:

##{Variable Name}##

Variable names from calling scripts can be used directly (means without the '##' markers) for the Cmd-Row discrete command data set section. Details on {Variables} and the CALL function see Command parameter syntax.

The usage of Placeholders and ##{Variables}## defined in advance works also in general for the SQL discrete command data set section. Note: In case the variable consists of several rows the last row will be taken.

For details on the SQL / Cmd-Row discrete command data set section see Add a Table, Add a Graphic and Add a Plot.

Shows report debug information in an extra page - this works only when the debug mode of the ProjectTRACKER is activated by the ProjectTRACKER PHP admin!

To generate RSS reports you need to follow a special header and table format:

RSS Channel Description:

RSS Item Description:

An example you can find in the Standard Report Effort Allocation Week Status.

The PHP expression:

$Parameter = $Test > 10 ? 1 : 0

could be implemented with the ProjectTRACKER command script as:

... | Parameter = Test > 10 1 0 | ...

Note: Don't use Parameter as true or false condition, as the value will be set to Test first. This is because of serial parser execution ((A = B) < C)!

In case the value of Parameter shall be checked and set to 0 or 1 itself, this can be shortened to:

... | Parameter > 10 1 0 | ...

The PHP expression:

if (DATE('Y', $_DATE) < ##DYEAR##)
  $Week = 0;
elseif (DATE('Y', $_DATE) > ##DYEAR##)
  $Week = 53;
else
  $Week = DATE('W', $_DATE);

with

• _DATE : Current date
• Week : Current week number

could be implemented with the ProjectTRACKER command script as:

... | _Y=_DATE DATE('Y') |..
      _Week=_DATE DATE('W') |..
      _Week2= _Y < ##DYEAR## 0 _Week |..
      Week= _Y > ##DYEAR## 53 _Week2 | ...

Note: _Week2 is needed as otherwise the parser would destroy _Week with the _Y value. This is because of serial parser execution ((A = B) < C)!

|E|Check=##DPROG##|<strong>Program not set!</strong> |
|H|##DPROGN## Program Task Status |
|T|H|SELECT Task.TaskGroup AS ID, Task.TaskName AS Task, Task.TaskEffortPlanned AS Plan, ..
  Task.TaskID AS _TID FROM Program INNER JOIN Task ON Program.ProgramID = Task.ProgramID ..
  WHERE Program.ProgramID=##DPROG## AND Task.TaskGroup LIKE 'E%' AND Task.TaskActive=True AND ..
  Program.ProgramActive=True AND Task.TaskSumFlag=False ORDER BY Task.TaskGroup |..
    Plan RIGHT FORMAT('%.1f') SUM |..
    Done = WDAYS('',_TID,'','','') RIGHT FORMAT('%.1f') SUM |..
    Rem = RDAYS('',_TID,'','','') RIGHT FORMAT('%.1f') SUM |..
    _Total = Done + Rem |..
    Rem% = Rem / _Total * 100 RIGHT ALARM(50,30) FORMAT('%.0f%%') AVE |..
    Plan% = _Total / Plan * 100 RIGHT ALARM(100,0) FORMAT('%.0f%%') AVE |

Delivers depending on the default program setting e.g. the following report:

TEST Program Task Status

|E|Check=##DPROG##|<strong>Program not set!</strong>|
|E|Check=##DYEAR##|<strong>Year not set!</strong>|
|N|[[portal:program-report]]|
|L|~~NOCACHE~~|2|Switch off DocuWiki cache!|
|H|Program Effort Curve ##DPROGN## ##DYEAR##|
|G|Z=0,COL=3,G,XL=Week,YL=PD/cht=lxy/chs=600x300/chco=ff0000,00ff00,ff8000/chdl=Done;Plan;Estimated+Total/chtt=Program+Effort+Curve |..
    SELECT TaskEffort.TaskEffortDate AS _DATE, Sum(TaskEffortCurrent/LocationWorkTime) AS _EFFORT ..
    FROM (Program INNER JOIN Task ON Program.ProgramID = Task.ProgramID) INNER JOIN (Location ..
    INNER JOIN (Engineer INNER JOIN TaskEffort ON Engineer.EngineerID = TaskEffort.EngineerID) ON ..
    Location.LocationID = Engineer.LocationID) ON Task.TaskID = TaskEffort.TaskID ..
    WHERE Task.TaskActive=True AND Program.ProgramActive=True AND Task.TaskGroup LIKE 'E%' AND ..
    Program.ProgramID=##DPROG## GROUP BY TaskEffort.TaskEffortDate ..
    ORDER BY TaskEffort.TaskEffortDate |..
      _Y=_DATE DATE('Y') |..
      _Y < ##DYEAR## SKIP _Y |..
      _Y > ##DYEAR## SKIP _Y |..
      Week=_DATE DATE('W') |..
      Done=_EFFORT CUM ROUND 1 |..
      Plan=PDAYS('',##DPROG##,'E%',_DATE) ROUND 1 |..
      _REM=RDAYS('','',##DPROG##,'E%',_DATE) |..
      Total=_REM+Done ROUND 1 |

Delivers depending on the default program and year setting the following report:

Program Effort Curve Example Project 2009