Virtual fields on Team object are not visible on Mux Staff module

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

Virtual Attribute created on Team object by referencing an Investment object's attribute, does not show up on the Staff module on the MUX. Virtual attribute similarly created on other OOTB objects, for example Risk or if created on custom object, are viewable on the MUX

STEPS TO REPRODUCE:

1. Create a Static Lookup
2. On Investment object create a Multivalued attribute, example: Test Mult Field and associate it to the lookup created on Step 1, as a multi valued lookup
3. Create a virtual attribute on Team object, example:  Attribute_A_INV1 using Investment Object's field Test Mult Field created on Step 2 and define the API Attribute ID
4. On Team Object create a non lookup based virtual attribute, example: Simple Staff Virtual using Investment Object's attribute Name and define the API Attribute ID
5. On Risk object create a virtual attribute: using Investment Object's field Test Mult Field created on Step 1 and define the API Attribute ID
6. Create a virtual attribute on a Child Object of Investment: using Investment Object's field Test Mult Field created on Step 1 and define the API Attribute ID
7. On MUX create a copy of the Blueprint Standard Investment Hierarchy and include the modules: Staff, Risk and custom object referenced on step 6. Publish this blueprint
8. On Mux Hierarchies, create an instance and associate this blueprint created on Step 7

Expected Results :-

The Team virtual attributes are visible on Team(staff) in Classic UX and are also visible on MUX, in Hierarchy / Project in Staff Module

Actual Results :-

The Team Virtual attributes are visible on Team(staff) in Classic UX. However, these are not visible in Modern UX in Hierarchy / Project in Staff Module. The virtual attributes on out of the box object: Risk and custom child object, respectively are being visible on MUX

Environment

Clarity 16.3.1

Cause

DE169011

Resolution

This issue has been reviewed by the Engineering Team and is considered to be working as designed. The observations is due to the restriction that is present in the associated objects data provider (obaStaff) that does not support virtual attributes.

Any change to this functionality shall be deemed as an enhancement request. An enhancement request could be raised as per the following process, link