Issue Summary

This is reproducible on Data Center: (yes)

Given the right permission, a User can move objects from one object type to another (example use case: archiving an object by moving it to another object type).

When an object is moved, there is no validation done for the Unique attribute value configuration. One might move an object resulting in multiple objects having the SAME Unique value.

For reference - a mandatory value of an attribute (Cardinality Min>0) is enforced already on the Mapping level, and an object missing a Mandatory value at target, cannot be moved!

Steps to Reproduce

1. As a Schema manager / Assets Admin, Create two object types containing only the default set of attributes (OTA, OTB)
2. In OTB>Attributes tab, configure the Name attribute to be unique
3. Create two or more objects in OTA, all with the same name, e.g. "OBJ1"
4. Move one object from OTA to OTB
5. Try to create a new object in OTB, and call it "OBJ1" - this should show a validation error: "The attribute 'Name' has to be unique"
6. Move a second OBJ1 object from OTA to OTB

Expected Results

The second object named "OBJ1" will block/fail to move with a validation banner/message: "The attribute 'Name' has to be unique"

Actual Results

A second OBJ1 object is being created in OTB, regardless of the Unique constraint.
Trying to edit this object will show the validation message when saving.

(Same behaviour whether moving from List/Detail/Object view)

...

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available