| \n\nName\n\n | \n\nName of the external app configuration.\n\n |
| \n\nDescription\n\n | \n\nDescription of the external app configuration.\n\n |
| \n\nActive\n\n | \n\nOption for marking the configuration for external storage as active.\n\n |
| \n\nTable\n\n | \n\nTable in which the legal requestor legal matterinformation is stored. For example,- To store documents for a legal request, select the **Legal Request \\[sn\\_lg\\_ops\\_request\\]** table.\n- To store documents for a legal matter, select the **Legal Matter \\[sn\\_lg\\_matter\\_matter\\]** table.\n- To store documents for a contract request, select the **Legal Contract \\[sn\\_lg\\_contracts\\_repository\\]** table.\nThe selected table determines the available variables in the **Select variables** field.\n\n |
| \n\nCondition\n\n | \n\nFilter conditions to determine saving documents for a specific request category.For example, say you've already configured the Box external storage integration and want only NDA contract documents to be stored there, you can define the condition as **\\[Category\\]** **\\[is\\]** **\\[NDA\\]**.\n\nThen, select the external storage name in the **App** field.\n\n |
| \n\nExecution order\n\n | \n\nOrder in which an external storage system is used for storing documents. When multiple external storage systems match the conditions, then the one with the lower-order value is chosen to store the documents.\n\n |
| \n\nApp\n\n | \n\nExternal storage system on which the documents are stored.**Note:** The list only shows external storage systems for which spokes have been installed and configured.\n\n |
| \n\nFolder structure\n\n | \n\nFilepath to store documents attached to a legal request or legal matter in the external storage system.Define a folder structure using a combination of static text and dynamically generated text from the selected field variables in the **Select variables** list.\n\nFor example, in the folder structure `Legal/${company}/Contracts/${number}`,\n\n- `Legal` and `Contracts` are static texts\n- `${company}` and `${number}` are the field variables chosen from the **Select variables** list.\n\nThese field variables are dynamically replaced by the values in each field while saving a document in the external storage.\n\n |
| \n\nSelect variables\n\n | \n\nList of variables that can be used in the folder structure. Variables pull information from the selected table to customize the folder structure.\n\n |
| \n\nAttributes\n\n | \n\nAdditional configuration items based on your Microsoft SharePoint and iManage configuration. Add the following details:**Microsoft SharePoint**\n\n- **Tenant**: Add the sys\\_id of the [Microsoft SharePoint tenant record](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/create-tenant.md).\n- **Site\\_Name**: Add the name of the site in the tenant.\n- **Document Library**: Add the document library set up in the site where all documents related to legal requests and legal matters are stored.\nFor more information on managing Microsoft SharePoint tenants, sites, and document libraries, see the Microsoft documentation.\n\nThese fields appear only when **SharePoint** is selected from the **App** field.\n\n**iManage**\n\n- **Library**: When a value is specified, the application uploads documents using the designated library. This can also include the creation or using the Workspaces, folders, and so on. This attribute is optional, so if the library is not provided, the preferred library of the iManage service account user is used.\n- **Workspace\\_type**: Captures the type of Workspace to support the various use cases. For example:\n - **Shared**: Use an existing Workspace to upload documents.\n - **Independent**: Create a separate Workspace for every request and matter. This helps in effectively organising and tracking the documents. Independent Workspace may or may not use a template.\n- **Template\\_ID**: Unique identifier of the template from iManage. The application uses the identifier to create iManage objects such as Workspaces, folders, and subfolders using the template configurations while uploading the documents. This attribute is used when the Workspace\\_type is Independent. You can use templates to maintain consistent names and folder structure for Workspaces created in iManage.\n- **Folder\\_path**: Used to identify the folders or subfolders, in which the document is uploaded. This attribute is used when the Workspace\\_type is Independent.\n- **Shared\\_workspace\\_ID**: Unique identifier of the Shared Workspace. This is used to identify the Workspace to upload the documents when Workspace type is Shared.\nFor more information on iManage, see [iManage](https://help.imanage.com/hc/en-us/sections/4715521414683-Getting-started) documentation.\n\n**Note:** iManage login credentials are required to access the documentation.\n\n |
\n