Skip to main content

Card lifecycle model

When working with Atomic triggers and cards it is useful to consider the Atomic Card Lifecycle Model. The lifecycle model describes the various states that a card can be in, and how the card can move between states from the time it is first created, until the time it is closed.

Card Lifecycle Model

The lifecycle model consists of states, transitions, and triggers. A card can only be in one state at a time and can transition between states when certain trigger conditions are met.

States

States break down into two categories - Open and Closed. As illustrated, cards always travel from open to closed. There are no subsequent transitions available once a closed state is reached. Cards can never move from a closed state to a different closed state, or back to an open state.

Open States

There are three open states, Active, Embargoed and Snoozed.

1. Active

When a card is active, it is available for viewing and actioning by the end user.

TransitionsTrigger
Snooze: Active → SnoozedUser Driven trigger occurs when end user snoozes card.
Unsnooze: Snoozed → ActiveScheduled system trigger occurs when a card snooze expires.
Publish: Embargoed → ActiveScheduled system trigger occurs when embargo expires.
Dismiss: Active → DismissedUser Driven trigger occurs when user dismisses card
Action: Active → CompletedUser Driven trigger occurs when user actions card
Cancel: Active → CancelledAPI Driven trigger occurs when a cancel instruction is received
Expire: Active → ExpiredScheduled system triggers occurs when card expiry time is reached.

2. Embargoed

An embargoed card is not available to the end user. Once the embargo period expires the card will transition to an active state.

TransitionsTrigger
Publish: Embargoed → ActiveScheduled system trigger occurs when embargo expires

3. Snoozed

A snoozed card is not available to the end user. Once the snooze period expires the card will transition to an active state.

TransitionsTrigger
Snooze: Active → SnoozedUser Driven trigger occurs when end user snoozes card.
Unsnooze: Snoozed → ActiveScheduled system trigger occurs when a card snooze expires.

Closed States

There are four closed states. Completed, Cancelled, Expired and Dismissed.

1. Completed

When a user actions a card, the card enters the completed state and is classified as closed.

TransitionsTrigger
Action: Active → CompletedUser Driven trigger occurs when end user actions card.
Action: Any Open State → CompletedAPI Driven trigger occurs when a remote action instruction is received.

2. Cancelled

When an API cancellation instruction is received the card is moved to the cancelled state and is classified as closed.

TransitionsTrigger
Cancel: Any Open State → CancelledAPI Driven trigger occurs when a cancel instruction is received.

3. Expired

Cards move to an expired state when the expiry date and time is reached. They are then classified as closed

TransitionsTrigger
Cancel: Any Open State → ExpiredScheduled system triggers occurs when card expiry time is reached.

4. Dismissed

When a user dismisses a card, the card enters the dismissed state and is classified as closed.

TransitionsTrigger
Dismiss: Active → DismissedUser Driven trigger occurs when end user dismisses card.