Portal Community

Pattern 1: Approval

The actor makes a binary decision: approve or reject. Optionally, they can add a comment to explain their reasoning.

AspectDetail
Actor inputDecision: Approved | Rejected, plus optional Comment
Output portsapproved, rejected, timeout
Multi-actorSupported via MultiPartyApprovalExecutor (Guide20)
Use casesBudget approval, contract sign-off, policy exception, user access request
Node typeApprovalNode

Pattern 2: Form Input

The actor fills out a structured form with specific fields. The form is defined by an Atlas Form ID — the actor sees the form rendered in their task inbox and submits it. The submitted field values become the node's output.

AspectDetail
Actor inputAny Atlas Form fields — text, numbers, dates, dropdowns, file uploads
Output portssubmitted, timeout
Multi-actorNot supported — only single actor
Use casesData enrichment, manager input on employee info, address correction, risk assessment form
Node typeUserFormNode

Pattern 3: Review

The actor reads presented content and acknowledges it. There is no approve/reject — just a required acknowledgement with an optional comment. Use when the workflow needs documented evidence that a specific person reviewed specific content.

AspectDetail
Actor inputAcknowledgement (checkbox or click) + optional Comment
Output portsacknowledged, timeout
Multi-actorNot supported — single reviewer
Use casesPolicy acknowledgement, SLA review, generated report sign-off, AI output verification
Node typeReviewNode

Choosing the Right Pattern

QuestionPattern
Does the actor need to approve or reject?Approval
Does the actor need to fill in fields?Form Input
Does the actor just need to confirm they saw something?Review
Multiple people must all decide?Approval (with All or Quorum strategy)