Set Override Default does not override the Default value
search cancel

Set Override Default does not override the Default value

book

Article ID: 203880

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

On Project object, we added a Default value for a field

Then we set the “Override Default” the field value from Views

However when we create a new project in Classic or Modern UX, the value of the field is still the Default Value and not the Override Default value

 

Environment

Release : Any

Component : CA PPM PROJECT MANAGEMENT

Resolution

The Override Default field in Studio will work the following way:

1. In Classic you must add it to the Create page layout to have the value overridden. This is because it's a 'view' setting, which means you have to put the field on the 'create' page for it to use the Override Default. When added to Create page it will work

2. It will not work in Modern UX as it is only for Classic views

We recommend using templates when creating projects to ensure you always have the desired value populated.

 

Additional Information

You can set different override defaults based on partitions.

If using templates, if the value is not filled in on the template, the override will not populate.