How to change\generate new GenProcID for Process.

Question

Hi forum, 
 I'm using One Identity Manager 9.1.1 
 I'm trying to develo a process that assigns/removes a memebership to an account for a generic target system, given specific informations, and i need to monitor the correct execution of the provisioning process. 
 The first step of the process is and HandleObject Insert, that inserts a new memebership in a table. This step generates the defined Assign membership process for the specific target system. 
 In order to monitor the correct provisioning execution I want to check the job queue (with a check SQL column step) to check the provisioning process status, using the GENPROCID as key to find the process. 
 I cannot use the GenProcID of the calling process beacuse i could have multiple calling processes with the same GENPROCID, so i want to insert the memebership and set a specific GENPROCID to the assign membership process, so i know how to identify the provisioning process. 
 I tried using the parameter ProcID of insert step to set a specifcic GenProcID but it doesnt work and the provisioning process keeps having the same genprocID from the calling process. 
 Is It possible to define a new genProcID for the provisining process gnerated? 
 
 Thank You, 
 Enrico.

rodney rosenda_67072 · Accepted Answer

Hi Enrico, 
 The following is a bit nasty and depends on the GENProcId not being substituted. I think that a synchronization journal report actually covers your requirements more elegantly. You can always do the following in your custom process using a wait and retry loop: 
 
 Use the genprocid, xobjectkey of the group (BasisObjectKey) you are adding a member to, job chain name (ex: AAD_Group_Insert/Update/Delete), and task name (ex: AdHocProjection) to find the uid_job@jobhistory in case the provisioning task is already processed and moved to the jobhistory table. 
 In case the provisioning task is frozen in the jobqueue table you can find uid_job@jobqueue the same way as above. 
 Use the uid_job (jobid@dprjournal) and BasisObjectKey (CausingEntityKey@DPRJournal) to find additional info. Test what will happen if you end a frozen job with success. 
 Note that step 3 is not needed since you can use the waserror@jobhistory to find an error situation. 
 
 Provisioning is normally a fire and forget task, errors can happen and the above described steps can be error prone.

rodney rosenda_67072 · Answer

In my environment, 9.0 LTS Cumulative Update 2, is the specified output parameter name not used (bug). Enabling or disabling the process task parameter also does not work as expected (also a bug). The provisioning task always makes an output parameter with the name 'UID_DPRJournal' available, you can for example use it as follows: Value = f.UidComparison("UID_DPRJournal", "&Out(UID_DPRJournal)&" )

How to change\generate new GenProcID for Process.

Top Replies