I have a simple case where the modification of the "MobilePhone" attribute should be approved by a manager. For this I use the basic RCDC for edit user and make a WF including an Approval Activity which I reference in a MPR which is triggered when the "MobilePhone" is modified. It works fine if the value for "MobilePhone" is the only change, but if e.g. the "Fax" attribute is changed in the same request, then the approver sees both the "MobilePhone" AND the "Fax" in the request content list. What I want is that only the "MobilePhone" attribute is shown in the request content list for the approver and that the change to "Fax" is performed despite the choice of the manager to approve the new phone number or not. Is that doable? I have tried the default Approver activity, and also created a custom approval activity in the hope that i can control everything in code by using a CurrentRequestActivity and a code activiy that preceeds the ApprovalActivity in the WF. But i haven't managed to do things right. I was hoping that i could e.g. update the requestparameters of the CurrentRequestActivity instance by deleted all except the one paramter to approve, but whatever i do all attributes still shows up in the request that the manager has to approve. (this is even just a simple scenario, since i want to do a separated Approval request for various other attributes in a user modify/request, e.g. a second manager has to approve a change in the "OfficePhone" value). I hope someone is able to help me out. :) Best regards

This is a feature that was requested for R2 unfortunately it only got partially implemented. Prior to R2, your only option would be to break up the request and resubmit via the Resource Client .NET code from codeplex. In R2, you could break up the request into 2 (or more) requests using Update Resource activity with the "Use Approval Activity" Parameter set to True. UNFORTUNATELY, this is Synchronous with each update activity. So each one needs to be done in sequence. If one is denied, the whole thing fails. So do you attributes that don't require approval FIRST. We wanted it do be done asynchronously (each child request being independent) but it didn't make it into FIM 2010 R2.Eric

Eric, Is that the ApplyAuthorizationPolicy parameter, right? I was using that in a scenario where I added a person to multiple groups, and yes, the activity waited for one approval to complete before it went to the next one. Frank C. Drewes III - Architect - Oxford Computer Group

Thanks for the answer. In my situation I'll have to go with the pre R2 solution. Just to be sure I'm following you completely, I'll listed below what I believe you suggest I do. You suggest that I make a MPR with a workflow with a custom action activity that is triggered when the value for "MobilePhone" is changed. This custom action activity connects with the FIM service through the Resource Client .NET service and creates a Approval request programatically. Is this the way to do it? (I know that the resource client web service can approval an approval request, but I haven't been able to find an example which shows how to create an approval request through the web service. If you know of an example please let me know) thanks again