Details
-
Bug
-
Resolution: Fixed
-
Blocker
-
COmanage Registry 4.2.0 (Pacific Pier)
-
RHEL 8.7, Registry 4.2.0, PHP 8.1.18
Description
We are unable to access the Namespace Assigner Settings screen in COs that do not already have a cm_namespace_assigner_settings record entry in the COmanage database. We've identified the issue as stemming from the validation rule configured for the name_type field in NamespaceAssignerSettings.php being set to required. The Namespace Assigner Controller is attempting to create a new cm_namespace_assigner_settings record if there is no record for the current CO, but this fails validation because there is no associated name_type value supplied. We have temporarily worked around this by setting name_type required to false and leaving allow empty set to false. See screenshots showing the UI error message when loading the Namespace Assigner Settings screen and the corresponding error message entry.