Conditional visibility of the task / Conditional task

Principle of operation of a conditional task

Conditional visibility introduces an additional condition to the task, which must be fulfilled in order for the task to be visible to the user(s). This condition is to answer 'Yes' or 'No' (using the Yes/No command) in another task. The remaining visibility and conditions of the task remains unchanged according to the standard/basic application logic.

Example 1- Single user task in one location

When there is Task A and Task B, where Task B is to be executed (and most importantly, it is conditionally visible) when Task A is executed with a specific answer e.g. 'Yes'. In order to configure such a task you need to perform the following steps:

Create task A - The task must be active, have location X, have user X added. It must have the Take/No command in the process (because only this command can conditionally call another task)
Create task B - The task must be active, have location X, have user X added. (So task A and B are configured just like any other standard/basic task in the app, so that they are visible and possible to complete).
Enter an additional condition for Task B (active function conditional visibility of the task). This means that Task B will not be visible if this additional condition is not met.
In Task A, enter the ID of Task B into the answer 'Yes'. In this way, a relationship in built between Task A and Task B.

Created in this way, the task will have the following effect for User X after logging into the mobile app:

User X will only see Task A
User X, when they execute the task (answers the command containing the condition and completes the task with any status) will see Task B and will be able to execute it at any time within the next 24 hours. The fulfilment of the condition is valid 24h from the moment Task A was completed (fulfilling the condition does not affect the task counters). This is caused by the parameter (in the application settings): TaskPrerequisitesValidDuration. The default value is empty (meaning 24h) but the configuration of this parameter is based on entering a natural number different from 0, the entered number will mean the number of days (periods after 24h, value 3 = 3x24h) for which the condition will be maintained (can be fulfilled). This parameter effects all the conditional tasks in a given instance.

This example shows the general principle of the conditional task (i.e. one additional condition to make the task visible) in case the task is performed only once. In the following examples the same scenario is shown, but in other more complex cases.

Example 2 - Conditional task with multiple users and multiple locations

When there is Task A and Task B, where Task B is to be executed (and most importantly, it is conditionally visible) when Task A is executed with a specific answer e.g. 'Yes'. In Task A there are three (X,Y,Z) locations and three (X,Y,Z) users, in Task B we have two (X,Y) locations and two (X,Y) users. The task is performed once. The description of application behaviour for this scenario will be as follows:

User X will perform Task A in location X
Task B becomes visible (because the condition from task A is met) in locations X and Y for users X and Y.

A conditional task is only an additional single condition, therefore it does not affect the standard/base logic of the app. Accordingly, the conditional task is visible for both users and both locations because without the existence of the conditional task it would also be visible according to the standard/basic logic of the app.

The exception for this situation is the use of an additional parameter (in the application settings): FilterTaskPrerequisitesLocation as a global setting for all conditional tasks in a given application instance. When this parameter is active (as in the example above) the behaviour will be as follows:

User X will perform Task A in location X
Task B becomes visible (because the condition from Task A has been fulfilled) in locations X for users X and Y.

The enabled flag narrows down the condition by narrowing the visibility of the location only to the location where (the conditional) Task A was performed. If you require the task to also be visible in location Y, you would have to perform Task A again, this time in location Y.

Please Note: There is no analogous narrowing of the location for users. The users in Task B can always see all those authorised according to standard/basic app rules.

Example 3 - Conditional task and cycles

When there is Task A and Task B, where Task B is to be executed (and most importantly, it is conditionally visible) when Task A is executed with a specific answer e.g. 'Yes'. Tasks A and B occur in cycles, e.g. weekly, they are visible daily from Monday to Friday from 8am for 120 minutes and from 2pm for 60 minutes. This type of scenario will act as a standard/basic task with a cycle with the above described examples of how a conditional task works. This means that Task B will be visible only for the period of the indicated cycle in the locations and for the users added in this task and the condition from Task A must be fulfilled. If Task A is executed at 8:01am then Task B will appear within its cycle to be executed and a valid condition (one-time) for 24h. The following scenarios are possible:

Task A is executed at 8:01am, Task B becomes visible. Task B was executed at 8:10am. Task A was then executed again at 2:01pm, Task B is visible once again and can be executed within its cycle.
Task A is executed at 8:01am, Task B becomes visible. Task B was not executed. Task A was then again executed at 2:01pm, Task B is visible and can be executed once again. As Task A has been executed twice, two positive conditions have been met so that Task B can show up, which does not mean that Task B can be executed twice, Task B can be executed as many times as the configuration of this task in its cycle counters allows, the number of positive additional conditions met does not increase the counter of task executions (because the app checks the standard/basic logic of operation).

Details of configuration

Calling Task (Task A from the section describing the rules of conditional tasks)

In the Advanced Settings of Task A you can see the parameter as in the view below. Activating it signals the generation of the calling task, after going to edit of the 'Yes/No' command, which is to call the condition of the appearance of Task B, there is a field to fill in the ID of Task B (conditionally appearing). You can indicate the same task for both answers, two different ones, or leave one of the answers unrelated to the conditional task. It is not possible to call two conditional tasks for one 'Yes' or 'No' answer.

Save the changes. Now, when somebody chooses 'No' and completes Task A, the task with this ID with the set conditional visibility will appear in the Task List.

Conditional tasks (i.e. conditionally run, Task B from the section describing the rules of conditional tasks)

In the Advanced Settings of Task B you can see the parameter as in the view below. Activating it means the task will expect to meet an additional condition from another task with which it has a relationship built. If the condition is not met (or the relationship is not established) the task will not be visible.