-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 6.5.0
-
Fix Version/s: 6.5.0.2
-
Component/s: Module - Relationships
-
Labels:
Setup:
- Add a property to the managed user schema called favoriteManager which has the same relationship setup as "manager".
- Update manager and favoriteManager such that they return-by-default=true.
- Create 3 users. empolyee1, employee2, boss1.
- make the manager of employee1 and employee2 to be boss1.
- make the favoriteManager of employee1 and employee2 to be boss1.
Request:
- read the employee1 object with
managed/user/employee1?_fields=*
. Note that both the manager and favoriteManager should return in the results.
- update the employee1's manager to be employee2:
PUT openidm/managed/user/employee1 { [other user fields]... "manager": {"_ref","managed/user/employee2"} "favoriteManager": {"_ref","managed/user/boss1"} }
Verify:
- read the boss1 reports.
managed/user/boss1?_fields=*,reports
- It should be expected that boss1 no longer has employee1 as a report.
- is a backport of
-
OPENIDM-13242 Updating relationship with the same object in a different relationship will not delete reverse references of the updated relationship.
-
- Closed
-
- is backported by
-
OPENIDM-13267 Backport OPENIDM-13242: Updating relationship with the same object in a different relationship will not delete reverse references of the updated relationship.
-
- Closed
-
- is duplicated by
-
OPENIDM-13267 Backport OPENIDM-13242: Updating relationship with the same object in a different relationship will not delete reverse references of the updated relationship.
-
- Closed
-