3.12 Runtime Commands

Tasks created in CBA ItemBuilder project files (see section 3.6) are to be used with an execution environment, i.e., using a particular deployment software (see chapter 7). In most cases, deployments are a set of CBA ItemBuilder tasks, administered in a linear sequences. An authentication (i.e., login) of the test-takers is often required first before the items are shown in the defined sequence. Regardless of the administration mode, items are rendered in the test-takers web browser or in a browser-component provided as part of the deployment software.⁵¹

Since the CBA ItemBuilder allows creating complex items with multiple pages, it is essential to distinguish the navigation within Tasks (implemented inside the CBA ItemBuilder) and the navigation between Tasks, which is handled by the deployment software. Both parts are linked with so-called Runtime Commands (short: Command), which the item author can define within CBA ItemBuilder tasks to allow test-takers to end working on a particular task.

Runtime Commands are used to send instructions to the deployment software. In order for a test participant to finish processing a CBA ItemBuilder task, at least one NEXT_TASK command is required in each task (see subsection 3.12.1).

The different Runtime Commands can be assigned to Buttons (see 3.11.2) and to MenuItems (see 3.9.7) using the context menu in the Page Editor (see Figure 3.138).

FIGURE 3.138: Context menu to assign a Runtime Command.

The dialog that opens (Set Runtime Command, see Figure 3.139) allows you to select one of the available Runtime Commands. Exactly one command (or EMPTY for none) can then be assigned to the currently selected Button or MenuItem (default is EMPTY).

FIGURE 3.139: Dialog Set Runtime Command.

After specifying which command should be triggered by click or touch on the selected Buttons or MenuItems by selecting an entry in the dialog Set Runtime Command the button OK is used to conform the configuration. If a command is already assigned, it can be removed by selecting the command EMPTY or by deselecting the selected entry in the Set Runtime Command dialog.

Runtime Commands can also be defined directly in the Properties view (see property Command in Figure 3.140). The entry EMPTY can be selected to remove a defined Runtime Command.

FIGURE 3.140: Property Command in section Component Interaction.

Runtime Commands can also be triggered from the dynamic content of items (see subsection 4.4.6 for specific finite-state machine operators that trigger commands).

Some commands refer to the higher-level navigation between tasks and need to be tested not only in the Preview (see section 1.4) but also in the deploymet software (see chapter 7).

3.12.1 Task-related Commands

A Task presented at runtime is always expected to be ended when one of the task-related commands is executed. Task-related Runtime Commands provide the possibility to end an assessment component form within the item.

NEXT_TASK: Ending a task and navigation to the next task is requested with the NEXT_TASK-command, that can be assigned, for instance, to a component of type Button.

A NEXT_TASK-command (either linked to a Button as described above in section 3.12 or triggered in th Finite-State Machine (see section 4.4.6) is required for each Task if the test-taker should be able to end the Task. Typically only tasks ended by a planned timeout implemented in the deployment software or tasks ended by an external event triggered by an interviewer or test-administrator have no NEXT_TASK-command.

If no next Task is defined within a CBA ItemBuilder Project Preview or a Task Preview was requested, the NEXT_TASK-command will trigger the message illustrated in Figure 3.141.

FIGURE 3.141: Preview message when calling the NEXT_TASK-command in the last Task.

BACK_TASK / CANCEL_TASK: For controlling the flow between tasks in more depth, deployment software (see chapter 7) and the TaskPlayer-API (see section 7.7) can additionally support the following commands:

• BACK_TASK: Navigates to the previous task
• CANCEL_TASK: Cancels the current part of an assessment

FIGURE 3.142: Item illustrating Task-related Commands (html|ib).

3.12.2 Dialog-related Commands

Pages can be used to design Dialog pages and Popups windows (see section 3.15) by configuring properties of the Frame (see Figure 3.156 for examples).

CLOSE / CLOSE_AND_NEXT_TASK: A specific CLOSE-command can also be used to close a currently open dialog page. The runtime command can be used to close a dialog page. Regular dialog pages can also be closed using the small “X” in the header if the attribute Closable=true is used. If Closable=false is configured, then the small “X” is not displayed in the header. Finally, the runtime command CLOSE_AND_NEXT_TASK combines CLOSE and NEXT_TAKS.

3.12.3 Fullscreen-related Commands

The presentation of assessment content created with the CBA ItemBuilder is done by deployment software (see chapter 7). It can be done in standard web browsers or with a specific web browser component (embedded into a deployment software and providing additional test security, for example, a kiosk mode; see section 7.2.3 for more details). The CBA ItemBuilder provides simple Runtime Commands to switch the display to full-screen mode intended for use directly in standard web browsers.

TRIGGER_FULLSCREEN/CANCEL_FULLSCREEN: The item shown in Figure 3.143 illustrates the use of the commands TRIGGER_FULLSCREEN and CANCEL_FULLSCREEN. If the execution environment supports it, the command TRIGGER_FULLSCREEN can be used to switch to full screen mode. Similarly, the full screen mode can be exited with the command CANCEL_FULLSCREEN. Depending on the integration of the item (see chapter 7) in a deployment system or task execution environment, these functions are identical to the full screen mode of the browser, or result in only the iframe containing the actual item being displayed in full screen.

FIGURE 3.143: Item illustrating fullscreen-related Commands (html|ib).

Whether the fullscreen-related commands can be used within the CBA ItemBuilder projects or whether the control over the fullscreen mode must be implemented by the execution environment depends on the deployment strategy and the deployment software used (see section 7.2.3 for more details).

3.12.4 Clipboard-related Commands

The commands COPY, CUT and PASTE allow to create buttons that can be used at runtime (i.e., for test-taker) to access the clipboard while answering tasks that use components of type InputField. The example item shown in Figure 3.144 illustrates this functionality.

FIGURE 3.144: Item illustrating clipboard-related Commands (html|ib).

---

51. A browser-component is an HTML browser control embedded in other software such as an Electron application.↩︎