To use this template, you must make some changes.

Modifying the template

Required:

• Set the SiteAddress variable.

• Set the Library variable (the name of the library where contracts should be backed up).

• Set the LibraryFilePath variable (the URL version for that library, which might be different from the library name).

Optional:

• Set the LegalContracts variable, renaming with your desired subfolder for your contract backups within SharePoint: the default name for the top-level subfolder is “Contract Backup”.

• Set the FolderName variable, which is the naming format for the structure of the subfolder created for each contract record.

• Modify the status message posted to that contract. This is the last action in the flow and acts as a notice on the contract record in LawVu that a copy of the file was successfully saved to SharePoint.

Folder structure and file naming

When backing up copies, think about naming conventions for the files and folder structures for the subfolders that each file is saved in. Note: these templates assume you want to back up all files with the current file name.

Saving a file in the same location with the same name will save it as a new version of that SharePoint file. Our suggested folder structure for saving files from the supplementary files tab of a contract record (see flow Upload a file to SharePoint when a new file is uploaded to a LawVu contract record) within a root SharePoint folder is:

Contract Backup

    [contract type]

        Contract record ID [ID] - [name]

The flows that back up the main contract file suggest having a subfolder for the main contract file and its subsequent versions. Changes to the file name in LawVu will result in separate files within this subfolder. Our suggested folder structure for saving the main contract document within a root SharePoint folder is:

Contract Backup

    [contract type]

        Contract record ID [ID] - [name]

            Contract document

Other flows to combine with this flow

If you want to have every single version of any contract record backed up to SharePoint (or some analogous location), then you should use a combination of the contract flows:

• Upload a file to SharePoint when a contract document is updated in LawVu and

• Upload a file to SharePoint when a new contract record is created in LawVu

If you only want a copy executed contracts backed up to SharePoint (or some analogous location), then you should use a combination of the contract flows:

• Upload a file to SharePoint when an already executed contract is uploaded to LawVu and

• Upload a file to SharePoint when a contract is executed in LawVu

This is because the trigger for flow Upload a file to SharePoint when a contract is executed in LawVu only captures existing contract records that progress from another lifecycle stage to Executed. You’ll need the flow Upload a file to SharePoint when an already executed contract is uploaded to LawVu to also capture contract records created directly into that lifecycle stage.