External Document Storage

> Administration > Account Management > External Document Storage

If the enterprise has an external Content Management System (CMS), the platform can use it for Document Storage for File Fields and Image Fields of AgileApps Live.

Caveat

This functionality is highly recommended to be used by only new tenants after 10.6 upgrade. Enabling it in existing tenants created before 10.6 version will make the File and Image fields usage unavailable.

Configuration

Configuration to Content Management System can be set by users with 'Manage Company Capabilities' enabled in their access profile. Configuration can be set by clicking on the > Administration > Account Management > External Document Storage .

Following fields are available for providing connection and authentication information to CMS

• Enabled (Checkbox to enable External Document Storage)
• AtomPub URL (e.g., Alfresco AtomPub URL is http://host:port/alfresco/cmisatom)
• Username
• Password
• Repository Id
• Root Folder Id

If External Document Storage is enabled, URL, Username, Password and Repository Id are required fields. Root Folder Id is not a required field and if dedicated root folder is not provided for this tenant, Repository's root folder will be used to store the documents.

Platform Behavior and User Experience

After the configuration has been set, files and images uploaded to the File Fields and Image Fields are stored in the CMS. The path used to store the documents is in the format {objectId}/{recordId}/{fieldTableColumn}/FileName under the root folder.

Clicking on file field and image field values in the record page, downloads the files from CMS server and shows it to the user.

Files from CMS are deleted when

• a file/image is removed from the AAL record by editing the record and removing it
• an object record with file/image fields is deleted forever from Recycle Bin.
• a file or image field is deleted from the Object Fields page (Customization in setup).
• an object is deleted forever from Recycle Bin (Customization in setup)
• When a tenant is deleted and if the Root Folder Id is set in the configuration, then the given root folder and its contents are removed from CMS.
• If root folder Id is not specified then the files are not deleted when deleting tenant. This approach is used to not accidentally delete the files in case if the default repository root folder is used for many tenants.