Versions Compared

Version Old Version 54 New Version Current
Changes made by

Eric Schullek

Eric Schullek

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

What Source systems does

...

The Source System Integration functionality allows CAM to integrate with any cloud-based system or system with a web service/REST API as an input to the provisioning process.CAM supports integration with iManage, Azure AD and APIGEE-based systems.as an input to the provisioning process.

CAM supports integration with iManage, Azure AD and APIGEE-based systems.

Source System Panel in CAM

Here’s what Source Systems looks like:

image-20250130-183240.pngImage Added

The table displays the following:

  • System

  • System Method

  • Authentication Type

  • Description

  • Base URL

  • Created By

  • Last Updated At

  • Actions

Filtering is possible in this panel.

The following filters can be used:

  • System Name (Text Search)

  • System Method (Dropdown)

  • Authentication type (Dropdown)

  • Description (Text Search)

  • Base URL (String Search)

  • Last Updated By (Dropdown)

  • Last Updated At (Sorts either ascending or descending)

Source System Limit

Note

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.

Please Consider: If you have a large number of jobs that you need to run, you could start all jobs at the same time and let Source System Integration work through the backlog. However, this results in poor performance and even failure if the number of jobs is too high. The first few jobs are put into the Running state and the remaining jobs are put into the Queued state. This could make a lot of jobs fail even when they aren’t running and that can negatively impact the other jobs that are running.

Please work with your partner or professional services consultant to discuss best practices of managing and queueing jobs to that limit.

...

Configuring A New Source System

...

Permission Mapping

Set permission based on CAM Roles. Common CAM roles are following:

  • Admin - System administrators responsible for CAM User Management and Workspace Management

    For e.g. An user added as: alexey.marcus@prosperoware.com|true#23/12/2019*Admin$true

  • Editor - CAM users with Edit permissions to access CAM Workspace Management

    For e.g. An user added as: alexey.marcus@prosperoware.com|true#23/12/2019*Editor$true

  • Watcher - CAM users with Read permissions only to access CAM Workspace Management

    For e.g. An user added as: alexey.marcus@prosperoware.com|true#23/12/2019*Watcher$true

  • Deny: CAM users with the Deny rights gives no access to the object. For e.g. An user added as: alexey.marcus@prosperoware.com|true#23/12/2019*Deny$true

Examples are as follows:

 Users:

Adding an Admin ( iManage Full Access) bob.bradely@demofirm.com|true#23/12/2019*Admin$true

Adding an Editor (iManage Read/Write access)

firstnamelastname2@firmname.com|true#null*Editor$true

Adding a Watcher (iManage Read only)

firstnamelastname3@firmname.com|true#null*Watcher$true

Denying Access (iManage No Access)

firstnamelastname4@firmname.com|false#null*Deny$true

Groups:

For example, adding an editor group

PartnersGroup|true#11/3/2021*Editor$true

 

Info

Note: Dates are based on your system setting found here: Admin->Settings.

  •  If multiple entries are included in this column, separate each entry by a comma.

  • firstnamelastname@firmname.com|true#null*Admin$false,Group4|false#null*Deny$true

 Click on the hyperlink of the CAM Role to show the CAM permissions available for the role.

Info

The permissions for these roles can only be edited after the server information has been saved. If the server details have not been saved, the Edit button will be grayed out. If hovered over, a tooltip will warn users about this.

Click on each type of Security Role to update their respective permissions.

Read

This allows access to only view documents, properties /metadata etc

Read Write

This allows full access to the document (view and edit), but limited control on properties /meta-data and no ability to change security (including for the folder, workspace etc)

Full Access

This allows full access to the document (view/edit/share) and full control over properties /meta-data and also the security (including for the folder, workspace etc)

...