@rrudramu

You can create a job that will open each instance from the Work class, then perform Page-Change-Class to the archival class. After the commit, delete the instance from the work class on the same iteration. This should automatically take care of saving the History instance in the archival class and also deleting the original instance from the main class.

@rrudramu you can create Dataflow and Dataset rules in the History class for implementing custom data archival in Pega. Ensure the History class is linked to the correct database table with all required columns and indexes for smooth data extraction. The Dataflow rule can be used to move data from the History table, while the Dataset rule helps define the data source and destination, such as a file or another database table. When creating these rules, consider using filters like date ranges or resolved statuses to archive only relevant data.