Status Reports or custom subobject cannot be downloaded/uploaded from the grid view (attachment attribute)

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

SUMMARY OF DEFECT
Status Reports having report saved in the attachment attribute cannot be downloaded. This behavior also affecting custom subobjects with attachment type attributes. 

STEPS TO REPRODUCE
1. Navigate to MUX - Projects - Status
2. Create a Status Report and publish it
3. The published report will now be available in the Attachment attribute in the Status Report grid page
4. Create a user who has Instance/OBS based access to the above project - status report
5. Login as the user and navigate to project - Status Report created in Step 2 and 3
6. Click on the Status Report in the Attachment attribute. 
Expected: The Status Report gets saved locally and opens up
Actual: Error message pops up
        Error: Could not download the file.

Error message in the app logs: 
WARN   [http-nio-] 
(clarity:[email protected]:5XXXXX__XXXXXXXXXXX:)  
User [email protected] tried to access attachment for object cop_prj_statusrpt, but does not have permission.
ERROR  [http-] ppm.rest (clarity:[email protected]:5XXXXX__XXXXXXXXXXX:)
com.ca.ppm.rest.exception.AuthException: API-1007 : You are not authorized to process request. Contact your system administrator for necessary security rights.

Workaround 1: Grant Project - View Management - All global rights
Workaround 2: Navigate to Status Reports in the main MUX tile and download the report

Alternative STEPS TO REPRODUCE:

1. Create subobject for investment object.
2. Create attachment attribute on the subobject.
3. Modify idea blueprint to add subobject as module.
4. Create a user who has Instance/OBS based access to the above idea and Global rights to the subobject itself.
5. Navigate to MUX -> Ideas -> Subobject and create new instance of the subobject.
6. Attempt to upload file into the attachment attribute and you get an error "Could not upload attachment".

Environment

16.3.3

Cause

DE175805 

Resolution

Resolved in:

• Clarity 16.4.0
• Clarity 16.3.3 Patch 1 (16.3.3.1)