Dormancy Guide

Automated alerts to users before their account enters a dormant state or incurs fees.

The implementation of a "dormancy" feature typically focuses on managing and automated fee processing for inactive entities. This is common in financial platforms, membership systems, and customer loyalty programs to maintain system hygiene and comply with unclaimed property regulations. Key Components of a Dormancy Feature

: Define a progression of states (e.g., Active → Inactive → Dormant → Unclaimed). dormancy

: Establish a recurring schedule (e.g., daily at a specific timezone) to scan for accounts hitting these thresholds.

: Identify specific actions or processing codes that automatically return an account to "Active" status. Functional Requirements for Developers Feature Attribute Description Config Level Automated alerts to users before their account enters

Define how settings at a higher level (like a division) flow down to sub-programs.

Automated deduction of "maintenance fees" from dormant accounts, often governed by local financial laws. Technical Considerations Key Components of a Dormancy Feature : Define

When building this in an API-driven environment, you can use specialized tools like the Pismo Create Dormancy Configuration endpoint to define these lifecycles. For biological or agricultural software, a dormancy feature might instead track environmental triggers like temperature or light cycles to predict "release" and "germination". Dormancy overview - Pismo Developers Portal