Actions - Flow Control

In this section, you will find all available actions for flow control.


Group

This action can be used to group other actions. This is useful if you want to apply a specific exception behaviour to a certain group of actions (see Exception Handling) or if you want to only execute a group of actions if a condition is fulfilled.

General Attributes

You can set the following general attributes:

NameThe name of the group action; this is only used within Mail & Deploy to identify the group action.
Condition

An optional expression (see Expressions) that evaluates to either True or False. The actions of the group will only be executed if the condition evaluates to True.
Exception Behaviour
Determines what Mail & Deploy shall do if the execution of one of the actions of the group causes an exception (see Exception Handling).

Do Not Handle.

If you select this behaviour, any exception caught by the group action will not be handled and passed on to the parent action container.

Cancel Group.

If you select this behaviour, any exception caught by the group action will lead to the complete group to be cancelled, but no exception will be passed on to the parent action container.

Continue With Next Action.

If you select this behaviour, any exception caught by the group will lead to the group execution to be continued with the next action. No exception will be passed on to the parent action container.

Actions
This is a list of actions (see Actions) which are sub-actions of the group. 

Preparation Actions
This is a list of actions (see Actions) which will be executed before the condition will be evaluated and the sub-actions of the group will be executed.


Cycle

This action can be used to repeat a certain sub-set of actions for each value of a datasource field.

Example: You have designed a report (see Reports) that contains data and charts about a single sales store and you want to create and distribute one report document for each sales store there is in the QlikView Document on which the report is based. In this case you can use a cycle action that cycles over each value of the field "Sales Store" in the QlikView Document, creates a report for that sales store and distributes it. 

General Attributes

You can set the following general attributes:

Datasource Field
The datasource field from which to read values to cycle over.
Field Value Selector

The field value selector that determines which values of the datasource field shall be used for the cycle.

All Values.

If you use this selector, all values of the datasource field will be used for the cycle, regardless of the current filter state of the datasource.

Applicable Values. 

If you use this selector, only those values of the datasource field will be used for the cycle which are compatible to the current filter state of the datasource.

Filtered Values. 

If you use this selector, only those values of the datasource field will be used for the cycle to which the datasource field is explicitly filtered.
Sort Order
This setting determines in which order the values will be processed by the cycle.

None. 
No specific sort order will be used and the values will be used in the exact order in which they have been read from the datasource.

Ascending.
The values of the datasource field will be processed by the cycle in ascending order.

Descending.
The values of the datasource field will be processed by the cycle in descending order.
Value Name
The name of the variable with which the current cycle value can be referenced in expressions (see Expressions) which are used in any of the actions of the cycle
Exception Behaviour
Determines what Mail & Deploy shall do if the execution of one of the actions of the cycle causes an exception ( Exception Handling).

Do Not Handle.

If you select this behaviour, any exception caught by the cycle action will not be handled and passed on to the parent action container.


Cancel Cylce.

If you select this behaviour, any exception caught by the cycle action will lead to the complete cylce to be cancelled, but no exception will be passed on to the parent action container.

Continue With Next Action.

If you select this behaviour, any exception caught by the cycle will lead to the cycle execution to be continued with the next action. No exception will be passed on to the parent action container. 

Continue With Next Value.
If you select this behaviour, any exception caught by the cycle will lead to the cycle to be continued with the next value. 

Actions

This is a list of actions (see Actions) which will be executed for each cycle value.

Preparation Actions

This is a list of actions (see Actions) which will be executed before the cycle values are evaluated and before the actions of the cycle will be executed. These actions can, for instance, be used to filter the datasource field from which the cycle values are derived so the number of cycle values is limited.

M
Mail is the author of this solution article.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.