Act on an application's decision
Purpose
When an association reviews applications, the decision is made in the Submissions engine. Membership must turn each decision into what it means for the membership: an approval becomes a dues order, and a rejection releases anything held.
How It Works
The engine delivers each decision about Membership's two kinds of subject: a join, decided against a membership type, and a renewal, reinstatement or change, decided against a membership. Membership records it once by its identifier, ignores stale decisions, and lets a decision that names its predecessor replace it. The application becomes decided, awaiting the applicant, withdrawn or closed according to the delivered decision. An approval of a purchase process prepares the dues order through Membership's own checkout preparation, naming the approved application so the order needs no further approval. The order is placed once and recorded on the application. The membership stays pending until Commerce fulfils the order. A rejection, withdrawal or closing cancels any term reserved for the applicant. Membership then acknowledges the decision to the engine. A decision Membership cannot act on is left unacknowledged so the engine tries again. Neither the order placement nor the acknowledgement is connected to the real Commerce or engine yet.
Relationships
- Depends on
CAP-MBR-MEM-011because the process says what a decision drives. - Depends on
CAP-MBR-MEM-009because the dues order is prepared exactly as a checkout would be. - Depends on the Submissions engine (
MOD-SUB-SUB) for deliveries and acknowledgement, and on Commerce orders (MOD-COM-ORD) for placement.