Details
-
Sub-task
-
Resolution: Done
-
Minor
-
None
-
None
-
None
-
2022 Sprint 1, 2022 Sprint 2, 2022 Sprint 3, 2022 Sprint 4, 2022 Sprint 5
Description
There seems to be an issue with custom entity attributes after defining the first one and then creating a new metadata source to use it. This happens most often with the list type, but I've also seen it happen with the string type; When navigating through the metadata source form and reaching the relying party overrides, the new CEA will not display. Adding a second CEA (or possibly making another new metadata source) will cause the previously missing one to appear.
The easiest way I've found to reproduce this is to run the selenium suite with all but the SHIBUI-1732 test commented out.