TTL(Time To Live) Parameter in %Persistent Class

1️⃣ Description of the idea

Introduce a new TTL (Time-To-Live) parameter within the %Persistent class. When enabled and configured with a time value (in seconds), this parameter automatically adds an internal expiration timestamp property and add timestamp to each record when inserted. The system will then monitor and delete records once the TTL has expired. This mechanism provides an elegant, class-based alternative to managing temporary data traditionally stored in temporary globals.

2️⃣ Who is the target audience?

• Application developers who handle time-sensitive or transient data and migrating from temporary globals to class-based solution.

• System architects aiming for cleaner, declarative data lifecycle management.

3️⃣ What problem does it solve?

Eliminates the need for manual deletion logic or external cleanup jobs for temporary data if it's implemented by default.

Offers a standardized, declarative TTL mechanism across the data model.

Simplifies development by making expiration behavior part of the class definition without complexity.

4️⃣ How does this impact the efficiency, stability, reliability, etc., of the product?

Consistency: Encourages a unified and declarative approach to managing temporary data across applications.

Efficiency: Automatically purging expired records reduces memory/storage overhead.

5️⃣ Provide a specific use case or scenario that illustrates how this idea could be used in practice

A web-based scheduling system temporarily stores schedules for 30 minutes. When a user opens the scheduler, a class is defined to manage the session. The system automatically deletes these records after 30 minutes.