XOG-2628: OBS Unit Name must be unique within an OBS

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

XOG OBS duplicate unit names under same parent results in 'XOG-2628: OBS Unit Name must be unique within an OBS'.

Scenario #1:

1. Created a two level obs.
2. Created OBS units with same name with the same parent name, it is giving error message"OBS-0212: OBS unit names must be unique within a parent unit".
3. Xog out the current OBS and Xog in with same name and under the same parent. It is Xogged successfully.

Scenario #2:

1. Created a parent department.
2. Created a child department by associating parent department.
3. Created a another child department using same name with same parent department. It is giving error message"OBS-0212: OBS unit names must be unique within a parent unit".
4. By removing parent department field, we don't get any error message and after saving above and associating parent field, you cannot see any error message.

Environment

Any supported Clarity release.

Resolution

This should not be allowed via XOG. The Clarity UI does not allow the creation of OBS units or Departments with same name with the same parent name.

XOG enforces the unique OBS name and Parent name constraint.

Scenario #1:

1. Created a two level obs.
2. Created OBS units with same name same parent name, it is giving error message "OBS-0212: OBS unit names must be unique within a parent unit".
3. Xog out the current OBS and Xog in with same name and under the same parent. It is xogged with warning messages "XOG-2628: OBS Unit Name must be unique within an OBS".

Working as expected.

Scenario #2:

1. Created a parent department.
2. Created a child department by associating parent department.
3. Created a another child department using same name with same parent department. It is giving error message"OBS-0212: OBS unit names must be unique within a parent unit".
4. By removing parent department field, we don't get any error message and after saving above and associating parent field.

Second scenario is also working as expected.