ETL

• License must be C4 or higher.

OR

Two add-ons are included with the license:

• Move Between Teams and DMS
• Auto Sync Between Teams and DMS

• Go to the Configuration tab in ETL Manager.
• The Cloud Provider and Storage is currently hardcoded to AWS and S3.
• In the second Storage lookup, select the particular existing bucket. Or Set the Bucket Name to create a new Bucket.
• Set the API Endpoint Base URL, the url used for the CAM URL. E.g. https://firmname.prosperoware.io, Prosperoware will share the URL.
• Enter the API Secret Key configured from Azure Portal. Prosperoware will generate key and share.
• Click Validate and you should see a green bar on top of the page saying Validation Successful.
• Click Save. A validation message appears saying the Configuration was successful.
• Then go to the Default Settings tab. This tab shows all mapped ETL systems to run jobs off of.

The following information is displayed on this panel:

Column	Description
From	Shows the system the ETL is reading from. Always will be Office 365
To	Shows the system the ETL will move or copy to. Typically the DMS system
Enabled	Displays if the job is enabled or not.
Bringing Chat Files	Displays if the job includes moving/copying chat files over
Source Security Applied	Displays if the job applies the source system security (the system in the from column)
Sync Interval	The job sync internal (in minutes, hours or days)
Start Date	The job start date to start on.
Actions	Allows below actions based on permissions: Edit ETL Config job Delete ETL Setting

 

• Click Add New from the Default Settings tab.
• Set if the job will be enabled from the start. If it will be, select Yes.
• From System will be auto-populated to Office 365. This cannot be changed.
• Select the To System. Currently supported systems are: HighQ, iManage, Office 365, Fileshare and NetDocuments.
• Select the repository if multiple repositories exist on the external system.
• Set up a new job internal in New Interval. Set the period in Every, select the time measure (minutes, hours or days), and set the starting period date (today, in the future).
• Add Profile of the job next:
  • First setup the Metadata to be displayed at settings form as follows
  • Create a Layout at Adminitration -> Layout ->Forms -> +Add Form.
  • Select ETL-DMS from Where to be displayed.
  • Add Metadata to be displayed on Profile section and provide Access.
  • click Save.
• Metadata can be set as default value or forced value.
• Add Settings as follows:
• Select whether or not to bring file as documents or shortcut.

Note: Chat files are always saved as JSON file.

• Select whether or not to import the Post files into the teams/channels/tabs when moving.
• Select to apply the system security either from Source or Target to the moved channel/team/tab.
• Option to create new users would be visible if Source security is selected in the above step. It allows to Create new users (if doesn't exists) with three options as below:

Option	Description
No Users	No new user is created; it applies default security Private to common user between Source and Target.
Internal Users	Internal Users of Source system is created on Target system with default security Private.
Every User	All users from Source system is created on Target system with default security Private.

• Click Save.

The mapping now is setup and displays in the Default Settings tab.

When ETL Job is executed, it displays in the ETL Manager -> Jobs tab and provides the following information:

Column	Description
System	The Source (from) System of the ETL Job. Always is Office365
Entity Type	The type of object being moved (Teams, Channels, Tabs)
Entity name	The name of the particular object being read from
Repository	The Source system Repository
System	The target (To) system (DMS System)
Entity name	The name of the object being moved to.
Repository	The target system repository
Created Date	Date job was created
Edited Date	Date the job was last edited
Job Status	The current status of the ETL job. Statuses are: Queued, In Process, Error, Complete.

Tip: Results in the ETL Jobs can be filtered. For the filter to work, users must put both a Source system and target system in the filter.

Action menu items are:

Action	Allows User To
Edit Job Setting	Edit default settings
Retry	Retry the failed job
Retry the subscription	This option will show on a selected job on the menu item if the job type is "Subscription" and Job status is "SUBSCRIPTION_FAILED".
Deactivate	Deactivate the selected job from execution
Delete	On click, warning dialog pops-up with Reason textbox and informs what will happen if you delete the job. "Once you delete the job, it will stop synchronizing documents from source to destination. Current synced documents will remain as is"

Similar to the Creating a New Job from the ETL Manager, users can add jobs from the object in Matters.

• Go to the Matters tab in CAM.
• Find a Office 365 Teams, Channel, or tab.
• Click the Action menu from the object. and Select Copy.
• Select the object (Matter/client/workspace) to copy or move the teams content to in the DMS. Currently, only objects that match the client/matter show up. In a future version, all objects will display in the lookup.
• From here, users can change the options below:
  • Users can specify a Default class to apply onto the moved teams/channels/tabs. It displays Class metadata description or Class id if description is not entered.
  • Set up a new job internal in New Interval. Set the period in Every, select the time measure (minutes, hours or days), and set the starting period date (today, in the future).
  • Add any metadata filters.
  • Select whether or not to import the chat files into the teams/channels/tabs when moving.
  • Select whether to map documents as shortcuts.
  • Select to apply the system security either from Source or Target to the moved channel/team/tab.

On clicking submit, the ETL job will be submitted to the ETL Manager and displays in the ETL Jobs tab.

ETL Jobs can be run from CSVs and uploaded to the Jobs tab in CAM.

The following CSV parameters are required for Linking Channels/Teams and Moving to the DMS:

Linking and Moving Teams:

• Profile Metadata (i.e ClientId, MatterId)
• job: LinkMsTeamsOrChannel,
• CreateInOffice365: 1,
• Office365Group: Name of the team we want to link into CAM,
• Office365Type: teams,
• Template: Id of the template.

Link and Move Channel:

• Profile Metadata (i.e ClientId, MatterId)
• job: LinkMsTeamsOrChannel,
• CreateInOffice365: 1,
• Office365Group: Name of the team that contains the channel we want to link,
• Office365Type: channel,
• Office365Channel: name of the channel we want to link into CAM,
• Template: Id of the template.

Sync Team to Folder:

• "targetEntityType" : "folder",
• "targetEntityId" : "$folderId"

Additional CSV fields for ETL that can be used:

• AutoOneWaySync: 1,
• TargetSystem: System of the target workspace.
• UniqueSystemCriteria: Unique Criteria to find the workspace (i.e clientid=asdtest&MattErId=asdtest or WorkspaceId = Worksite11!623),
• TargetServer: The server of the target workspace.

• isEnabled: Sets if enabled

• applySourceSecurity: applies source security

• createTargetUserMode : Sets how to create. 2

• defaultClass

• createrootfolder

• bringchatfiles

Example CSV for Teams ETL:

LinkTeamsETL.csv

A out of the box form for ETL is included for using ETL with the Request Workflow (Workspace Wizard) feature. The form includes:

• Form Name: ETL- Default Profile
• Entity Type: Documents
• Where to display: ETL-DMS
• Is Forced Value? Yes or No response.
• Document class
• Author
• Operator

Templates can be mapped from the iManage structures to the Microsoft Teams Channel or folder structure and vice versa.

When selecting To system as Office365 and from system in iManage, the following options appear in ETL Configuration.

• How to Handle Team:
  • Create as Tab
  • Create as folder
  • Skip
• How to Handle Channels:
  • Create as tab
  • Create or map to existing folders.

Selecting the map to existing folders icon allows in the template panel to map folder structure, tab and channels from a source template to the target template. They can be the same, different.

Now the templates can be seen and used in Template Editor.