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:
Steps to Reproduce:
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
com.ca.ppm.rest.exception.APISystemException: Unable to upload Status Report ###### to the project.
Caused by: com.niku.union.odf.exception.ODFValidationException: CMN-0015: Attribute 'cop_pdf_file' was locked and cannot be changed.
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.
DE78753, Fixed in 16.2.1 as well as targeted for 220.127.116.11.
Workaround: Remove the locking of attribute