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.

Parameterized lookups based on a boolean field do not allow selections in the MUX

book

Article ID: 140980

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

No values are selectable and can not be changed in the Modern User Experience (MUX) for parameterized lookups based on a boolean field.

STEPS TO REPRODUCE: 

  1. Go to Administration > Data Administration > Lookups
  2. Create a lookup: New_ux_param

    Query:
    SELECT
    @SELECT:RES.ID:[email protected]
    ,@SELECT:RES.FULL_NAME:[email protected]
    FROM
    SRM_RESOURCES RES
    WHERE
    @[email protected]
    @BROWSE-ONLY:
    AND ((RES.IS_ACTIVE = 1) AND (@WHERE:PARAM:USER_DEF:INTEGER:[email protected] = 1)) :[email protected]

  3. Go to Studio > project object

  4. Create a boolean attribute:  n_flg

  5. Create a numeric attribute: n_integ with Validation range 0 to 1

  6. Create a lookup type attribute called: new_ux_param_boo

    • Lookup linked: new_ux_param

    • Lookup parameter mapping: n_flg

  7. Create a lookup type attribute called: new_ux_param_integ

    • Lookup linked: new_ux_param

    • Lookup parameter mapping: n_integ

  8.  In the project object views, add all 4 attributes to the edit view

  9. Set the lookups as pull-down (Project properties View > Fields > By editing the field properties)

  10. Open any project and look at the fields

  11. Select the value 1 for the n_integ and click on the pull-down for new_ux_param_integ

    Values display

  12. Check the Boolean flag and do the same on the new_ux_param_boo

    No values display (This is the first anomaly of the Boolean based parametrized lookup)

  13.  Add the 4 fields to the list view

  14. Select the value 1 for the n_integ and click on the pull-down for new_ux_param_integ

    Values display

  15. Set the n_flg and do the same on the new_ux_param_boo

  16. Values display and can be saved

  17. Once values are saved on the list view, the project properties field shows the value and you can change it to any other

  18. Go to the Modern UX > Blueprints

  19. Add a section and the fields

  20. Link the project to the blueprint and open the project

  21. The values have been carried as specified on the Classic UI

  22. Change the value of the new_ux_param_integ

  23. Changes can be saved

  24. Try to do the same with the new_ux_param_boo field


Expected Results: The field value can be changed and saved  

Actual Results: No values are selectable and can not be changed

Cause

This is caused by DE52076

Environment

Release: 15.7

Component: Studio

Resolution

This is fixed within Clarity 15.8

Workaround: 

  1. Use an integer field instead of a boolean (as on the steps to reproduce)

    OR
  2. Create a static list lookup with Yes and No values

Additional Information

See also: Lookups master KB for Clarity