Upgrading to 15.6.1 From an Environment That Had the Blueprint Attribute Audited in the Project Object Will Cause System Errors

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

Upgrading from a 15.6.0 environment that had Blueprint attribute audited to 15.6.1 will cause post-upgrade issues:

• If Blueprint attribute was audited during upgrade:
  
  1. Every time the Audit Trigger runs (e.g: a save is done in a project), a "System error. Contact system administrator." will be shown.
  2. Trying to modify the Audit Trail without first disabling Blueprint as an audited attribute will display an "Error 500 - Internal Server Error. The server could not retrieve the document due to server-configuration or other technical problems. Contact your site administrator.".
  3. After disabling Blueprint, trying to enable it back will display a "Error 500 - Internal Server Error. The server could not retrieve the document due to server-configuration or other technical problems. Contact your site administrator.". After checking back the Audit Trail page, the Blueprint attribute will be shown as disabled, but the trigger will still contain the code referencing to the Blueprint attribute and the errors will still appear when saving an instance for the Project object.
• If Blueprint was not audited during upgrade, but it has been audited at any point in time before the upgrade, issues are similar, as Blueprint cannot be audited back, and once it is tried, the issues are now the same as in earlier scenario.

Steps to Reproduce

1* Use a 15.6.0 Clarity PPM environment.

2* Go to Administration > Studio > Objects > Project > Audit Trail and enable the audit for the Blueprint attribute (both Attribute Audit and Object Audit at the same time).

3* The function ODF_AUD_5001040_FCT references ODF_BLUEPRINTS.code and ODF_BLUEPRINTS.name. The trigger 'T_PROJECT_IINV_INVESTMENTS' calls this function in the Blueprint attribute code block.

4* Disable Project object audits for the Blueprint attribute.

5* Upgrade the environment to 15.6.1.

6* Check the FUNCTION ODF_AUD_5001040_FCT.

Actual Results: The same function is displayed.

Expected Results: The function is not using 'name' and 'code' from ODF_BLUEPRINTS, but these coluns are now located in ODF_ABSTRACT_BLUEPRINTS. The function is invalid and for the same reason, the trigger that references it is invalid as well.

This is true even after completely disabling all the audited attributes from Project; the function is never dropped and/or rebuilt.

In 15.6.1, the Blueprint attribute is also present in the Idea object, so the logs might show errors regarding the 'T_IDEA_IINV_INVESTMENTS', which also points to the invalid 'ODF_AUD_5001040_FCT'.

Environment

Clarity PPM 15.6.1.

Cause

This issue has been reported to Engineering as DE50771.

Resolution

This issue is currently under review by Engineering.

Workaround

From both the Idea and Project objects, remove the Blueprint attribute from the 'Audited Attributes' list AND Save. If it has been tried to enable the Blueprint audit and failed with an error 500, the Blueprint audit will be apparently disabled (Blueprint will show in the 'Available for Auditing' section), but the issue will still appear.