ValidationAction

ValidationAction

Purpose Perform a domain-specific boolean check via MScript (quotas, object states, feature flags, plan limits, etc.).

When to use it

• afterCheckParameters (input sanity/business rules)
• afterFetchInstance / afterCheckInstance (state-based rules: locked, archived, protected)
• Anywhere a domain invariant must be upheld

Key fields

Behavior & absolute roles

• If errorStatus is 401/403, failures are treated as authorization; users with absolute roles bypass.
• If errorStatus is 400, failure is a business rule; no bypass—even for absolute roles.
• With storedCheck, result is put on context (e.g., this.validation_<name>), and the flow continues.

Example — forbid updates to protected items as business logic

{
  "id": "a200-validate-protected",
  "name": "preventProtectedUpdate",
  "description": "Protected items cannot be modified.",
  "validationScript": "this.instance?.isProtected === false",
  "shouldBeTrue": true,
  "checkType": "liveCheck",
  "errorMessage": "This item is protected and cannot be modified.",
  "errorStatus": "400"
}

Example — treat as authorization (allow absolute roles to bypass)

{
  "id": "a201-validate-approval-role",
  "name": "requireApproverRole",
  "description": "Only approvers may change this state.",
  "validationScript": "this.session.roles?.includes('approver')",
  "shouldBeTrue": true,
  "checkType": "liveCheck",
  "errorMessage": "Approver role required.",
  "errorStatus": "403"
}