In the following chapters, you can read about what data is stored on the action respondents, how the action respondents are affected by raw data exports, data activations, data cleaning, etc.
Actions connected to Optional filters/Hierarchical filters
As described in the previous chapter the Optional and Hierarchical filters selected by the user can be saved on the action in order to connect the action to a specific unit, filter, etc. Below you see what data will be saved when the action is connected to the hierarchy, what happens if the Optional filter is a Computed variable or contains Grouped answers.
When the hierarchical filter nodes selection is saved on the action the action is connected to the selected node and all the nodes further up in the structure (parent, parent-parent, etc.).
For example; the hierarchy structure looks like below. If now “Team X” is selected and the action created the action will belong to Team X, Sweden, and Total.
Data will also be saved on the variables building the hierarchical structure for more flexible reporting. In the example above the hierarchy was derived from the Country and Team variables so when the action is saved on Team X in the hierarchy it will also be saved to Sweden in the Country variable and Team X in the Team variable.
Note: If multi-select is supported in the hierarchical filter in the StoryTeller the action will be connected to all the selected units. If this should not be allowed, make sure a single selection is used in the hierarchical filter in the StoryTeller report.
Optional filter variable with Grouped answers
If an Optional filter variable to be saved on the action contains grouped answers the action is saved on the selected item only, a created action will not be connected to an item not selected by the user. See the example below.
Example: Country is used as an Optional filter and contains the following answer options:
- Denmark - regular answer
- Germany - regular answer
- Norway - regular answer
- Sweden - regular answer
- Nordic - a Grouped answer based on Denmark, Sweden, and Norway
If the user selects Sweden and creates an action it will be connected to Sweden only and not to the grouped answer Nordic.
If the user selects Nordic and creates an action it will be connected to Nordic only, the action will not be connected to the induvial items building the grouped answer (Denmark, Norway, and Sweden).
Optional filter variable based on Computed variables
If the Optional filter variable to be saved on the action is a computed variable the action is saved on the selected item, see example below.
Example: Country is a computed variable with two answer options and used as an Optional filter,
- Sweden - based on a City variable =Stockholm and Norrköping.
- Germany - based on a City variable = Berlin and Hamburg
If the user selects Sweden and creates a new action the action will be saved on Sweden in the computed variable only, the action is not connected to Stockholm and Norrköping in the City variable.
Action respondents not effected by computed variables
Action respondents are never processed when computing new variables, indexes or merged variables, or grouped answers.
For example a variable storing country is used as an optional filter and the selection is saved on the action. If you now create a new computed variable based on the Country variable the action respondents will not be processed, only the survey respondents will be processed and get data in the newly created computed variable.
Note: like in the respondent level action planning process action respondent are processed when Input variables are based on other Input variables.
For example: in the action Form you have a Status Input variable with the options “New”, “In progress”, and “Completed”. If you now create a new Input variable based on the Status Input variable the action respondents will be processed and get data in the new Input variable.
Action data stored on non-input variables, which happens when hierarchical and Optional filters have been saved on the action, is affected by recoding and cleaning.
Example: a Team variable is used as Optional filters and contains the answer options Team A, Team B, and Team C. If Team B is recoded to Team A this change will affect both the survey respondents and the action-respondents meaning that all actions connected to Team B now are connected to Team A.