CAM Limitations

CAM has the following limitations:

Administration

• The js API has a default limit per request of 5MB. Depending on the size of the source system data being fetched, an error screen could be triggered while on the Administration tab.

Open

Content Mover

• Content Mover Jobs may fail if using the ssl=true setting for Azure jobs only.

• Content Mover does not currently support NetDocuments when moving content from a DMS to Teams.

• Two-way syncing is not supported via CSV in Content Mover.

  • Use the Directory tab-> Copy action.

• Replace Shortcut functionality is currently only supported for iManage. If the target is other than iManage, the Replace Shortcut Action will be hidden.

Controls Center

• When an Exclusion Control for Office365 adds a user that has no email address, no user is removed from the team and the user does not have access to any Office365 apps.

Dashboards

• The limit of the S3 object filename (e.g. dashboard, widget, report) is 1024 characters.

• The S3 file size is limited to 160GB.

• The S3 bucket name is limited to 36 characters.

Data Uploader

• CAM supports only 254 characters in the group names when added to the group path. Same goes for the CSV.

• The OU and container information will be synced in only one CSV to bring overall user and group information together. In the future, the CSVs may be separated.

• A limit on the number of jobs a tenant can submit in Data Uploader now applies. The limit is 50,000 jobs. An error will warn the user of the limit, and any new DU jobs will not be submitted for processing until the batch completes. This eliminates newer jobs continuously filling the queue or causing timeouts on the current original job. Note that one job is submitted for the Data Uploader job per script.

• Data Uploader CSVs must contain a maximum of 100 rows. When more than 100 rows exist issues may result like imports taking much longer than necessary.

• Data Uploader’s EntraId support does not support MTO!

FileShare

• If the Event is not working, a timer will check and upload the CSV every 10 minutes. Eventually, the timer will not be needed as support is built into the event tracker.

• Security is not applied with NTFS for NetApps currently. This feature isn’t present currently.

• Creating a new folder with the Create Folder option from a template from a Fileshare with security applied is currently hidden and unavailable.

General AWS Limitations

DynamoDB

10+ levels of subfolders will cause DynamoDB to exceed its' maximum size.

General Provisioning

• Removing values and passing nulls are not supported for provisioning jobs (e.g. create workspace or modify workspace)

iManage

• The iManage API doesn’t support passing docserver as the server metadata for jobs. Please see Create or Edit or Delete/Disable Users/Groups | iManage Specific

• Metadata filtering is not supported using the API search by the iManage API in the Documents or Workspaces tab with API Search turned on.

• IManage’s API doesn’t support searching by workspace_name which causes the user not to be able to use it to search in the Documents or Workspaces tabs.

• In SPM, CAM cannot create an open matter under a restricted client. It is an iManage issue/limitation with the iManage API. Thus any Create/Update Policy job will fail with: Number of Policies not Updated.

• iManage has an issue where updating a folder will result in the edit date being modified on all other folders and subfolders on the workspace that folder was on. Please see the iManage known issue here: https://help.imanage.com/hc/en-us/articles/6284502437531-NT-126206-Edit-Date-value-is-updated-on-all-folders-and-subfolders-in-a-workspace-when-creating-a-new-folder?input_string=update+parent+folder+properties+also+update+edit+date+on+child+folder

• iManage on-prem throws an error if my matters is added for a user that has never logged into iManage beforehand! See note on iManage MyMatters

Jobs

Secondary authentication for bulk (25+ documents) jobs from the Workspaces tab or Analytics is not fully implemented and will be fixed in an upcoming Hotfix.

Link Workspaces

• The link workspaces display shows a max of 5 fields in the result grid.

Logging

• Audit Logs from Microsoft have an API latency of 50+ minutes for that information to attach after the job executes.

• NetDocuments only supports displaying a single audit record at a time and will be ordered in the order the target log entry is modified or created.

• Currently, iManage does not support activity time.

M365 Provisioning

Planner

• Only 250 tasks in the Not Started and In-Progress states are assigned to the user. This is a Microsoft limitation.

• Users are restricted to creating only 1500 tasks using the service account. This is a Microsoft limitation.

General Provisioning

• Secondary authentication for Export to CSV for bulk (25+ documents) is not enabled and is by design.

• There currently is a limitation on the maximum number of Users that can be added in a single CSV job. It is recommended to limit the number of Users to add to 500 per job.

• The file size should be 450MB or less from M365 to NetDocuments in Azure and AWS to sync the contents.

Tabs

• If you are creating a website tab for iManage or NetDocuments or any other website link, Microsoft will no longer load the site on the channel. It will show a button to open up the browser to the page. Read about this from Microsoft here: https://devblogs.microsoft.com/microsoft365dev/upcoming-updates-to-loading-websites-in-teams-tabs/

Metadata

• Mapping on a search folder is not permitted.

• Mapping between a channel and a Tab is not permitted.

Navigation

• When running actions on the Documents/Workspaces/Analytics tabs, you cannot navigate away from the tab after queuing the job. It must complete first successfully or fail. This is iFrame behavior.

NetDocuments

• NetDocuments doesn’t support the name of a tab to contain one of the following special characters: /:*?"<>|

• NetDocuments does not support the following special characters: Tab, Non-breaking space, \, /, :, ?, *, ", <, >, and |. It replaces these symbols with spaces.

Service Desk

• Move Document/Folder operation is applicable only for iManage and NetDocuments.

• There is a limit of 5,000 documents that can be moved at a time with Service Desk. See the note below.

Template Editor

• CAM no longer allows you to create metadata values directly in the Template Editor

• The Metadata Scenarios with Multiple Servers and Regions are applicable only for iManage, NetDocuments, and M365.

• Users can import up to 10 levels of subfolders. Also, subsites will be hidden from the advanced mapping for the Content Mover window of Template Editor as they are not supported.

• CAM matches Microsoft in that planners cannot be added onto private channels. Microsoft has a limitation.

Request Workflow

If the Rule format from Copy As is removed after saving, CAM will again pick the Rule format "@system@_@clientId@-@matterId@".

Source System Integration

• When importing data into a Source system with the Azure API, sensitive information can't be copied over due to security reasons. Hence, it is not possible to autofill any data for authentication as it contains sensitive data regarding office365 or any system's client id, and secret id.

• There is a pagination limitation with the Simple Legal DMS. There currently is no way to find the limit for any system as it is based on multiple parameters such as the time taken by the API to provide a response, the number of concurrent calls that need to be made, if it is a system requiring a second API call, how much data is gotten in a single call, etc.

  Usually, systems working on single API calls like Azure can complete more than 10k, while systems like Simple Legal, which uses a couple of API calls, will struggle with 2k or 3k, based on the page size of calls.

• A limit on the number of jobs a tenant can submit in Source System Integration now applies. The limit is 50,000 jobs. An error will warn the user on the limit, and any new Source system jobs will not be submitted for processing until the batch completes. This eliminates newer jobs continuously filling the queue or causing timeouts on the current original job.

• Aderant Expert Sierra: Since Expert Sierra is on AWS and Aderant exposes the Database, the recommended way to connect to Sierra via SSI is to leverage Aderant Cloud’s sync to an on-premises SQL database, and then use that as a source to CAM.