MUX - Notification link not working for custom subobject with investment object as parent.
search cancel

MUX - Notification link not working for custom subobject with investment object as parent.

book

Article ID: 276346

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

Notifications have been created and work as expected for Risks, Issues, and To Dos on a Project but, after creating a similar Notification for the custom sub-object based on investment object as parent, the notification doesn't link properly to that subobject instance and throws errors.

Steps to Reproduce: 

1. Create subobject based on Investment as parent.
2. Create an Owner attribute as type of lookup based on "Browse for resources" lookup and API enable it.
3. Navigate to MUX->Administration create a simple Notification on the change of Owner field created in Step 2 above.
4. Navigate to MUX->Administration and go to Blueprints
5. Modify project blueprint to add subobject created in the Step 1 above to the modules and Publish.
6. Navigate to MUX->Projects and update project blueprint to the one changed in the above step 5.
7. Go to project properties and click on Subobject module.
8. Attempt to change the Owner field and wait for notification show up in the Bell icon.
9. Click on the noficiation under Bell icon and click on the instance link, notice error "API-1003 : Could not find resource investments."

Expected Results: It should allow user to go to subobject instance from notification link.

Actual Results: it throws an error when clicking on notification link.

Resolution

DE78597, Fixed in 16.2.1.