Document Archival and Retention |
With version 13 of GLOBODOX, we introduce the long-awaited Document Retention and Archival module. These comprise of the following features for both Documents and Stacks…
You can now create an Archive DB for every GLOBODOX DB (referred to henceforth as the Source DB). Any documents or stacks marked as Archived in the Source DB are moved to the Archive DB every few hours.
When an Archive DB is created it is blank. Once the ITAZ GLOBODOX ARCHIVAL SERVICE processes this DB for the first time, then Folders, Tags, Document Types and Stack Types get automatically created as required.
A Document Type and Stack Type is only created in the Archive DB when the first document or stack of that type is moved to the Archive DB.
For example, the source DB may have Agreements and Invoices as the two defined Document Types. But if only documents of the type Agreement have been marked as Archived then only the Agreement document type will be created in the Archive DB.
You can create multiple Archive DBs. This may be required if over the years your Archive DB becomes very large or if you prefer to have different Archive DBs for each year.
The Source DB is always linked to the newest Archive DB that was created.
The Archival Date, Expiry Date and Recycle Bin features work even if you choose not to create or use an Archive DB. In this case documents or stacks marked as Archived continue to reside in the Source DB but the permissions on them change.
To create an Archive DB…
Note: Only users with ‘Manage Archived’ privilege can create an Archive DB.
To archive documents in the same DB (and not create a separate Archive DB)…
Note: Only users with the ‘Manage Archived’ privilege can set this option.
When you create an Archive DB, you can choose a security label which will be automatically applied to any document or stack marked as Archived. Users listed in that security label will have access to the archived documents and the actions they can perform will also be those listed in the security label.
Security is applied to archived documents and stacks via a security label. You can either select another security label or edit the settings of the currently selected security label.
To change the Security Label…
To change the settings of the currently selected security label…
To create a new Archive DB…
Note: All Documents and Stacks will now be archived to the new Archive DB. The old Archive DB will still be accessible though it will not be used anymore for archiving additional documents or stacks.
A field called Archival Date gets added to a Document Type when the Archive Documents of this Type option is checked*. If you want a document to be archived, simply use this field to enter the date on which you want the archival to happen. On the specified date, the document will be marked as Archived.
No changes can be made to Archived Documents. Also, if a Source DB is linked to a Archive DB then Archived Documents will be moved to the Archive DB within a few hours of being marked as Archived.
*For Stacks the option is called Archive Stacks of this Type and everything else works the same.
To set an Archive date…
Note: You can also multi-select multiple documents in a Document Type or multiple stacks in a Stack Type and set the date value for this field. You can also Right-click and choose the option Set Expiry date to set the value.
This is currently not possible.
You cannot unarchive a Document or Stack, once it is marked as Archived.
You can manually delete Documents and Stacks in the Archive DB. Once a document/Stack is archived, a security label is applied. Now only users with the Delete privilege in the Security Label can delete data and documents in the Archive DB. You can also use the Expiry Date feature.
This Windows service handles the moving of documents and stacks from the Source DB to the Archive DB. Only documents and stacks marked as Archived are moved to the Archive DB.
The Expiry Date feature lets you set a expiry date for a document or a stack. You can choose to have the document automatically deleted (or moved to the Recycle Bin) on the Expiry Date. Alternatively you can search for documents which are past the Expiry Date and then manually delete them.
To enable the Expiry Date feature, you must be logged in as Superadmin or a user with a Superadmin role.
To enable this feature…
To set an Expiry date
To set an Expiry date
You can now configure GLOBODOX such that any documents or stacks you delete are moved to the Recycle Bin. Documents or stacks stay in the Recycle Bin for a period of time (which you can specify) before they are automatically delete.
While documents or stacks are in the Recycle Bin, they can be restored (i.e. Undeleted) or they can be deleted permanently.
When a Stack is deleted, it is moved to the Recycle Bin along with all the documents in that Stack. When you undelete this stack the documents which were part of the stack are undeleted as well.
To enable the Recycle Bin feature, you must be logged in as Superadmin or a user with a Superadmin role.
To enable this feature…
To empty items in the Recycle Bin...
Note: All items present in the Recycle Bin will be deleted.
To delete items once recycled..