Users without global Idea Edit rights are unable to create Ideas from template

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

Users without global Idea Edit rights are unable to create an idea from a template if the template has resources assigned
The attempt to create Idea instance from Template fails with the following error message in the Modern UX 
"PRJ-10007: You do not have the rights to add team members to this investment."
This error occurs if the user has no Resource Hard / Soft Book - All access right.

When "Resource Hard / Soft Book - All" access rights are granted to the resource then the following error occurs: 
"API-1019 : Could not process the request due to internal error".

Steps To Reproduce:

1. In Clarity Classic, assign the following Global Access Rights to a resource 'A':

•  Agreement - Navigate
• Classic PPM - Navigate
• Custom Investment - Navigate
• Idea - Risk, Issue, Change Request - Create
• Idea - Risk, Issue, Change Request - View - All
• Idea Management - Navigate
• Ideas - Create from Template
• My Workspace - Navigate
• Page - Navigate
• Project Management - Navigate
• Resource Management - Navigate
• Roadmap - Navigate
• Staffing - Navigate
• Tasks - Navigate
• Timesheets - Navigate
• To Do - Navigate
• Resource - Hard Book - All
• Resource - Soft Book - All

2. Using a Clarity Admin account, create a new Idea Template in the Modern UX.
    Add resource 'A' as Manager (Idea -> Properties)

3. Add labor resources to the Idea Template in the Staff module. 

4. Log in as user 'A' (created in step 1) and perform the following steps in Modern UX:

• Navigate to: Ideas -> New from Template
• Select the template created by the admin
• Click "Next"
• Enter a Subject name
• Select Start and Finish dates
• Enter an Idea ID
• Click "Create"

Expected: A new Idea instance gets created

Actual: Error message: "PRJ-10007: You do not have the rights to add team members to this investment."

Environment

Clarity 16.3.1, 16.3.2, 16.3.3

Cause

DE174454

Resolution

This is fixed in:

• Clarity 16.3.3.2 (16.3.3 Patch 2)
• Clarity 16.4.0