Hello all,
We have a situation with IDM (7.2 SP6), where we are attempting to simulate a 'role to position' assignment internally within IDM. ie we want an entry type to represent the position object that should replicate positions in HCM that we can then assign Roles and Persons to. Initially we attempted using the MX_ROLE entry type for both position (ie ROLE:POSITION...) and business role (ie ROLE:BUSINESSROLE....) using the differing name format. Unfortunately we experienced a number of issues with our workflows and approval as Role->Role is considered a 'structural' relationship with MXREF_MX_ROLE and MXMEMBER_MX_ROLE as opposed to an 'assignment' so no pending value is generated, validity is difficult and the approval becomes poisonous. Any thoughts to correct this would be appreciated?
With the above situation in mind, I attempted to use the MX_GROUP entry type to simulate the position object, and linked roles and persons to this. In the short term, we had pending values created and approvals working nicely, though inheritance was now the isse as the MX_PERSON was not inheriting the roles indirectly via the Group. The other problem we had here related to the actual use of the group object and all the implied links to AD provisioning....too much heartache.
So, next attempt is to use a newly defined entry type Z_POSITION. This is my first attempt on this, and while the entry type and attribute creation seems simple enough, I am struggling with activating the entry type via the UI. How can I activate the maintenance of the new entry type in the 'Manage' tab, such that it is accessible in the 'Show' dropdown?
Your assistance with the individual Qs would be appreciated, in addition to your thoughts on the best concept design to achieve the position object described above.
Cheers
Andrew