Container hiding all variables, and not honoring UI Policies after upgrade. - Support and Troubleshooting

Container hiding all variables, and not honoring UI Policies after upgrade. Issue  Symptoms Instance has been upgraded from Istanbul to Jakarta, Kingston or London.

Catalog item is displayed properly on Native UI, but when viewed in Portal, the containers are not honoring the UI Policies.

Container should hide only one variable but hides all the variables within it.

Release Jakarta, Kingston, London

Environment This usually happens after an upgrade

Steps to Reproduce Step 1: Create 2 variable sets.

Step 2: First variable set should contain multiple choice variable . ( Choice 1, Choice 2 )

Step 3: Second variable set should contain the below variables

Container Start 1 Variable 1 Variable 2 Container End 1 Container Start 2 Variable 3 (makes this field mandatory from the dictionary) Variable 4 Container End 2 Step 4: Create a UI Policy - When Choice 1 is selected , make Variable 1 => mandatory = false, visible = false

Step 5: Check in Native UI, the UI policy works as expected, and also in Portal.

Step 6: Rename the containers with a different name.

Step 7: Upgrade the instance to Jakarta, Kingston or London

Step 8: Now check the catalog in Portal, and the UI Policy will hide Variable 1 & Variable 2 both .

Step 9: It should hide only Variable 1

Resolution Resolution 1 : Try clearing the cache and reload the catalog item.

Resolution 2 : If clearing the cache does not work, rename the containers as container1 , container2 etc. Now reloading the catalog in portal works as expected. Only Variable 1 is hidden.

Resolution 3 : Try creating new containers, and reload the catalog in portal.

ALSO, TRY TO KEEP THE CONTAINER NAME SIMPLE.

CONTAINER NAMES SHOULD NOT BE DUPLICATED.