Changes

A commissioning task is a special task, which is able to display the property which defines the status of the check directly on row level{{Attention|Since Version 3. 0.0 {{Version/AndroidSince|3.0.0}} Commissioning Objects are handled as [[MRO_Objects_(Client)]]}}

There are two types of A [[SYSCLS_COMMISSIONINGCHECK|commissioning taskstask]] is a special task object, on one hand state relevant task which are indicated by either displays properties defining the cross or check icon at the beginning status of the row as well as the "Not Applicable" label and Checkbox at the end of check on the row. On the other hand, there are not state relevant tasks, which can be seen as some kind of information object which do not have a status. The information object is indicated by the white circle as icon where state relevant tasks display the current status. Further it no not have the "Not Applicable" checkboxlevel directly.

All commissioning tasks no matter of what type There are intended to be nested into a parent object called two types of commissioning workpackagetasks, * '''state relevant''' tasks which provides are indicated by a (solid/hollow) check symbol at the functionality to close all underlying tasks and synchronize them left side of the row as well as the "Not Applicable" icon. The later icon is a circle with a diagonal line in it at the serverend of the row.* '''non state relevant''' tasks, may triggering which can be seen as some further functionality therekind of informational object which do not have a status. This line is indicated by a white "i" as icon and does not have the "Not Applicable" icon.

{{Attention|A All commissioning task is finished only if tasks, no matter of what type, are intended to be nested into a value is entered as propertyparent object called [[SYSCLS_COMMISSIONINGWORKPACKAGE|commissioning workpackage]], or which provides the "Not applicable" checkbox is ticked accordingly. A value is entered if functionality to close all underlying tasks and synchronize them with the property is not null, which means that even a boolean property false is valid!}}server (triggering some optional workflow).

== Information {{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.}}

Like mentioned before, this == Task types ===== Information commissioning task ===This task is indicated by the white circle "i" in front of the rest of the row. It is originally intentioned intended to hold further information for the user, like a manual additional photos or just as a note for the engineer which is not relevant for the status of the whole commissioningprocess. 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.

All tasks like checking if a functional plan The leading icon indicates the completion status of the task. A task is available, certain protocolls are in place and updated or entering some specific values finished once the value is not null '''OR''' the ''Not Applicable'' icon is handled with these taskstoggled. It is also possible both, to check fill out a task 's property and toggle it as "''Not Applicable" if a task is not possible to be done at the moment but should be seen as finished''.

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 two icons work package an icon and a button. Both icons indicate a differnt kind are shown at the bottom of status, the left screen. This button visualizes the workpackage overall status which is a property assigned to the workpackage. The other icon is calculated as sum 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 a red cross, the whole workpackage is regarded as (technically) not finished. Resulting of this, The icon within the button visualizes the work package's status which is again a workpackage has property assigned to the work package. This leads to four possible statesof a work package:

* # Workpackage status OPEN | technically technical status OPEN* # Workpackage status FINISHED | technically technical status OPEN* # Workpackage status OPEN | technically technical status FINISHED* # Workpackage status FINISHED | technically technical status FINISHED

Clicking the button attemps at the bottom attempts to switch the workpackage status and if . If the workpackage is changed from '''open ''' to '''finished''', it triggers a sync of the whole workpackagework package. As some kind of convinience, popup editors for For all state relevant and not filled out (technically open) child tasks which have not be set an editor will pop up and give allowing the user the possibility to fill out enter the missing value but can be canceled of course. Cancelling the dialog leaves the task's value empty.

{{Hint|If a commissioning work package does not contain any commissioning checks or if they are not yet fetched from the server, the technical status displayed at the bottom left corner is '''Finished'''!}} The following images should give an overview about possible states occuring upon using this feature: <gallery widths="170200" heights="310">File:UI_new_commissioning_task.png|New commissioning workpackage(status 1)File:UI_commissioning_task_not_done_properly.png|Open commissioning workpackage with open child tasks(status 1)File:UI_commissioning_task_done_properlyUI_commissioning_during_finishing_with_applicable.png|Open commissioning workpackage with Convenience method for not technically finished tasksupon closing workpackage. Tasks can be marked as not applicable during finishing workpackages; The delete button is removed. {{Version/AndroidSince|2.5.2}}File:UI_commissioning_task_finished_not_properly.png|Finished commissioning workpackage with open child tasks(status 2)File:UI_commissioning_during_finishingUI_commissioning_task_done_properly.png|Convinience method for not Open commissioning workpackage with technically finished tasks upon closing workpackage(status 3)File:UI_commissioning_task_finished_properly.png|Finished commissioning workpackage with technically finished tasks(status 4)

  == Technical Background == The status of work packages is essentially an Integer property. Currently its value definitions are as follows.* Anything not greater than (≤) 0 indicates the package is open;* Anything not less than (≥) 1 indicates the package is finished. == See also ==* [[SYSCLS_COMMISSIONINGCHECK]] (Classification)* [[SYSCLS_COMMISSIONINGOPTIONALCHECK]] (Classification)* [[SYSCLS_COMMISSIONINGWORKPACKAGE]] (Classification) [[Category:Android|CommissioningObjects (UBIK Android)]]