This article reviews why to use parameters and when to use them vs not use them.
Parameters allow the person to link sections of a program to prebuilt rules and content. This allows them to build programs more efficiently and edit sections that are repeated across targets and phases and push all those changes to all targets and phases that are linked to that parameter.
You can create a parameter for each section that has this link icon next to it. -png.png?width=461&height=108&name=mceclip0%20(25)-png.png)
Local Parameters are parameters saved and linked within a program and only exist in that program or a copy of that program. Editing Local Parameters only affects the targets and phases in the program you are editing. Local Parameters are highlighted in green.
Global Parameters are parameters that are available and linked across programs. Global Parameters allow admins to create frequently used program rules and content and put them in a drop-down menu for efficient program building. Editing a global parameter affects all programs that are linked to that Global Parameter. This allows admin to push program rules and changes across the entire library and learner's programs when needed. Global Parameters are highlighted in orange. -png-1.png?width=826&height=500&name=mceclip1%20(16)-png-1.png)
Global Parameters will be created less than local parameters since Global Parameters will most likely be created as part of your initial set up and refined within the first few months of using Motivity. To learn more about using Global Parameters, read this article.
Only use parameters when you have content that is or could be used across multiple targets and phases. This will allow you to edit the content in one place and push those changes to all other targets and phases.
**Tips: Here are the parameters most often linked to Global parameters
1. Session Types: Creating consistent session types is important to avoid multiple start session buttons in data collection mode and helps prevent splitting programs and targets into different events.
2. Key Instructions: Create instructions to those running programs (e.g., consistently used SDs across a program).
3. Measures and Instructions: Create a data collection interface that is frequently used (e.g. Frequency, Percent correct, DTT, Task Analysis, Total Duration), and then you can choose from the drop-down of global parameters instead of constructing them from scratch.
4. Instrument: This is most often used for Custom Prompts. Create a parameter for Custom Prompt instruments such as prompt hierarchies or custom buttons.
5. Session Outcome: Creating a drop-down list of common session outcome criteria will save you time when creating programs. These are usually more standard rules and content (e.g. Initial trial + 90% of 5 trials)
6. Transitions: Creating a drop-down list of common transitions will also save you time when creating programs (e.g. 3 consecutive sessions, Baseline Transition Criteria, etc.).
Last Reviewed: 9/8/22