MarkAsOutstanding for person objects when importing from an HR feed

Question

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

Robert Byrne · Accepted Answer

Thanks to Markus and Ingvar for this hint which shows that in fact other tables, like Person or Department, can take advantage of the Target System Synchronization handling provided by Manager: 
 What i would do, if I want to use MarkForOutstanding when I am using the Sync Editor. 
 Create a Target System Namespace for the Import to the Person table. As you are using Sync Editor this would be the obvious choice. 
 
 Assign the Person table to that &ldquo;Target System&rdquo; 
 Enjoy the use of the Target System synchronization forms in the custom target system area.

Barry Jackson · Answer

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.

Barry Jackson · Answer

Hi Ingvar, 
 
In that case it's pretty much the same answer but with a HandleObjectComponent - Update to set isInActive to True on the Person object. 
 
Regards, Barry.

Endpoint Privilege Management

MarkAsOutstanding for person objects when importing from an HR feed