OWB: Unable to open project XXXX. An exception occurred: java.lang.NullPointerException

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

There is an Open Workbench (OWB) Schedulers Connect issue when the Clarity application default setting is set to export current baseline only. If you have more then one baseline, and you remove all resources from all tasks, upon save back to the CA PPM application, the assignment baseline information is deleted for the current baseline, and not the non-current baselines.

Steps to Reproduce:

1. Login to the application as an administrator user
2. Navigate to Administration, Project Management: Settings
3. Check the box for the 'Export Current Baseline Only' option
4. Create a project
5. Add a resource
6. Create a task
7. Assign resource to task with etc
8. Create three baselines
9. Open project in OWB
10. Release resource from task
11. Save back to CA PPM application  
12. In Clarity change the default baseline from 3 to 2
13. Open project in OWB

Expected Result: The project to open without error

Actual Result: You get "Unable to open project XXXX. An exception occurred: java.lang.NullPointerException". This issue is caused when OWB/Schedulers save, all the assignment baseline records are not deleted. Only the assignment baseline records for the current baseline is deleted.

 

Resolution

WORKAROUND:

Do not save a project back to Clarity after removing all assignments from all tasks.

Instead, make sure you have at least one assignment remaining on the project.

If you already have the problem, make an assignment within Clarity

After an assignment is made you can then open the project in OWB without getting an error.