IT Shop Request Properties changing display when adding Condition (query) to Value definition (9.2 version)

I have a request property set up where the 2nd and 3rd parameters are dependent on the selection of the first. I am able to get that selection using $PC(<param name>)$ but when I try to apply a Condition (query) to filter down the options to the "department" selected for parameter one, the display in the web portal changes from a tree structure display to a drop down selection with the full path displayed. How do I keep the tree structure of the display over the drop down selection? Should I be doing the filtering in the Valuation script instead of the Condition (query)? My data is filtered to what I want but I need the display in the web portal to remain the same.

My Condition query

FullPath like $PC(my_param)$ + '%'

Parents
  • Adding a Condition (query) changes how the One Identity Manager 9.2 Web Portal renders the parameter. Instead of using the hierarchical tree control, the portal treats it as a dynamically filtered lookup and displays a dropdown containing the full path.

    Your condition is valid:
    FullPath LIKE $PC(my_param)$ + '%'

    This correctly limits the available entries to the department selected in the first parameter.

    Moving the filter to the valuation script will not preserve the tree. A valuation script calculates or preselects the parameter value; it does not control which values are available for selection.

    In version 9.2, the available options are:

    1. Keep the condition and use the filtered dropdown.

    2. Remove the condition to retain the unfiltered tree.

    3. Implement a Web Portal customization if both dynamic filtering and hierarchical navigation are required.

    If the full path makes the dropdown difficult to read, you may also review the display pattern of the referenced table. Changing it can shorten the displayed labels, but it will not restore the tree control.

Reply
  • Adding a Condition (query) changes how the One Identity Manager 9.2 Web Portal renders the parameter. Instead of using the hierarchical tree control, the portal treats it as a dynamically filtered lookup and displays a dropdown containing the full path.

    Your condition is valid:
    FullPath LIKE $PC(my_param)$ + '%'

    This correctly limits the available entries to the department selected in the first parameter.

    Moving the filter to the valuation script will not preserve the tree. A valuation script calculates or preselects the parameter value; it does not control which values are available for selection.

    In version 9.2, the available options are:

    1. Keep the condition and use the filtered dropdown.

    2. Remove the condition to retain the unfiltered tree.

    3. Implement a Web Portal customization if both dynamic filtering and hierarchical navigation are required.

    If the full path makes the dropdown difficult to read, you may also review the display pattern of the referenced table. Changing it can shorten the displayed labels, but it will not restore the tree control.

Children
No Data