An ordered array like [{label: 'Purchase order', value: 'PO-1002'}, {label: 'Project', value: 'Miller 40x60'}]. The junction decides what leads. The reminder appends the due date to the list if the junction did not already include it. The API shape-checks and caps at eight facts with trimmed labels and values.
Also called: reminder detail · PO number in the reminder · task facts · at-a-glance list
- 1TaskContext.facts flows to detailFacts on POST /api/tasks and is stored on tasks.detail_facts.
- 2The reminders cron reads them, adds Due if missing, and passes them to notifyUsers as facts.
- 3The email renders them as its at-a-glance card; the SMS stacks them, dropping any fact whose value the title already states and capping from the front.
Migration 223 records the problem: “A reminder's DETAIL used to live only in the prose note, so every channel got the same wall of text: the email printed a paragraph where it had a context card sitting empty beside it, and the text message could only be truncated.” The SMS de-duplication rule has its own note: 'Without the first rule the amount and the supplier repeated themselves and pushed the due date off the end.'
- One prose blob shared across channels
- Truncated SMS losing the due date
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →