OWB open error "Operation denied: AvailCurve cannot be set to null" when one or more users on a team are allocated at 0%

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

When trying to open a project in Open Workbench (OWB), getting error: Unable to open project  <ID>. Operation denied: AvailCurve cannot be set to null if the project has any teams on it and their allocation / availability is 0. 

STEPS TO REPRODUCE: 

1. In the Modern User Experience (UX), go to Resources
2. Create a new team
3. Add one or more resources to the team (all allocated at 0%)
4. Create a new project
5. Add the team to the project
6. Open the project in Open Workbench (OWB)

Expected Results: Project opens successfully

Actual Results: Receive error: Unable to open project <project ID>. Operation denied: AvailCurve cannot be set to null

Environment

Release : 15.9.2 and higher

Component : CLARITY OPEN WORKBENCH (OWB)

Cause

This is caused by DE62017

Resolution

No changes to the code are planned at this time.

Workaround: Ensure that at least one resource in each team has an allocation of greater than 0%

1. In the Modern User Experience (UX), go to Resources
2. Go to the team
3. Ensure at least one resource on the team is allocated at 0%

Additional Information

See also: OWB open error: "Operation denied: AvailCurve cannot be set to null"