Project

General

Profile

Actions
Copy link

Feature #1145

closed

Support multiple organizations for one contract

Added by Alena Peterová over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
High
Assignee:
Radek Tomiška
Category:
Contractual relationship
Target version:
Moonstone (9.1.0)
Start date:
06/18/2018
Due date:
% Done:

100%

Estimated time:
Owner:

Description

One contracted position can have 0 or 1 link to the organizations structure now.

We want to make use of multiple organization structures and be able to place one contract:
  1. to multiple org. structures
  2. to multiple positions in one org. structure
Use-cases:
The contracts are imported from HR for both cases. Manual creation of contracts is definitely not wanted.
  1. one structure is "Systemized positions", the second structure is "Locations". Placing in "Systemized positions" is imported from HR and it's used for computing automatic roles and/or managers. Placing in "Locations" is processed manually by the administrator, who knows where the users really "sit". This placement is used for putting users in Active Directory structure.
  2. the structure is "Departments", the user has contract in one department, but sometimes needs to help in some other department (a doctor helps in different hospitals)

Related issues

Related to IdStory Identity Manager - Task #779: Contractual relationship - More relations on organizationsClosedRadek Tomiška10/23/2017

Actions
Related to IdStory Identity Manager - Task #732: Recalculate automatic roles after move some nodesClosedRadek Tomiška10/03/2017

Actions
Actions
Copy link
 #3

Updated by Radek Tomiška over 6 years ago

  • Status changed from New to In Progress
  • Target version set to Moonstone (9.1.0)
  • % Done changed from 0 to 20
Actions
Copy link
 #5

Updated by Zdeněk Burda over 6 years ago

  • Priority changed from Normal to High
Actions
Copy link
 #8

Updated by Ondřej Kopr over 6 years ago

I made part of review:

  • implement IdmContractPositionService as script enable is good idea, thank you,
  • when I synchronize positions is propagate provisioning for each add role (all automatic roles has system) the ticket #1043 must be probably finally solved in this version :D is my responsibility,
  • automatic role recalculation works perfectly, I was not able to break the behavior with recalculation and I really tried :),
  • it is possible create automatic role by attribute with equals to "Next positions (IdmTreeNode - List of ids or codes)" this doesnt work, but is necessary create automatic role by attribute to equals to this attribute? Probably not,
  • many of projects synchronize contract slices and probably next positions will be synchronize in this synchronization -> but create new next position for contract controlled by slices is possible, so I can create script for update next positions in the synchronization.

For now I didnt find bugs or strange behavior for next positions. I will continue with feedback tomorrow, now I'm tired.

Actions
Copy link
 #9

Updated by Ondřej Kopr over 6 years ago

  • Status changed from Needs feedback to Resolved
  • Assignee changed from Ondřej Kopr to Radek Tomiška
  • % Done changed from 90 to 100

I made last test, I didnt find problem with the feature, main purpose of the feature is two position for one contract with all automatic role and this works perfectly. Thank you.

Actions
Copy link
 #10

Updated by Radek Tomiška over 6 years ago

  • Status changed from Resolved to Closed

Thx for feedback:
- i removed next positions from automatic roles by attributes. I removed 'guarantees' attribute too, it's correct (they are unimplemented too i think)? https://github.com/bcvsolutions/CzechIdMng/commit/2e505b2fd87f4c3b5c3e9d3cfe56c2bdd8917e1b
- slices and next positions - next positions are not included in slices, they work separately => the same behavior as other eav definitions. I added 'ScriptEnabled' annotation to 'IdmContractPositionService' so is possible to work with them manually in script if needed, as you says.

Actions
Copy link
 #11

Updated by Radek Tomiška over 5 years ago

  • Related to Task #779: Contractual relationship - More relations on organizations added
Actions
Copy link
 #12

Updated by Radek Tomiška over 4 years ago

  • Related to Task #732: Recalculate automatic roles after move some nodes added
Actions
Copy link

Also available in: Atom PDF