Difference between revisions of "Purging and Archiving Data on the Platform"
From AgileApps Support Wiki
imported>Aeric m (Text replace - 'Category:System Administration' to 'Category:Installation') |
imported>Aeric |
||
| Line 7: | Line 7: | ||
:* When a record is deleted, it is moved to the Recycle Bin where it is purged after 30 days. | :* When a record is deleted, it is moved to the Recycle Bin where it is purged after 30 days. | ||
:* Custom purge mechanisms can be configured for required objects using Calendar based data policies where the logic for purging can be specified using Java code. | :* Custom purge mechanisms can be configured for required objects using Calendar based data policies where the logic for purging can be specified using Java code. | ||
:* | :* The platform provides a data export mechanism which can be used for data archiving. | ||
:* Data can also be read using the REST API and saved elsewhere.<noinclude> | :* Data can also be read using the REST API and saved elsewhere. | ||
<noinclude> | |||
[[Category:Installation]] | [[Category:Installation]] | ||
</noinclude> | </noinclude> | ||
Revision as of 18:36, 22 June 2011
Purging and Archiving Data on the Platform
To keep storage requirements to a minimum, perform these actions at regular intervals, using the platform GUI:
- Audit logs are purged after a retention period which can be configured.
- Debug logs used for development are retained for a day.
- When a record is deleted, it is moved to the Recycle Bin where it is purged after 30 days.
- Custom purge mechanisms can be configured for required objects using Calendar based data policies where the logic for purging can be specified using Java code.
- The platform provides a data export mechanism which can be used for data archiving.
- Data can also be read using the REST API and saved elsewhere.