PMO Lookups are clasified as user-defined versus system-restricted.

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

PMO (Accelerator: Program Management Office) lookups are clasified as user-defined causing confusion to Administrators when updating lookups as they think these lookups are custom and can be changed but with an upgrade those changes get overwritten.

Steps to Reproduce: 

1. As Administrator login to Clarity.
2. Navigate to Administration->Data Administration->Lookups
3. Search for OBJ_PROJECT_STAKEHOLDER
4. Notice this lookup is clasified as user-defined.

Expected Results: this lookup should not be clasified as user-defined.

Actual Results: this lookup is clasified as user defined.

Environment

16.x

Resolution

DE153678, Fixed in 16.3.0.

Engineering changed to system-restricted only the dynamic lookups that are forced in upgrades. We have to force their reinstallation for several reasons so we won't remove the force option.

• OBJ_PROJECT_STAKEHOLDER

• OBJ_IDEA_BUSINESS_OWNER

• COP_PORTLET_TIMESHEET_PERIOD

• COP_PORTLET_PROGRAMS

• CSK_RESOURCE_BROWSE

• OBJ_PII_ATTRIBUTE

• CSK_RPT_ALL_DYNAMIC_LOOKUPS - these are all the dynamic lookups used in reporting that are a mirror of the Jaspersoft Input Controls.