Page tree
Skip to end of metadata
Go to start of metadata

An Archival policy type is designed to help you create a more cost effective systems for long term.

Therefore, you can create a policy to move and store old organizational content in the following ways:

  • If you choose No Action, you will see an error that it is not supported and you will not be able to create the policy
  • After the specified time period is reached, content gets moved to a specific folder or location (Archive)

The following table identifies what actions are blocked for an Archival type of retention policy.

 Policy Type

Reads 

Blocked

Moves

Blocked

Copies

Blocked

Updates

Blocked

Deletes

Blocked

Policy 

Length

Expiration Actions
RetentionNONONONOYES
  • Time Period
  • Fixed Date
  • Move files to a specific location

 What is a use case for an Archival Policy?

This type of policy helps an administrator plan for the future by setting up a process to run automatically when the time comes.

For example: 

  1. If phone records only have to be accessible in the system for 5 years, but stored for at least 10 years, then the Administrator doesn't have to just remember to move the current phone records in 5 years into storage.
  2. The administrator can just create an Archival policy to move them automatically in 5 years.

This also allows a process to run independent of an employee's length of service.

For example: if the same employee is no longer an Administrator in 5 years, but the old records still need to be moved, they will be. 

Creating the Policy


To create an Archival Policy:

  1.  Log in to the Admin Portal.
  2. From the left navigation pane, select Retention.
  3. On the Manage Retention Policies screen, click the Add Policy button.


 4. Completely fill out the Policy Attributes section.


PropertyDescription
Policy NameA string of characters, letters, and numbers that provide a title for the policy
 Policy Type

 Select Archival

Description
  • Required
  • A string of characters, letters, and numbers that provide details about why the policy is necessary
  • This description is displayed in the User Portal when the cursor hovers over the Policy Name in the Details tab
Hide Policy from Users
  • Prevents policy details from being shown and leaked. 
  • Selecting this option removes the display of applied policies and their expiration dates from the Details tab in the User Portal.
  • Selecting this option also blocks the API call to the backend to find out which policies are applied. This is how data leaks are prevented.
  • Although the policy name and expiration date are not shown, the restrictions are still enforced. For example, if the policy you are hiding from users prevents them from deleting the file, although the policy information is not shown, the user will not be able to delete the file.

(warning) Administrators need to be aware that users might report issues with the system when a retention policy is blocking their ability to access or delete a file or folder. The user will not be aware of why certain options are greyed out if they don't see the policy restrictions listed. However, if the user is able to select the option and it is restricted by a policy, they will see an error message telling them why when they try to select the option.

Alert on Violation

Displays an alert in the Admin portal on the Governance dashboard. 

(warning) Administrators need to be aware that not all violations are logged here. The reason for this is that all permissions for a file are collected in one file- including user permissions and sharing permissions. In some cases, a sharing permission that was set first might stop a file from being deleted before a retention policy that was added later. The reason why the file cannot be deleted, or which set of permissions or policy is stopping the deletion, is not FileCloud's main priority. FileCloud's main concern is protecting the file and finding out if it cannot be deleted. This is why you might not always see a violation in the Dashboard, but the file will always be protected. If a user is constantly trying to delete a file that is protected by a retention policy then the chances of seeing the violation in the Governance Dashboard increase.

Send email alert

Notifies all provided recipients that there are only 7 days until the policy expires.

(info)  The same information is available on the Governance dashboard. The Governance Dashboard list each file individually, and displays the date and time when a policy will expire so the Admin knows and can take action if any is needed.

 AlertsA list of email addresses separated by a comma who will receive the email notification that there are only 7 days until the policy expires.
 5. Attach folders or files in the Apply Policy To section.

The Path and the Metadata tabs allow you to define the conditions that specify how the policy will be applied in the system.

Add a Path

Add Path allows you to define a folder that a policy will apply to AS WELL AS all the files and sub-folders it contains

What you CAN do in the Path fieldWhat you CANNOT do in the Path field
  • Paths work for managed storage  ONLY
  • Since managed storage includes Team Folders, you CAN add a path to a Team Folder
  • A Path takes the form of: /username/sub-folder
  • You can add more than 1 path
  • You can set BOTH a path and specify metadata
  • You CANNOT add a path to network folders
  • You CANNOT add a path to external folders
  • You CANNOT add a path to shared folders
  • You CANNOT add a path to protected folders, such as /boot, /root, and /var in LINUX
  • You CANNOT edit a path. If you make a mistake, you must first remove the path and click Add to specify the correct path
  • The full path must exist before the policy will be enforced

When creating the policy the full path doesn't have to exist, however.

At a minimum: 

  • The first component of the path has to already exist /username/
  • This means that the username or team folder has to already exist before you can save the policy
  • You CANNOT specify a path that does not exist

This will prevent you from saving the policy


Configure Metadata

Data that provides additional information about files and folders is called Metadata.

  • To specify files and folders that this policy should apply to, you can use metadata sets, attributes, and tags.
  • You can use metadata to apply a policy to all files that meet the metadata conditions even if they are not in the same folder.

You can select metadata from the following existing attributes or sets:

  • Default sets = provided with FileCloud Server and applies to every folder and cannot be modified Tell me more about the Default set
  • Built-In sets = provided with FileCloud Server and includes the Document Life Cycle and Image metadata sets, NEW for 19.1  Tell me more about these new sets
  • Custom attributes and sets = created by administrators in the Admin Portal 



 6. Set the Expiry Actions

You can configure an Archival policy to expire in a set Time Period or at a Fixed Date.

 

To set a Time Period:

  1.  In the Actions section, click Time Period.
  2. In Time Period of Retention, click the down arrow.
  3. From the list, you can select a built-in option:
    1. 30 days
    2. 60 days
    3. 1year
    4. 2years
  4. From the list, you can also select Custom.
    1. In No. of days, type in a whole number greater than 0.

To set a fixed date:

  1.  In the Actions section, click Fixed Date.
  2. Click in the Expiry Date text box.
  3. A calendar will be shown with the current month.
  4. Select a date from the calendar.

Renew Expiry on Access: this is a set number of days or years that is used to calculate when the policy expires based on the last access date. 

(warning)  Available only if the Time Period  option is set, and selected by default.

Renew Expiry on AccessExpiration Date

For example, if on March 2, 2019, for an X-ray, you set expiry to:

  • Time Period = 60 days
  • Renew on Access = selected

Then the policy will expire on May 2, 2019 UNLESS: 

  • If a doctor previews the file before May 2, say on May 1, 2019

Then the 60-day time period will be reset to July 1, 2019. 

(lightbulb)  The ACTUAL date is reset by a user every time they access the file.

To set Renew Expiry On Access:

  1.  In the Actions section, next to Renew Expiry on Access, make sure the checkbox is selected.

When a Retention policy expires, you can configure it to allow access to or delete the attached files and folders.

To set Policy Expiry Actions:

  1. In Policy Expiry Actions, select either:
    1. No Action :  Although this option is available, if you select it you will get an error and will not be able to save the policy
    2. Archive :  After the specified time period or fixed date is reached, content is moved to a specific folder or location 
  2. If you select Archive, in Archive Path you must type in a path to the location where the files are moved.



  • No labels