[Util] Validate Question Set

Checks question structure and TypeSafe limits locally so malformed or risky question sets can fail before a billed decision call.

Inputs

Supply exactly one:

Parameter	Description
Questions	JSON object keyed by question ID.
Question set	A file from the configured classpath question-set folder.

The Question set selector lists JSON files under src/main/resources/questions/. Incoming message attributes are explicit null metadata and are not read.

Output

The payload is a JSON object with valid, errors, and warnings. Output attributes are null. valid is true only when errors is empty; warnings alone do not fail validation.

Happy path — Set Up sample

Validating the Set Up file support-ticket-triage.json:

{
  "valid": true,
  "errors": [],
  "warnings": []
}

Errors and warnings together

A deliberately broken file can return both arrays. Example payload from support-ticket-triage-error.json:

{
  "valid": false,
  "errors": [
    "broken: type must be one of noul, choice, score",
    "broken: instructions are required",
    "broken: 'options' is not a TypeSafe question field; put it under 'criteria'"
  ],
  "warnings": [
    "team: choice has no no-match option; consider adding one",
    "team: option 'technical' has an empty description",
    "team: duplicate option description 'Payments'",
    "sentiment: score has fewer than 3 levels"
  ]
}

Validation behavior

Errors include:

• Missing or empty questions
• Unknown question types
• Missing instructions
• Missing Choice criteria or more than 255 options
• Fewer than 2 or more than 10 Score levels
• Legacy options, levels, legend, criteriaTrue, or criteriaFalse fields outside criteria

Warnings include:

• Choice with no no-match option
• Empty or duplicate option descriptions
• More than 20 Choice options
• Fewer than 3 Score levels

Provider call

None. The operation does not read the connection or API version.

See the limits in the TypeSafe API documentation.

XML examples

Validate a classpath file:

<typesafe:validate-question-set
    config-ref="TypeSafe_Config"
    questionSet="support-ticket-triage.json" />

Use an application-specific file name. Connector 1.0.1 ships a bundled ticket-triage.json sample that can take precedence over an application file with the same classpath path (issue 15).

Validate an inline Questions object:

<typesafe:validate-question-set config-ref="TypeSafe_Config">
    <typesafe:questions>#[payload]</typesafe:questions>
</typesafe:validate-question-set>

See also

• Set Up a reusable question set
• Evaluate