Pending Value Problem / Attribute Not Being Read

[#1]

Hello fellow experts. I've written something about this problem before. I had hoped that by rebuilding the repository where I'm having my provisioning issue, the problem would be solved but I'm still having the same issue. This leads me to believe it's something inside the provisioning framework or maybe a bug inside IDM itself.

A little background on my environment, I am running IDM v7.2, patch 5 on top of an Oracle database.

I'm trying to write some attribute values back to HCM from IDM. To do this, I used a setup that has been covered in other discussions. Basically, I have a repository that was created as an AS ABAP Application Specific repository referring back to my HCM system and the hook tasks have been manually changed to use the Business Suite tasks.  I have a BAdI setup on HCM's side and ran the initial load to bring the HR_COMMUNICATION privilege over to IDM. This all worked. My test user has an account in HCM and the PRIV_XXX_ONLY and PRIV_SYSTEM_XXX privileges for this repository and has an email address attribute, MX_MAIL_PRIMARY, and an ACCOUNTXXX attribute.

When I attempt to assign the HR_COMMUNICATION privilege for this repository, the pending value that get created doesn't grab the MCVALUE from this person's record in the Identity Store.

This makes no sense to me. The value is clearly there. Why is it not being entered into the pending value entry type for the provisioning framework to process it? Here's the task in question:

I'm at a complete loss on this one. If anyone has any suggestions or paths I could go down to look into this, I'd be eternally grateful. Thanks.

[Former Member · Accepted solution]

So thanks all for getting me to think about the various different ways in which this problem could be solved. I did, finally, get it fixed yesterday. Like I've been saying, this is a DEV environment and this functionality works in PROD so while I wanted to fix the problem without going this far, the thought occurred to me that maybe I should just import PROD's Provisioning Framework then point all my hook tasks and whatnot to that framework. That seems to have done the trick.

I would still be interested in know what the real problem was in case I run across it again but in the world of consulting, the method of solving the problem really doesn't matter, only that the problem is solved.

[Former Member · Accepted solution]

Awesome. If you add a "delay before start" (to halt the processing for a few minutes) on the task that used to fail, then look at the PVO values/audit as I mentioned earlier you should be able to see where it's set.

[Former Member · Accepted solution]

That's a good idea too. I sometimes forget I can put a delay on tasks which would allow the pending value to hang out there for a bit and thus let me look at it. Thanks for that. I'll use that at some point in the future, I'm sure.