Decision tables in Agent Block can now carry a value that the agent fills silently once the respondent's answers pin a row. Derived values ride along to records, exports, and process board cards without appearing as a question.
If you use Records-backed decision tables in an Agent Block, you may have a column that should be filled automatically once a row is matched rather than asked as a question. A product code, a tier identifier, an internal category. This release adds that.
Mark any mapped column in a decision table as “fill silently from match.” Once the respondent’s answers identify a row, that column’s value is pulled from the matched row and saved to the submission. It never shows up in the conversation.
The derived value behaves like any other field from that point: it appears in record mapping, process board cards, exports, and action block field mappings. Nothing downstream needs to know it came from a table lookup rather than a respondent answer.
Before this, you could only output columns the agent explicitly asked about. If you needed a derived value (like a plan code that depends on the combination of size and coverage type), you either asked the respondent a question they couldn’t meaningfully answer, or left the derivation to post-processing elsewhere.
Now you define it once in the table. The agent handles the logic.
Agent block decision tables can now carry a value that is implied by the chosen combination but never asked. Mark a mapped column 'fill silently from match' and, once the respondent's answers pin a row, that column's value (for example a unique code per combination) is pulled from the matched row and saved to the submission. Derived values ride along to records, exports, and process board cards like any other field, but never appear as a question in the conversation.
