The Plan of Record (POR) flag is not editable on the Cost Plan properties.

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

STEPS TO REPRODUCE:
1. Create a project
2. Enable the project financially:
   Project Properties > Settings > Add the financial Department and Location
3. Go to the Financial Plans tab > Cost Plans
4. Create a New Manual Plan CP1 and click Save
5. On the Cost Plan properties tab, notice that the Plan of Record checkbox is enabled and greyed out.
   This is expected as the ONLY cost plan of the project must be Plan Of Record (POR)
6. Create a second cost plan CP2 and click save
7. On the properties tab, the Plan Of Record flag is editable and can be checked or unchecked. Leve it unchecked
   This is as expected. When multiple plans exist, you can switch the POR flag form one to another.
8. Go to Studio > Objects > Cost Plan object > Views > Cost Plan Properties > Fields
9. Edit the Properties of the Plan of record field and uncheck the Default flag
10. Go to the project financial plans tab and open the CP2 financial plan that is not set as POR

Expected Results: To be able to mark the cost plan as POR
Actual results: The POR flag is read-only and can not be modified

Environment

Any Clarity PPM release

Cause

This is caused by DE56114

Resolution

This has been analyzed by Engineering and Product Management and determined this is not a bug.

The functionality is designed to use the button to mark the Plan of Record. 

In the past we had a defect logged CLRT-72446 in which the fix was to prevent users from doing the inline editing of the 'Plan of Record' field. 

Even in the Modern UX, on the FINANCIALS Module, if you add the 'Plan of Record' field to the columns the field is NOT editable.

When this was allowed to be edited it caused issues because it allowed multiple Cost Plans to have the 'POR' flag set. 

On the Financial Plans - Cost Plans list view, select the cost plan you want to set as POR and through the Actions menu, call the Set as Plan of Record action

Additional Information

1. Reset the Default flag we unchecked on step 9
2. Restored the object to defaults
3. Cleared cache
Still the field is read-only