FIM newbie here.
We have a situation where the HR source provides the user IDs and their manager IDs. Quite normal.
The kink is that many managers are "external" and their IDs are not present in the HR file but exist in AD.
An example 3 line file could be
UserID,FirstName,LastName,ManagerID,Title
123,Joe,Soap,X123,Manager
345,Chris,Spalding,123,Worker
678,David,Soul,123,Worker
Joe Soaps manager identified by X123 exists in AD as do all the other 3 users. The person identified by X123 just isn't present in the HR provided file. So the 'natural' use of anchors and references fail. It is impossible to push External people into the
HR system. However, All AD entries containing IDs are projected/joined into the MV and onwards into the Portal.
Is it possible to build a rules extension on import to get the "manager" via MV search using the key ManagerID?
I was hoping the following might be possible.
Invent a MV attribute to hold the manager reference called myManager type reference.
With the advanced attribute flow rule import to attribute myManager with flow rule XYZ
In the C# code
get the CS.ManagerID
<somehow get the MVobjectID of the MV entry having UserID = CS.ManagerID>
push the MVobjectID found into myManager
and then flow myManager to AD manager and Portal Manager attributes.
I am not sure if it is possible/would work.
Is it possible to grab a MV objectID with FIM C# methods?
Is it possible to work with reference typed attributes with flow rules?
Just what methods are available to work with the MV in C#?