A [[MROCLS_PICK_LIST_TASK|Pick List task]] looks and behaves the same like a standard Integer Task with SelectiveList. Other than the standard Integer Task, the Pick List Task has an [[UBIK_Active_Lists|Active List]] defined on instance level to pick from for its value property. The task counts as finished as soon as a list item has been selected, or when pressing ''Not Applicable''.
{{UnderConstructionStart}}
==== Procedure Tasks {{Version/MobileSince|5.1}}{{Version/WinXSince|5.1}} ====
Procedure tasks are [[#Sequential_Task|sequential tasks]] that can define a more complex workflow with task branching. There are three specific types of procedure tasks: [[MRO_(Plugin)#Switch_Start_Task|switch (start) tasks]], [[MRO_(Plugin)#Switch_End_Task|switch end tasks]] and [[MRO_(Plugin)#Calculation_Task|calculation tasks]].
As a simple example, you can configure several predecessor tasks to measure the temperatures of different parts of an equipment and then a follow-up calculation task to compute the average of them. Then a follow-up of that can be a switch task which determines the follow-up task branch. If the average temperature is above 30°C, the follow-up task is to turn on the cooling mechanism. The other branch can be directly the end of the switch, but it can also include further switches depending on the actual required workflows. The technical details of these tasks can be found in the links above.
For both switch (start) and calculation tasks, a symbol is displayed in the UI to reflect its following evaluation status.
* Pending: The task is waiting to be automatically executed/evaluated;
* Finished: The task is automatically executed/evaluated successfully;
* Error: The task was automatically executed/evaluated but resulted in an error.
When a predecessor switch task is not yet finished, its follow-up procedure tasks are hidden because it's simply unknown which ones are relevant for the users. Once it's finished, the branch to follow appears while the other branch remains hidden. Additionally, all procedure tasks in that other branch get set to NA (not applicable).
{{Hint|Procedure tasks are meant to execute automatically without user inputs as soon as their predecessor(s) is/are finished. However, the finishing of such a predecessor task must be triggered by the users. If such a predecessor task becomes finished due to e.g. a server update, the follow-up procedure related workflow does not trigger. This is an intentional design to avoid having the workflow triggered in the name of the users even when they are not responsible for or even aware of it. }}
{{UnderConstructionEnd}}
{{DeprecatedStartTag|parameter=Please refer to [[Main_Page]] for the most recent information.}}
[[Category:Android|MRO Objects (UBIK WinX)]]
[[Category:Client|MRO Objects (Client)]]
[[Category:Mobile|MRO Objects (Client)]]
[[Category:Pages with broken file links|MRO Objects (Client)]]
[[Category:WinX|MRO Objects (UBIK WinX)]]
=== MRO objects with project information (WinX only) {{Version/WinXSince|2.5.4}} ===
[[File:UI_WinX_MRO_ProjectInfo.png|thumb|MRO Object with Project Info (WinX)]]