--- title: "Decisions" slug: "decisions" updated: 2024-07-30T15:51:29Z published: 2024-07-30T15:51:29Z canonical: "support.beast-code.com/decisions" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.beast-code.com/llms.txt > Use this file to discover all available pages before exploring further. # Decisions Use Decision course cards in Beast Core 4 Courseware Editor to set conditions and change flag values when the learner selects an associated option. Decision card features (and their associated course cards) allow you to add interest, variety, learner interactions, and performance-based assessments to your lessons. ## How Flags Work 1. Create and name Flag**s** in the **Overview** tab » **Flags** section - Use **Flag** names you will easily recognize (in dropdown menus) 2. When setting **Flag** conditions on a **Decision** (or other applicable) course card: - Assign the value **1** to mean a **Flag’s** condition is **not complete** - Assign the value **2** to mean a **Flag’s** condition is **complete** 3. The learner must complete a required action to perform a **Flag’s** operation ## Decision Card Function When you add a **Decision** card to a lesson: - The learner selects from provided options - **Flags** are set according to the selected option - The lesson proceeds The **Decision** card functions differently based on which option you select in the card’s dropdown menu ![](https://cdn.document360.io/820c65d9-cf4e-4289-9237-5bc834b3bd3e/Images/Documentation/image(833).png) - In the default **Text** option - The learner selects a provided word or statement to perform the **Flag** operation - In the **Avatar**, **Interface**, 3D Viewer, and **Simulation** options - The learner selects a specific Component to perform the **Flag** operation ## Use Cases **Decision** cards (and their associated course cards) provide a lot of flexibility for: - Allowing learners to take control of their learning - Assessing practical knowledge You can use **Decision** cards for things like: - Requiring a learner to repeat multiple maintenance procedures for the same component - Allowing a learner to choose the order in which certain topics are presented in a lesson - Assessing a learner’s ability to find an assigned component or perform a desired action **Examples**: - Ask the learner to choose between two switches on an **Interface** - Ask the learner to select a correct pump in 3D Viewer - Ask the learner to select one of four different screws in a **Simulation** ## Decision Card Editing For proper functioning: - Populate a **Decision** course card based on your **Decision Type** selection - Add all necessary **Flags** and conditions - Use **Decision** cards in conjunction with their associated course cards ### Decision Types - [Decision (Text)](/beast-core/docs/decision-text) - [Decision (Avatar)](/beast-core/docs/decision-avatar) - [Decision (Interface)](/beast-core/docs/decision-interface) - [Decision (System Viewer)](/beast-core/docs/decision-system-viewer) - [Decision (Simulation)](/beast-core/docs/decision-simulation) A named, mutable, stored value used for lesson routing based on learner interaction. Gives you an omnipotent bird's eye view of the workspace. A specific and defined piece of equipment or part within a system or a space.