Difference between revisions of "Commissioning Objects (UBIK Android)"
| Line 5: | Line 5: | ||
There are two types of commissioning tasks, on one hand state relevant task which are indicated by either the cross or check icon at the beginning of the row as well as the "Not Applicable" label and Checkbox at the end of 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" checkbox. | There are two types of commissioning tasks, on one hand state relevant task which are indicated by either the cross or check icon at the beginning of the row as well as the "Not Applicable" label and Checkbox at the end of 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" checkbox. | ||
| − | All commissioning tasks no matter of what type are intended to be nested into a parent object called | + | All commissioning tasks no matter of what type are intended to be nested into a parent object called commissioning workpackage, which provides the functionality to close all underlying tasks and synchronize them with the server, may triggering some further functionality there. |
| − | + | ||
| + | {{Attention|A commissioning task is finished only if a value is entered as property, or the "Not applicable" checkbox is ticked accordingly. A value is entered if the property is not null, which means that even a boolean property false is valid!}} | ||
== Information commissioning task == | == Information commissioning task == | ||
| − | + | Like mentioned before, this task is indicated by the white circle in front of the rest of the row. It is originally intentioned 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 commissioning. 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 == | == State relevant commissioning task == | ||
| − | == Commissioning | + | All tasks like checking if a functional plan is available, certain protocolls are in place and updated or entering some specific values is handled with these tasks. It is also possible to check a task as "Not Applicable" if a task is not possible to be done at the moment but should be seen as finished. |
| + | |||
| + | The icon leading the row is indicating the completion status of the task. A task is finished once the value is not null OR the "Not Applicable" checkbox is ticked. This means even a boolean property FALSE means a task is finished. | ||
| + | |||
| + | == Commissioning Workpackage == | ||
| + | |||
| + | A workpackage contains | ||
[[Category:Android|Commissioning]] | [[Category:Android|Commissioning]] | ||
Revision as of 10:27, 3 June 2015
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.
There are two types of commissioning tasks, on one hand state relevant task which are indicated by either the cross or check icon at the beginning of the row as well as the "Not Applicable" label and Checkbox at the end of 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" checkbox.
All commissioning tasks no matter of what type are intended to be nested into a parent object called commissioning workpackage, which provides the functionality to close all underlying tasks and synchronize them with the server, may triggering some further functionality there.
 | A commissioning task is finished only if a value is entered as property, or the "Not applicable" checkbox is ticked accordingly. A value is entered if the property is not null, which means that even a boolean property false is valid! |
Information commissioning task
Like mentioned before, this task is indicated by the white circle in front of the rest of the row. It is originally intentioned 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 commissioning. 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 like checking if a functional plan is available, certain protocolls are in place and updated or entering some specific values is handled with these tasks. It is also possible to check a task as "Not Applicable" if a task is not possible to be done at the moment but should be seen as finished.
The icon leading the row is indicating the completion status of the task. A task is finished once the value is not null OR the "Not Applicable" checkbox is ticked. This means even a boolean property FALSE means a task is finished.
Commissioning Workpackage
A workpackage contains
