Identity Manager

MarkAsOutstanding for person objects when importing from an HR feed

Hi.

Just wondering about how to handle an HR feed (typically from a CSV file) where removed/deleted employees are removed from the file. The use case is that some employees are fed from a file and others are created manually in 1IM.

I have tested to configure the "ImportSource" attribute to be set to my HR sync project and when an employee record is removed from the file, I have configured the workflow to set it as "MarkAsOutstanding" in Sync Editor. This works fine, and my question is how to handle that further in 1IM?

I would like to have that employee being permanently deleted. How can I do that?

Another question is how to see those employees that have the XMarkedForDeletion set in the Manager tool? I have found how to do this for target system accounts, but not for employees.

 

Kind regards,

Ingvar 

  • The challenge is that there is no Target system synchronization for a sync project that reads person objects from a file. So I haven't been able to find the method for outstanding object in Manager tool.
  • The link I posted above will answer your question which was " have configured the workflow to set it as "MarkAsOutstanding" in Sync Editor. This works fine, and my question is how to handle that further in 1IM?

    I would like to have that employee being permanently deleted. How can I do that?
    "
    Once the object is marked as outstanding in 1IM you need to post process it in the Manager to really delete it. Described in that link. HTH
  • Hi Ingvar,

    If I have understood you correctly you want to delete the Person record when it is set to 'MarkAsOutstanding'. (Not sure why you don't have the workflow configured to Delete instead of MarkAsOutstanding but I guess you have your reasons.)

    To do this create a process chain on Person that fires off the event UPDATE.

    Set a generating condition something like this:

    Value = $XMarkedForDeletion[o]:Int$ <> $XMarkedForDeletion:Int$ AndAlso _ $XMarkedForDeletion:Int$ = 2

    Then have a process step that uses HandleObjectComponent - Delete to delete the Person object that was just updated.

    Of course it may be that the employee cannot be deleted if it has assigned objects so you may have to remove assignments before you can perform the delete.

    HTH, Barry.
  • One more point, Ingvar. Keep in mind that if you delete a person, you will loose history associated with that person (approvals, etc.) So you might want to "permanently disable" (IsInactive=True) them instead of deleting them.