You are viewing an old version of this content. View the current version.
Compare with Current
View Version History
« Previous
Version 3
Next »
The ETL (Extract Transform Load) Manager feature is designed so that users can move Teams and Channels to the DMS system from Teams and to automatically sync any changes between Teams and the DMS system.
Major features include:
Two add-ons that control ETL Manager.
Moving channels, tabs and teams from the Teams application to the DMS system from the Matters tab.
Copying channels, tabs and teams from the Teams application to the DMS system from the Matters tab.
Setting up ETL jobs between systems to occur on a schedule.
Allowing CSV Upload of Jobs to move channels, tabs or teams from the Teams application to the DMS.
License and Add-on Requirements
License and Add-on Requirements
OR
Two add-ons are included with the license:
Once the permissions are granted, users can go to the ETL Manager to configure ETL jobs.
Configuring an ETL Job
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 |
Adding a new Mapping
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. |
The mapping now is setup and displays in the Default Settings tab.