Release Notes CAM R23.07.30 23.Q3 (Major)

New Features

Issue Id	Description
CAM Commands
Cloud-14395/CAMHD-1533	The Create Workspace CAM Command now can support Site and Teams creations natively. This allows iManage based firms which use the command to surface the creation of sharepoint sites and MS Teams in front of the users.
Request Workflow
Cloud-7403	When using the Request Workflow to create a Team, it is now possible to use the unique matter IDs, and the system will prefill the client field based on the matter selected. This is useful when the end-user does not know the Client ID but knows the Matter ID tied to it.
Cloud-9854 / Cloud-15098/ Cloud-15099 / Cloud-15100	Improved Exclusion and Inclusion security controls so that job data gets validated, once submitted, to block any type of security bypass or injection. For example, If a user is included for client, matter, and client-matter, then in the lookup that client-matter will only show for that included user, and if any other user tries to add that client-matter manually, then while submitting the job, it will show a validation error.
Cloud-12940	If a deleted or disabled user in CAM cannot be removed from the system, Request Workflow and the Users tab will show that the user is disabled/deleted.
Cloud-13275 / CAMHD-1257	When creating a new dialog for Create Team, CAM will auto generate the mandatory metadata that are required for all Create Team actions, for example Office365Type with default value as teams Office365 Group Name with display label as Team name mailnickname with display label as Mail alias
Cloud-13296	A new Grant Access workflow set is created out of the box to allow users to grant access to sharepoint sites.
Cloud-13976	Two permissions are added to remove access: One to remove access to Teams, one to remove access from the CAM application.
Cloud-13977 / Cloud-13979 / Cloud-8899	Improved functionality when using the Request Workflow wizard to Remove Access or display that user in dropdowns: The "Office365TeamIdCollection" metadata allows for Only teams where the logged in user is a member show up in that user’s lookups. A check has been added so that if the user is in the CAM Admin role, they can see all Teams. This will allow CAM Admins to remove users from Teams where they are not members. The wizard will present the list of team members in the Security panel, based on the team selected from the drop-down list, whether the user is an external user or not. A request can go for approval to designated approvers if that is configured in the workflow, or simply submit the job into CAM if the user does not require approval. There is an option to Add/Remove users with admin roles as: Yes/No If the users are accidentally removed, then you can add them back to the team Note: Keep the following in mind: You will not be able to remove all admin users: at least 1 admin user is required in the team. When you try to remove the last admin member from the list, a notification will be shown: "The Team must have at least one user with an Admin role. Please add at least one Admin user back to the Team." Token Users are automatically populated on the member list and cannot be removed.
Cloud-13981	The Security portion of Request Workflow now has a toggle to automatically put Project Team members into the security, otherwise continue manually adding users or using the Default Security. This allows for an easier, faster method to input team members.
Cloud-13982	Validations are added into the Project Teams Request Workflows that appear when a user goes to the previous page to finish completing information or changes information.
Cloud-13994 / CAMHD-1453	Expand Arrows next to the Template Preview categories will no longer show when there are no sub-items.
Cloud-14156	The layout for Security in Request Workflow now displays information in a table, paginates the table results and allows for multiple selection, edits and deletions.
Cloud-14392	Minor improvements have been made to Private Channel’s workflows in the Security panel including the ability to edit Roles, removing unnecessary counts and cleanup of spacing.
Cloud-14538 / Cloud-14945	The Approvals tab UI has been enhanced to show three additional columns: Status. It can be one of the following: Approved Rejected Waiting for Approval In Process. If a request goes to a group including multiple members/users, and one of those users has opened the request to approve/reject it, then the status will show In Process to other members of the same group (instead of showing Waiting for Approval). Additionally the other users will not able to approve or reject the request. Approver. The name of the user who approved/rejected the request. Comment. The reasons behind the approval or rejection of the request.
Cloud-14868	It is now possible to configure the Approval report export in any of the following ways: Selecting all fields: Requested by/Action Type/Status/Client/Matter Selecting only one of the available fields: Requested by/Action Type/Status/Client/Matter Selecting a combination of fields: Requested by + Action Type/Status/Client/Matter Action Type + Requested by/Status/Client/Matter Status + Requested by/Action Type/Client/Matter Client/Matter + Requested by/Action Type/Status Additionally, it is possible to select multiple values in the drop-down of Requested by/Action Type. Note: For the Status field, it is only possible to select one value at a time.
Cloud-15787	Users with the Admin role can export an Approvals report from the Approvals tab containing all the requests based on the filter, irrespective of who requested or approved the request(s). Users without an Admin role can also export an Approvals report from the Approvals tab, but this report will only include the requests based on the filter and will be dependent on Requested by and Approved by on that page for the logged-in user only.
Cloud-15789	The Approval Export window has an improved display to clearly display the user and email for the Requestor and Approver.
Source Systems
Cloud-15399	To avoid strain and potential concurrency issues during the upload process, API support has been enabled in Source System Integration to allow submitting JSON files directly in the queue.
Cloud-15400/ Cloud-13001/ CAMHD-1181	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.
Template Editor
Cloud-12221	When clicking Add new Metadata, a note displays with the correct format and example to input the metadata value as.
Cloud-12939/ Cloud-9532/ CAMHD-1135	Template Editor workflows for Private Channel security supports adding users with a username lookup to make it easier for users to be added without knowing the id.

Fixed Issues

Issue Id	Description
Request Workflow
Cloud-12174	The default metadata value of AddtoMyMatters is not getting passed from the Create Workspace Wizard if CategoryId is also present as auto-populated metadata as the Category will be used instead of the AddtoMyMatters.
Cloud-14122	If Users exist in Project Team and Request Workflow Security, the duplicate users will have the same roles passed as per the mapped security.
Cloud-16266 / Cloud-11774 CAMHD-590 / DDP-324	Create Workspace Jobs submitted via Request Workflow no longer fail or duplicate items due to inconsistent case-sensitive naming. Tip: We recommend firms to set a high enough Matter Range when working with Workspaces/matters with identical ID values to avoid the system duplicating or repeating matter ranges, if the range is exceeded.
SPM
Cloud-13714	SPM Policies and other controls can be mapped and secured using other sets of exclusionary metadata than just Client-Matter Numbers, such as FileNumber or ClientNumber.