-
Bug
-
Resolution: Fixed
-
Neutral
-
4.5.2
Hi,
The fix for MAGNOLIA-4069 may have an unfortunate consequence if the realName property isn't found, and instead a realmName property already exists, then the MoveAndRenamePropertyTask sets realmName to a null value.
Perhaps, the MoveAndRenamePropertyTasks should be wrapped within a PropertyExistsDelegateTask ?
Let me know if you have any questions.
Cheers,
Matt
Acceptance criteria
- is related to
-
MAGNOLIA-4069 Delta for 4.5 update contains typos in CheckOrCreatePropertyTask related to realmName property for system and admin userManagers
- Closed