@acorex/modules 21.0.0-next.57 → 21.0.0-next.63

package/assessment-management/README.md

@@ -17,7 +17,7 @@ The **Assessment Management Module** provides a comprehensive, generic assessmen
 - **Publication Modes**: Assigned (specific users), Open (anyone with link), Embedded (in other modules)
 - **Multi-Responder**: Support for collaborative responses with role-based permissions
 - **Timer Support**: Countdown, elapsed, scheduled, and no-timer modes
-- **Questionnaire calculations**: Named expressions (`resultKind` + `expression`) on Questionnaire; evaluated in the viewer for summaries and placeholders (see `features/questionnaire-calculations/README.md`)
+- **Questionnaire outcomes**: Named expressions (`resultKind` + `expression`) embedded on Questionnaire; evaluated in the viewer for summaries and placeholders
 - **RuleSet-Based Scoring** (planned): Optional RuleSet entity for additional backend scoring patterns
 - **Conditional Logic**: Skip logic, branching, dynamic visibility
 - **Real-time Tracking**: Progress tracking, time spent, completion percentage
@@ -64,7 +64,7 @@ Assessment template with embedded sections and questions (value objects).
 - Embedded sections and items (not separate entities)
 - **Pre-questionnaire**: Welcome screen before questions (rich text, multi-language)
 - **Post-questionnaire**: Review step before submit, summary screen after submit
-- **Questionnaire calculations** (related entity): Named values from expressions; see `features/questionnaire-calculations/README.md`
+- **Questionnaire outcomes**: Named values from expressions embedded on the questionnaire (`outcomes.sections`)
 - **RuleSet** (planned): One-to-many RuleSet entity for additional scoring scenarios
 - Timer and navigation settings
 - Question randomization
@@ -298,9 +298,9 @@ Performance and quality assessment.
 
 ---
 
-## Scoring and calculations
+## Scoring and outcomes
 
-**Questionnaire calculations** are implemented today: the `QuestionnaireCalculation` entity stores `resultKind` and `expression` per questionnaire; `questionnaire-viewer.service` evaluates them (with `answer.eval`, `outcome.eval`, `fn.*`) for post-submit summaries and `{{name}}` placeholders.
+**Questionnaire outcomes** are implemented today: the embedded `outcomes.sections` field stores `resultKind` and `expression` per outcome rule; `questionnaire-viewer.service` evaluates them (with `answer.eval`, `outcome.eval`, `fn.*`) for post-submit summaries and `{{name}}` placeholders.
 
 **RuleSet** (planned) may add backend-side JSON expression trees and aggregation at submit time for scenarios that need server evaluation only.