MUX- Unable to publish status report or update an object instance's attachment attribute when there is a process which locks attributes.
search cancel

MUX- Unable to publish status report or update an object instance's attachment attribute when there is a process which locks attributes.

book

Article ID: 276902

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

After upgrading to 16.2, it's not possible to publish a status report if there is a process which starts on creation of the status report, and locks one or many attributes during the execution of process.

It is also observed in MUX when updating instances of Ideas, projects or any other object's attachment attribute where it is complaining about attachment attribute locked when it is not locked by any process. We are seeing this error message CMN-0015: Attribute 'my_attachment_attr_id' was locked and cannot be changed.

Pre-Requisites to reproduce this behavior:

  • Create a process on the object 'Status Report'
  • Set Start option to Auto Start, Start Event = Create and Start Condition = Status
  • Report Name = 'Lock'
  • On the Start Step, create a System action to lock one or many attributes on status report object

Steps to Reproduce: 

  1. Create a project in Modern UX
  2. Navigate to 'Status' module and click on Reports
  3. On the Reports Grid view, create a status report instance and ensure to have the name as 'Lock' in order to process to execute 
  4. Once the instance is created, click on the Name of the report in order to preview and then publish 

Expected Results: The status report should get published 

Actual Results: The report is not published and the error "Unable to Upload Status Report of the Project" is seen on the toaster message. In the app-ca logs below stack trace is seen:

ERROR [http-nio-8080-exec-365] ppm.rest (clarity:[email protected]:3D70-4D16-914E6A98B:PPM_REST_API)
com.ca.ppm.rest.exception.APISystemException: Unable to upload Status Report ###### to the project.
at com.ca.clarity.projmgr.rest.function.StatusReportPublisherFunctionResource.create(StatusReportPublisherFunctionResource.java:146)
...
...
Caused by: com.niku.union.odf.exception.ODFValidationException: CMN-0015: Attribute 'cop_pdf_file' was locked and cannot be changed.
at com.ca.platform.osf.object.rest.marshaller.AttachmentHandler.validateAttribute(AttachmentHandler.java:314)

Alternative steps to reproduce the issue.

1. Create attachment type attribute on idea, project or any other object and api enable it.
2. Create a simple process to lock 1 or more attributes on that object but not the attachment attribute.
3. Run the process against given instance.
4. In MUX attempt to modify attachment attribute and notice error as CMN-0015: Attribute 'my_attachment_attr_id' was locked and cannot be changed.

Expected Results: It should allow to modify attachment attribute as it is not locked by a process.

Actual Results: It is throwing an error when attempting to modify an attachment attribute.

Environment

Clarity 16.2.0

Cause

DE78753

Resolution

DE78753, Fixed in 16.2.1 as well as targeted for 16.2.0.1.

Additional Information

Workaround: Remove the locking of attribute