Meridio Source

Proventeq Migration Accelerator allows you to discover items based on the criterion given in the discovery filter.

•  Dynamic Filter

PMA allows to filter out documents and folders based on a variety of criteria like Container[ObjectType:0] & Items[ObjectType:1].

So, to discover folders and documents, you need to provide filter string as explained below:

Filter Type	Filter String
Container with DocID	[{"ObjectType":0,"Filter":"KContainer.CategoryID=<CategoryID>"}]
File Name with DocID	[{"ObjectType":1,"Filter":"D.DocID=<DocID>"}]
File Name by CategoryID	[{"ObjectType":1,"Filter":"D.CategoryID=<CategoryID>"}]
Container and File Name	[{"ObjectType":0,"Filter":"KContainer.CategoryID=<CategoryID>"}, {"ObjectType":1,"Filter":"D.CategoryID=<CategoryID>"}]

 

The <CategoryID> and <DocID> should be replaced with the Category ID and Document ID as mentioned in above query.

 

• Version Processing

PMA supports version filtering by retrieving the latest top N versions from source system to limit the versions that are migrated to the target system.

Please note that Version Processing is not applicable for Meridio to SharePoint on Premise or Office365 Migration.

 

•  Security

To discover the document, folder and site level security, you need to select the Discover Security Information checkbox under Security heading.  This ensures all the security information of the source system is captured.

 

File Shares Source

Proventeq Migration Accelerator allows you to discover items based on the criterion given in the discovery filter.

Please note that Dynamic Filtering and Version Processing settings are not applicable for File Shares to SharePoint/Office365 Migration.

Discover Security

To discover the document and folder level security, users need to select the Discover
Security Information checkbox under Security heading. This ensure all the security
information of source system is captured.

 

Oracle UCM Source

Proventeq Migration Accelerator allows you to discover items based on the criterion given in the discovery filter for Unplaced documents only.

 

• Discovery settings

 

• Version Processing

PMA supports version filtering by retrieving the latest top N versions from source system to limit the versions that are migrated to the target system.

If you wish to discover only the latest top N versions, you just need to put the value in text box as shown below.

For example, if Last N versions value is 4, then only the latest 4 versions of documents will be discovered and migrated.

 

Documentum Source

Proventeq Migration Accelerator allows you to discover items based on the criteria given in the discovery filter.

• Discovery Setting

• Discovery Filter

Use the below discovery filter options to filter out cabinets, documents or folders while performing discovery. There are two types of discovery filter options supported:

• REST Service based Filter
• DQL Query based Filter

 

•  REST Service Filter

REST service filter can be used to discover the folders or documents by iterating through give cabinets and folders hierarchy structure. So, it will discover the filtered documents or folders along with cabinet or folder structure.

Filter Format: [{"FilterType":"REST","ObjectType":<ObjectType>,"Filter":"<Filter Criteria>"}]

Object Types:

The following Object Types are supported (User numeric values):

• RootFolder = 2
• SubFolder=3
• Item = 4

Filter:

The following functions are supported in REST:

• contains
• starts-with
• between

Examples:

• Filter Criteria template for RootFolder with Contains function:

The contains function checks whether or not a property contains a specified value in the filter Criteria.

[{"FilterType":"REST","ObjectType":2,"Filter":"contains(object_name, 'Di') or contains(object_name, 'A')"}]

By using this filter expression, the request only returns objects whose object_name contains A.

• Filter Criteria template for Items with starts-with function:

The starts-with function checks the starting string of a property.

[{"FilterType":"REST","ObjectType":4,"Filter":"starts-with(object_name, 'D')"}]

By using this filter expression, the request only returns objects whose object_name starts with D.

• Filter Criteria template for Items with between function:

The between function checks whether or not the value of a property lies between a specified range. Check the format of the date provided in the filter.

[{"FilterType":"REST","ObjectType":4,"Filter":"between(r_modify_date, date('<date1>'), date('<date2>'))"}]

Eg:

[{"FilterType":"REST","ObjectType":4,"Filter":"between(r_modify_date, date('2014-03-02'), date('2017-09-10'))"}]

By using this filter expression, the request only returns objects whose r_modify_date is in between 2014-03-02 and no later than 2017-09-10.

•  DQL Query Filter

The DQL filter can be used to filter the documents across public and private cabinets or in a particular cabinet/folder in a flat structure i.e. without iterating through cabinets/folders structure. So, the discovery result will discover only filtered documents (similar to Documentum Search) without any cabinet or folder and its hierarchy/structure.

Filter Format: [{"FilterType":"DQL","ObjectType":"<ObjectType>","Filter":"<Condition1> AND (<Condition2> OR <Condition3>)"}]

 

Here, the Filter Type will be as DQL, Object Type is the content or object type in the Documentum and Filter will be suitable DQL filter to discover specific set of documents.

• Filter Criteria template for Items within specific Public/User Cabinet:

This filter will bring all the files under respective public/user cabinet id.

 [{"FilterType":"DQL","ObjectType":"dm_document","Filter":"i_cabinet_id = '<Cabinet_ID>'"}]

• Filter Criteria template for specific document and its versions:

This filter will bring given document id with all the versions.

[{"FilterType":"DQL","ObjectType":"dm_document","Filter":"i_chronicle_id ='<Chronicle_ID>'"}]

• Filter Criteria template for Items between dates:

This filter will bring all the files creation date and modified date in between Date1 and Date2.

[{"FilterType":"DQL","ObjectType":"dm_document","Filter":"<Creation Date> > date('<date1>') and <Creation Date> < date('<date2>')"}]

[{"FilterType":"DQL","ObjectType":"dm_document","Filter":"<Modified Date> > date('<date1>') and <Modified Date> < date('<date2>')"}]

• Filter Criteria template for specific document name:

This filter will bring the files with specific File Name.

[{"FilterType":"DQL","ObjectType":"dm_document","Filter":"object_name ='<File Name>'"}]

• Filter Criteria template for Items containing repeatable attribute values:

This filter will bring the files with repeating attributes like tags having <Tag1> and <Tag2> values.

[{"FilterType":"DQL","ObjectType":"dm_document","Filter":"any <Repeating_Attribute> IN ('<Tag1>','<Tag2>') "}]

Eg:

[{"FilterType":"DQL","ObjectType":"dm_document","Filter":"any keywords IN ('KeywordA','KeywordB') "}]

• Filter Criteria template for Items containing given name:

This filter will bring the files and its versions where <attribute> starts with <FileName>, ends with <FileName> and contains <FileName> respective to the Percentage(%) symbol specified.

1. This will bring <FileName> starts with given name.

[{"FilterType":"DQL","ObjectType":"dm_document","Filter":"<attribute>  like '<FileName>%' "}]

1. This will bring <FileName> ends with give name.

[{"FilterType":"DQL","ObjectType":"dm_document","Filter":"<attribute>  like '%<FileName>'"}]

1. This will bring <FileName> containing given name.

[{"FilterType":"DQL","ObjectType":"dm_document","Filter":"<attribute>  like '%<FileName>%'"}]

•  Version Processing

PMA supports version filtering by retrieving the latest top N versions from the source system to limit the versions that are migrated to the target system.

If you wish to discover only the latest top N versions, you just need to put the value in text box as shown below.

For example, if the Last N versions value is 4, then only the latest 4 versions of documents will be discovered and migrated.

Note: As SharePoint Online does not supports branched versions (like 4.1.1.0), so Documentum branched versions will fail in package processing. To process these failures, one need to reprocess them without the Package Processing option by removing the “Enable Package Processing” option in the General Settings tab as shown below.

Also, make sure the application setting shown below is enabled to process the branched versions after disabling the package processing.

<add key="SharePoint.ProcessMinorVersions" value="True" />

•  Discover Security

To discover the document and folder level security, you need to select the Discover Security Information checkbox under Security heading.  This ensures all the security information of the source system is captured.

 

HummingBird Source

Proventeq Migration Accelerator allows you to discover items based on the criteria given in the discovery filter.

Please note that Version Processing setting not applicable for Hummingbird to SharePoint/Office365 Migration.

 

•   Dynamic Filter

You can filter out documents and folders based on a variety of criteria like Matter, SubMatter, DOCNUMBER, etc.

So, to discover specific documents and folders, you need to provide the SQL clause filter string like below:

Dynamic Filter	Filter Description
DP.E_DIVPROJ =’<FolderID>’	This filter will get folders and documents of respective folder ID.
DP.E_DIVPROJ IN (<FolderID>,<DocumentID>)	This filter will get folders and documents of respective folder ID and particular Document ID.
DP.CREATION_DATE BETWEEN ‘<Date1>' AND '<Date2>'	This filter will get the documents created between the Date1 and Date2.
DP.CREATION_DATE > '<Date>'	This filter will get the documents created from the given date.

• Security

To discover the document and folder level security, user need to select the Discover Security Information checkbox under Security heading.  This ensures all the security information of the source system is captured.

 

 

 

WorkSite Source

Proventeq Migration Accelerator allows you to discover item based on the criteria given in the discovery filter.

• Dynamic Filter

PMA allows to filter out documents and folders based on a variety of criteria like Root Container, Container & Items.

So, to discover specific workspace, documents and folders, you need to provide the SQL clause filter string as explained below:

Filter Type	Explanation	Filter String
Figure 1 - Root Container (Workspace)	Figure 2 - To filter particular workspace	{"RootContainer" : "Root.PRJ_NAME ='<Workspace Name>'"}
	Figure 3 - To filter multiple workspaces	{"RootContainer" : "Root.PRJ_NAME in ('<Workspace Name>', '<Workspace Name2>')"}
Figure 4 - Container	Figure 5 - To filter specific folder.	{"RootContainer" : "Root.PRJ_NAME ='<Workspace Name>'","Container" : "(Container.ItemName = '<Folder Name>' AND Container.EntityType ='Folder')"}
Figure 6 - Item	Figure 7 - To filter specific item inside the specific folder.	{"RootContainer" : "Root.PRJ_NAME ='<Workspace Name>'","Container" : "(Container.ItemName = '<Folder Name>' AND Container.EntityType ='Folder')","Item" : "Item.DocName = '<Document Name>'"}

The <Workspace Name>, <Folder Name> and <Document Name> should be replaced with the respective names as mentioned in the above query.

 

 

•   Version Processing

PMA supports version filtering by retrieving the latest top N versions from the source system to limit the versions that are migrated to the target system.

If you wish to discover only the latest top N versions, you just need to put the value in text box as shown below.

Please note that Version Processing not applicable for Worksite to SharePoint on Premise or Office365 Migration.

 

•  Security

To discover the document and folder level security, user need to select the Discover Security Information checkbox under Security heading.  This ensures all the security information of source system is captured.

 

 

FileNet API Source

Proventeq Migration Accelerator allows you to discover items based on the criteria given in the discovery filter.

• Discovery Settings

Please note that Dynamic Filter discovery is not supported for FileNet Discovery.

• Version Processing

Please note that Version Processing is not applicable for FileNet Discovery.

•  Security

To discover the document, folder and site level security, you need to select the Discover Security Information checkbox under Security heading.  This ensures all the security information of the source system is captured.

 

Exchange Source

 

Please note that Dynamic Filter discovery is not supported for Exchange source system.

• Version Processing

Please note that Version Processing is not supported for Exchange source system.

•  Security

To discover the document and folder level security, you need to select the Discover Security Information checkbox under Security heading.  This ensures all the security information of the source system is captured. Exchange only supports folder level security.

• Security Settings