MUX Action item links for sub-sub-objects does not contain a hyperlink to the object instance

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

MUX Action item links for sub-sub-objects to facilitate user redirection is not proper

STEPS TO REPRODUCE: 

1. Administration > Studio > Objects > Create a master object called Master
      API enable it, provide an Investment Extension and make it Event enabled
2. Administration > Studio > Objects > Create a child object to Master called: master_child
      API enable it and make it Event enabled
3. Administration > Studio > Objects > Create a child object to master_child called: master_granchild
      API enable it and make it Event enabled
4. Administration > Data Administration > Processes > Create a process called: master_child process
      Add Primary object: master_child
      Add Linked Object: Parent
      Start Options: Auto-start on create
      Start Step: Create an action item with action: Approved and Rejected
      Action Item Description add variables of master_child object: Name and Parent
      Assignee: The user you are logged in with
      Post Condition: If action item Approved > Then Go to Finish
      Validate and activate the process
5. In MUX > Administration > Blueprints > Make a copy of the Master object blueprint
6. Modules > Add the master_child subobject and Enable Properties Navigation
7. In MUX > Go to Investments > Master object
8. Create a Master object instance and associate it to the blueprint we created
9. On the master_child suboject module create a sub-object instance
10. Go to MUX > My Workspace > Action Items
11. There is an Open Action item generated by the process with a link to the master_child object instance
12. Administration > Data Administration > Processes > Create a process called: master_granchild process
        Add Primary object: master_granchild
        Add Linked Object: Parent (master_child)
        Add Linked Object: Parent (Master)
        Start Options: Auto-start on create
        Start Step: Create an action item with action: Approved and Rejected
        Action Item Description add variables of master_granchild object: Name and Parent
        Assignee: The user you are logged in with
        Post Condition: If action item Approved > Then Go to Finish
        Validate and activate the process
13. In MUX > Go to Investments > Master object 
14. Open the instance we created and go to the sub-object module
15. Edit the Subject instance and go to the sub-sub-object module (master_granchild)
16. Create a master_granchild object instance
17. Go to MUX > My Workspace > Action Items
18. There is an Open Action item generated by the process

Expected Results: The action item contains a link to the sub-sub-object instance so user can navigate to it
Actual Results: The action item contains the reference to the sub-sub-object instance, but it is read-only, does not contain a hyperlink for the user to navigate to the same

Environment

Clarity 16.3.0, 16.3.1, 16.3.2

Cause

This scenario has been analyzed through DE170943

Resolution

It has been determined this is the current design. We didn't implement the link back for Third level Object

If a link back is required for 3rd level objects and MUX notifications are to be implemented for 3rd level objects, please raise an enhancement: 

Enhancement Requests for Clarity

Additional Information

In MUX > Administration > Notifications you can create a notification for the master_child subobject to alert the owner. This notification in MUX successfully redirects you to the master_child subobject instance.
However, there is no support for sub-sub-objects. The notification target object does not include sub-sub objects