Changes
All commissioning tasks, no matter of what type, are intended to be nested into a parent object called [[SYSCLS_COMMISSIONINGWORKPACKAGE|commissioning workpackage]], which provides the functionality to close all underlying tasks and synchronize them with the server (triggering some optional workflow).
{{Hint|A commissioning task is finished only if a value is entered or the "''Not applicable" '' icon is toggled accordingly.<br/>
Any value not equal to null is a valid property value, which means that also a value '''false''' for a boolean property is valid.<br/>
The boolean status is reflected through the checkbox' color: dark blue if it has not been set yet, white if set and white / empty if it is false.}}
== Task types ==
=== Information commissioning task ===
This task is indicated by the white "i" in front of the row. It is intended to hold further information for the user, like additional photos or just a note for the engineer which is not relevant for the status of the whole commissioning process. Nevertheless, it is possible to give it a value like the other tasks which is of course synchronized with the server at least if the commissioning workpackage gets finished.
=== State relevant commissioning task ===
All tasks, for example checking whether a functional plan is available or specific values have to be entered, are handled with this type. It is also possible to check a task as '''Not Applicable''' if it is not possible to be done at the moment but should be seen as finished regarding the work package. The leading icon indicates the completion status of the task. A task is finished once the value is not null '''OR''' the '''Not Applicable''' icon is toggled. It is possible both, to fill out a task's property and toggle it as "Not Applicable".
== Commissioning work package ==
[[File:UI_commissioning_big_picture.png|220px|thumb|border|alt= Architecture of status calculation|Architecture of status calculation]]
A workpackage work package contains tasks of the above mentioned two types. The UI is showing an extra line on bottom of the content browser once Once navigated into to a workpackage which shows work package an icon and a button with an integrated iconare shown at the bottom of the screen. The standalone This button visualizes the calculated sum overall status evaluated of all status of the underlying state relevant commissioning tasks which . This means that , as long as at least a single child object task is not finished and therefore shows an empty circle, the whole workpackage is regarded as (technically) not finished. The icon within the button visualizes the workpackage work package's status which is again a property assigned to the workpackagework package. Resulting out of this, a workpackage has This leads to four possible statesof a work package:
* Workpackage status OPEN | technical status OPEN
