Issue
An instance has been upgraded from Istanbul to Jakarta, Kingston, or London releases.
The catalog item is displayed properly on native UI, but when viewed in Portal the containers are not honoring the UI policies.
The container should hide only one variable but instead hides all the variables within it.
Release
Jakarta, Kingston, or London
Cause
This usually happens after an upgrade.
Steps to reproduce the issue:
1. Create two variable sets.
- The first variable set should contain a multiple choice variable. (Choice 1, Choice 2)
- The second variable set should contain the following 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
- Container Start 1
2. Create a UI Policy. When Choice 1 is selected, set Variable 1 to: mandatory = false, visible = false
3. Check in Native UI, the UI policy works as expected, and also in the portal.
4. Give the containers a different name.
5. Upgrade the instance to Jakarta, Kingston, or London.
6. Check the catalog in the portal. The UI Policy hides both Variable 1 and Variable 2. It should hide only Variable 1.
Resolution
To fix this, do the following:
1. Try clearing the cache and reload the catalog item.
2. If clearing the cache does not work, rename the containers as container1, container2, and so on. Reloading the catalog in the portal should work as expected with only Variable 1 hidden.
3. Try creating new containers, and then reload the catalog in the portal.
Tip: Keep container names simple and do not duplicate container names.
