Skip to main content

​
Field Dependencies (Parent/Child)

Field Dependencies let one field (the “parent”) run first and provide its result as context to another field (the “child”). This is useful when a child field needs accurate upstream information to produce the right output.

​
When To Use

  • You need to reuse structured information across fields (e.g., a parsed price feeding an email).
  • Multiple fields form a logical sequence (extract → reason → write).
  • You want consistent, single‑source‑of‑truth values across deliverables.

​
Examples

  • Pricing in emails: A “Price Calculation” field extracts or calculates a customer‑specific price. A “Follow‑Up Email” field depends on it so the email always references the correct price.
  • Next steps clarity: A “Next Steps” field lists exact action items. A “Status Update Email” depends on it to generate a crisp, accurate status message.
  • Persona tagging → tailored copy: A “Persona Detector” identifies roles. A “Recap Email” depends on it to adapt tone and focus (e.g., CFO‑friendly summaries).
  • Decision drivers → objection handling: A “Top Decision Criteria” field captures what matters. An “Objection Response” field depends on it to address the right points.

​
How It Works

  • Ordering: Parent fields run first, then children. Fabius injects parent outputs/scores into the child’s prompt as “past fields” context.
  • Scope: Parent results come from the same interaction (call/document) being analyzed.
  • Transparency: In the UI, you’ll see “Parent context” with the parent results so you can verify what influenced the child output. In the modal, click a parent’s name to open that field in a new tab.

​
Setup

  1. Create both fields (parent and child) in Analysis → Fields.
  2. Open the child field (Settings → Analysis → Fields → your field) and use the “Parent Field Dependencies” card to add parent fields. Use the trash icon to remove a dependency.
  3. Use draft testing to validate the flow—the parent runs first and the child’s output incorporates it.
In draft testing, Parent context is shown automatically whenever the field has dependencies. Click the “Parent context” badge to see the upstream values that fed this result. This appears in both the stacked view and the comparison table — no toggle required.

​
Design Guidelines

  • Keep parent fields atomic: extract or compute one clear thing.

​
Troubleshooting

  • Child output looks “off”: Inspect Parent Context. If the parent value is wrong/missing, fix that first.
  • Conflicting parents: Avoid overlapping responsibilities; split responsibilities or designate a single source of truth.
  • Unexpected order: The system runs all parents before the child. If you chain multiple levels (grandparents), keep each step simple.
Next: