Hi,

I had a requirement. We are provisioning users from FIM to Google(Generic Rest API MA). There is an attribute 'att1' at FIM. I want to update that attribute on successful export(provision) into Google.

For example, If I am provisioning 4 users from FIM to Google, on two users got exported successfully and two got failed. In that case, fro success users i need to update 'att1' attribute to 'True' at FIM and for failed users i need to update false in "att1" attribute at FIM.

Can i know the proceedure to do that.

Thanks

Prasanthi.

Hello,

in the past I would have used transaction properties on that, but that Feature in code is deprecated.

I would now use Expected State Detection on this, which creates DREs on objects if state is correctly detected on Import flow.

With that DRE set the Attribute via a workflow.

/Peter

Hi Peter,

I have gone through the link provided. I understood that Expected State detection is used to know that state of an object at external source. But i am confused. how to check that user had provisioned. I don't want the users to be re imported from Google. As of now we are doing only exports. In this case can i know how to proceed.

Thanks 

Prasanthi.

Hello,

you dont need to reimport the users from google, simple "testing" way is to create a seperate export only sync rule like "Check Google Account Name" with an export flow of the account name from mv to that ma with "use for existence test" flag.

while this is an outbound syncrule it will in "reality" be evaluated on imports, with the result of a DRE be created. But there will be no import flow from google ma to mv.

But the google MA object must be connected to the mv object to get this working.

you can create a transition-in set then for all users that are getting this DRE and create a workflow that modifies your attribute.

/Peter

Hi Peter,

Thank you....

Sorry if am asking small questions....... 

1. The "use for existence test" we should create at FIM right. As of now there are no entries in "DetectedRuleList". 

2. We are using Code Based(MVExtension) code for google MA. In this case how can i update an attribute value at FIM on successful provision of a user to Google.

3. "But the google MA object must be connected to the mv object to get this working." could you please explain.

Hello,

1. the "use for existence test" is a flag on an outbound sync rule attribute flow, like "inital flow only". And yes you have to configure this in FIM Portal (sync rules)

2. For this to work it does not matter how objects are provisioned to the MA, its a seperate syncrule you can combine that with your current provision code.

3. I think that this is already the case on your side as the provisioning will create that connector for you, just want to make sure the you do not some kind of fire and forget ;-)

To make this work you must also have that attribute the you use as the isCorrectProvisioned" (att1) as an attribute in portal in order to change the value via a workflow.

Check the part with "operational outbound synchronization rule" in the link I stated above, that is what you need.

/Peter

The existence test fires on an import run profile step -- so do you need to be doing imports on that MA otherwise the existence test will never fire. Based on earlier comments this does look like a fire and forget type of approach.

A cheat would be to modify the API you are using to put the anchor attribute and the result into a file or DB and then import that through a separate MA.