Adaptive Learning Paths: Output Conditions

1 Initial Problem

Adaptive Learning Paths need information about what an object contributes to the further learning path after it has been processed. In a purely linear Learning Sequence, it is sufficient to open the next object in the order. For adaptive paths, however, it must be possible to define which states or values an object provides when it is left.

Without Output Conditions, subsequent objects cannot reliably react to whether a previous object has, for example, been completed, not attempted, failed or completed with a certain score.

2 Conceptual Summary

Output Conditions describe which state an object provides for adaptive navigation. They are created on an object of the Learning Sequence and can then be evaluated by Input Conditions of other objects.

The implemented Output Conditions are:

Output Conditions are therefore the outgoing part of an adaptive connection: they define what an object “offers” as soon as its state is evaluated.

3 User Interface Modifications

3.1 List of Affected Views

3.2 User Interface Details

Output Conditions are created in adaptive content management through the action "Conditions" of an object. The table is shown as a Kitchen Sink Table. Existing Output Conditions can be displayed in each object row, and new conditions can be added through the action menu.

When adding a condition, a drilldown opens. The available Output Conditions are offered there. Learning Progress variants are offered as subentries of the Learning Progress condition.

For simple Output Conditions such as Always, no further configuration is necessary. For configured conditions such as Points Output, a form opens in which the score is entered.

Existing conditions can be changed using the edit action. For configurable conditions, the same form is prefilled with the existing values.

Output Conditions use a shared condition concept:

3.3 New User Interface Concepts

No new UI concepts.

3.4 Accessibility Implications

Operation uses Kitchen Sink components such as Presentation Table, Drilldown, Modal and form fields. For accessibility, it is important that condition names and additional values are provided textually and are not recognizable only through icons.

4 Additional Information

4.1 Involved Authorities

4.2 Technical Aspects

Output Conditions are discovered automatically. Each Output Condition implements a shared interface and extends the condition base class. The generic tables are:

Condition-specific data is stored in dedicated tables. Examples:

Evaluation takes place at runtime through the respective condition class. Learning Progress Output checks the learning progress status. Points Output checks whether the object is completed and then provides its configured points value.

4.3 Privacy

Output Conditions can evaluate learning progress data. No new categories of personal data are introduced.

4.4 Security

No special security-relevant changes. Inputs such as point values are processed through form validation.

4.5 Contact

Person to be contacted in case of questions about the feature or for funding offers:  Auerbach, Jeanine [jeanine.auerbach]

4.6 Funding

Funding status and funding parties are listed in the block 'Status of Feature' in the right column of this page.

If you are interested to give funding for this feature, please get into contact with the person mentioned above as 'Contact'.

5 Discussion

6 Implementation

Feature has been implemented by {Please add related profile link of this person}

6.1 Description and Screenshots

{ Description of the final implementation and screenshots if possible. }

6.2 Test Cases

Test cases completed at {date} by {user}

6.3 Privacy

Information in privacy.md of component: updated at {date} by {user} | no change required

6.4 Approval

Approved at 21 OCT 2026 by Vorkauf, Klaus [KlausVorkauf].