A method and system for implementing retention based hold on entities in a Records Manager application is disclosed. The method introduces a Hold Phase in a Disposition Schedule of an entity’s lifecycle. Further, the holds are automatically removed from the entities after completion of a retention period for Hold Phase.
Method and System for Implementing Retention Based Hold on Entities in a Records Manager Application
Disclosed is a method and system for implementing retention based hold on entities in a Records Manager application.
Generally in a Records Manager application, holds on entities are placed to liaise with any legal adherence that requires entity to hold its disposition. Further, the holds are retained by one or more conditions managed within the entity. However, this disclosure exposes another dimension to apply holds on entities, i.e. as a Disposition Phase in the Disposition Cycle, which gives a retention and approval handler to the Records Manager application. Therefore, being a Disposition Phase, the holds are automatically controlled by a Disposition Sweep instead of a Hold Sweep.
In a scenario, an entity may be required to be put on a Hold Phase for a specified period of time during the lifecycle of the entity "instead of"/ "along with" a specific condition to match. The lifecycle of the entity includes a Disposition Schedule flexible enough to add a Hold Phase during the lifecycle of the entity. Therefore, a Hold Phase may be added at any point of time in a Disposition Cycle of the entity. Further, the hold is removed automatically from the entities after completion of a Hold Phase retention period and its due approval workflow at the phase end. The execution of Hold Phase on the entities is performed by a Disposition Sweep.
In an embodiment, a Hold Phase implemented on an entity may be independent of any conditions. Therefore, the conditio...