Cascading Actions: Actions that trigger other Actions

[Joseph_Musekura]

In QlikView, actions that trigger other actions i.e. cascading actions, have unexpected behaviour, especially in AJAX and Webview mode. 

In QlikView Help, it is underlined that "Actions that trigger other actions, called cascading actions, may cause unforeseen consequences and are not supported!"

Environment:

QlikView 

Example:

In the attached example, if you navigate through the sheets using “tabrow”,  you will have the same result both in desktop, IE Plugin, AJAX and Webview. 

When you navigate using tabrow, it displays same number of the sheets in each objects.

But if you navigate through the sheets using buttons, the result is wrong in AJAX and Webview.

Resolution:

From QlikView 12.00 SR4 and 11.20 SR15 we introduced a new parameter called "MaxActionLevel" that allows to define a number of cascading triggers that QlikView supports. 

IMPORTANT:

Cascading triggers are not supported. The application logic must be tested and validated for functionality by the application developer/designer.
Unexpected application behavior or results is only supported with Cascading triggers are disabled.

Enable Cascading Triggers

1. Edit settings.ini. Default location C:\ProgramData\QlikTech\QlikViewServer 
2. Add the following setting under the [Settings 7] part of the settings file, where N is the desired number of cascading levels.
   MaxActionLevel=N
3. Save the settings.ini file
4. Restart QlikView Server Service to apply the new setting

Disable Cascading Triggers

1. Edit settings.ini. Default location C:\ProgramData\QlikTech\QlikViewServer 
2. Remove the following setting under the [Settings 7] part of the settings file.
   MaxActionLevel=N
3. Save the settings.ini file
4. Restart QlikView Server Service to apply the new setting

NOTE:
MaxActionLevel is a not a permanent and supported feature and can be removed from the product at upgrade without further notice. 

Test application functionality when making use of MaxActionLevel.

As an example:  There have been instances where default existing Listbox filter values and selected filter values are cleared when a MaxActionLevel entry is included in the settings.ini.