Difference between revisions of "Purging and Archiving Data on the Platform"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
=== Purging and Archiving Data on the Platform === | <includeonly>=== Purging and Archiving Data on the Platform ===</includeonly> | ||
To keep storage requirements to a minimum, perform these actions at regular intervals, using the platform GUI: | To keep storage requirements to a minimum, perform these actions at regular intervals, using the platform GUI: | ||
| Line 6: | Line 5: | ||
:* Debug logs used for development are retained for a day. | :* 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. | :* When a record is deleted, it is moved to the Recycle Bin where it is purged after 30 days. | ||
:* The platform provides a data export mechanism which can be used for data archiving. | :* 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. | :* Data can also be read using the REST API and saved elsewhere. | ||
<noinclude> | <noinclude> | ||
[[Category: | [[Category:Installable Version]] | ||
</noinclude> | </noinclude> | ||
Latest revision as of 19:34, 2 April 2014
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.
- 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.