Skip to main content

Type Alias: ActivityEventFamily

ActivityEventFamily = typeof ActivityEventFamily[keyof typeof ActivityEventFamily]

Defined in: packages/sdk/src/types/generated/family.ts:43

The six kinds of thing that happen. Closed, and deliberately small.

The cut is a judgement call and the values are what a reader would call them, not what our modules are called:

  • PEOPLE — who is in the workspace and what is recorded about them: the member lifecycle, role and label changes, field edits, and the imports that do all of those in bulk.
  • CONVERSATIONS — every exchange with a person, in any channel: chats, escalations, calls, voicemail, and a Member's run through a Workflow (assignment.* is our internal name for one — see the glossary). One family rather than five because "someone was talking to a patient" is one question; the channel is a detail of the answer, and it is one rung further down. A workflow run belongs here even though a machine drives it: what it produces is an exchange with a person, and a reader looking for "who did we talk to" expects to find it.
  • JOURNEYS — a member's progress through a journey.
  • AUTOMATION — the machine working on its own, with nobody on the other end: routine runs and a workflow being published.
  • OPERATORS — who is available and who is in which group. Separated from PEOPLE because presence is high-frequency and about staff, and folding it into member activity would drown the member changes that are the reason anyone opened the feed.
  • ADMINISTRATION — the account around the work: phone numbers, domains, settings, subscriptions and purchases.

Commerce is folded into ADMINISTRATION rather than split out. It is a genuinely separable family and a reasonable person would split it; it is here because on a clinical workspace's feed a subscription change and a business-hours change are the same kind of interruption — somebody changed the setup — and a seventh clause competing for one line of a row costs more than the distinction buys. Splitting it later is one entry in the table below plus one translation, which is why it is safe to start merged.