ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Ability to XOG in Display Mappings on child objects of Investment Object Corrupts the Attribute

book

Article ID: 237949

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

SUMMARY: If display mappings are xogging into the project object for the Priority attribute, the display mappings become corrupt and get disconnected for the parent investment object's priority attribute.  These should stay in sync as it should be inherited from the investment object.

STEPS TO REPRODUCE: 

    1.  Xog in different display mappings for the project object Priority attribute.  Make the mapping values go beyond 36, which is the top of the range.
     You can package the Project Object to get the xml and then add display mappings such as below added to the correct display mappings for Priority

 -- Add this to the bottom of the display mappings for the Priority attribute--
  
    <mapping hi="100" lo="100" mappingCode="range-0-0-null" typeCode="purple" value="">
              <nls description="Critical" languageCode="ca" name="Template"/>
              <nls description="Critical" languageCode="cs" name="Template"/>
              <nls description="Critical" languageCode="da" name="Template"/>
              <nls description="Critical" languageCode="de" name="Template"/>
              <nls description="Critical" languageCode="en" name="Template"/>
              <nls description="Critical" languageCode="es" name="Template"/>
              <nls description="Critical" languageCode="fi" name="Template"/>
              <nls description="Critical" languageCode="fr" name="Template"/>
              <nls description="Critical" languageCode="hu" name="Template"/>
              <nls description="Critical" languageCode="it" name="Template"/>
              <nls description="Critical" languageCode="ja" name="Template"/>
              <nls description="Critical" languageCode="ko" name="Template"/>
              <nls description="Critical" languageCode="nl" name="Template"/>
              <nls description="Critical" languageCode="no" name="Template"/>
              <nls description="Critical" languageCode="pl" name="Template"/>
              <nls description="Critical" languageCode="pt" name="Template"/>
              <nls description="Critical" languageCode="ru" name="Template"/>
              <nls description="Critical" languageCode="sv" name="Template"/>
              <nls description="Critical" languageCode="tr" name="Template"/>
              <nls description="Critical" languageCode="zh" name="Template"/>
              <nls description="Critical" languageCode="zh_TW" name="Template"/>
            </mapping>
 
 
 

Expected Results: XOG will not let you update the display mappings for an attribute that is actually on the investment object

Actual Results: XOG does an update and breaks the connection between the investment object and the project object attribute.
                

 
     



Cause

DE64552 as you should not be able to change items such as display mappings on attributes inherited from the investment object.

Workaround: None except do not try to XOG items into the project object. 

Environment

Release : 16.0.1

Component : Clarity Studio

Resolution

Resolved in 16.0.2