Populating muti Value attribute in Task flyout

book

Article ID: 221263

calendar_today

Updated On:

Products

Clarity PPM On Premise

Issue/Introduction

In Modern UX when you populate a multi value lookup on a Task's flyout page and then you select a different task on the Task grid page, then the value entered on the original task is not saved in it but rather on a different task that you click on.


STEPS TO REPRODUCE: 

1. Create a dynamic lookup with the following id: 'C_L_SPP_PRVKY' using the following query
   
   SELECT  @SELECT:RESOURCES.ID:[email protected],
        @SELECT:RESOURCES.FULL_NAME:[email protected],
        @SELECT:RESOURCES.LAST_NAME:[email protected],
        @SELECT:RESOURCES.FIRST_NAME:[email protected],
        @SELECT:RESOURCES.UNIQUE_NAME:[email protected],
        @SELECT:RESOURCES.UNIQUE_NAME:[email protected],
        @SELECT:RESOURCES.LAST_UPDATED_DATE:[email protected]
  FROM    SRM_RESOURCES RESOURCES               
  WHERE   @[email protected]  
  AND     case when resources.user_id is null then 0 else resources.user_id end != -99             
  AND     RESOURCES.RESOURCE_TYPE = 3


2. Create a multi value lookup attribute on a Project object with the following ID: 'c_prj_spp' using the lookup created in step 1. Enter data for the API Attribute ID.
3. Create a dynamic lookup with the following id: 'C_L_SPP_TASK' using the following query:

   select
        @SELECT:RESOURCES.ID:[email protected],
        @SELECT:RESOURCES.FULL_NAME:[email protected],
        @SELECT:RESOURCES.LAST_NAME:[email protected],
        @SELECT:RESOURCES.FIRST_NAME:[email protected],
        @SELECT:RESOURCES.UNIQUE_NAME:[email protected],
        @SELECT:RESOURCES.UNIQUE_NAME:[email protected],
        @SELECT:RESOURCES.LAST_UPDATED_DATE:[email protected]
        from ODF_MULTI_VALUED_LOOKUPS mv
        left join PRTASK tsk on tsk.PRPROJECTID = mv.PK_ID
        left join SRM_RESOURCES RESOURCES on RESOURCES.ID = mv.VALUE
        where mv.OBJECT = 'project' and mv.attribute = 'c_prj_spp' and @[email protected]
        and (tsk.PRID = @WHERE:PARAM:USER_DEF:INTEGER:[email protected] or @WHERE:PARAM:USER_DEF:INTEGER:[email protected] is null)

 

4. Create a multi value lookup attribute on a Task object with the following id: 'c_tsk_spp_prvky'. In the lookup parameter mappings set 'prj_id' to 'object_id'. Enter data for      the API Attribute ID.
5. Add the attributes to respective Project and Task properties pages.
6. Create about 4 expense resources which will be used to populate the dynamic lookups.
7. Go to Modern UX -> Administration -> Blueprints. Click to open an instance of a Blueprint and drag and drop the attribute created in step 2 to 'Project Summary' section. 
8. Associate a project instance to Blueprint used in step 6.
9. Open a project Modern UX that has attribute created in step 2 populated.
10. Click to open the Task grid page and create on the Two tasks, 'Task A' and 'Task B'. Add the multi value lookup attributed created in in step 4 as a column
11. Click on 'Task A' then on 'Details' to open the flyout page.
12. In the flyout page populate a value in the multi value attribute then next click not in flyout page but on 'Task B' on the task grid page.

 

Expected Results: Values entered in flyout page of 'Task A' should be populated on the multi-value lookup attribute of 'Task A'. 
Actual Results: Values entered in flyout page of 'Task A' are saved onto 'Task B'. 

Cause

This is caused by DE61742

Environment

Release : 15.9.1, 15.9.2, 15.9.3

Component : PPM INVESTMENTS, PROJECTS, RESOURCES & NPIO MANAGEMENT

Resolution

Workaround: Avoid clicking directly onto another task after modifying the multi value attribute. 

This is resolved in Clarity 16.0.0