none
FIM 2010 Workflow Processing Issue RRS feed

  • Question

  • Hi All,

    We are having a problem with FIM 2010 (Update Rollup 2) workflow processing.

    Background is:

                Set: Object State 2 set (criteria based membership, criteria includes AUX_Attr1 ‘NOT Equal’ 3)

                Set Object State 3 Set (Manually managed membership)

    WF1: set AUX_Attr1 to 3

    WF2 : Set AUX_Attr1 to 2

    MPR 1: Transition in MPR (Transition set = Object State 2 set), fires WF2

    MPR 2: Transition in MPR (Transition Set = Object State 3 Set), fires WF1

    What we are seeing is the following:

                We add a user to “Object State 3 Set”

    From the request history we can see that:

    The successful request for the set membership change (transition in Object State 3 Set)

    The successful request by the Forefront Identity Manager Service Account to set AUX_Attr1 to 3

    and FIM correctly fires MPR 2, this sets AUX_Attr1 to 3 and this has been verified by looking through the request history

                A couple of seconds later FIM fires WF2 which sets AUX_Attr1 back to 2.

                The request history shows no signs of the object transitioning back into “Object State 2 set” so I am unsure why this workflow would trigger again.
    Monday, August 6, 2012 1:24 AM

All replies

  • Best thing to do with this problem is look at the request that caused this to happen and look for parent requests and for the applied policies

    David Lundell, Get your copy of FIM Best Practices Volume 1 http://blog.ilmbestpractices.com/2010/08/book-is-here-fim-best-practices-volume.html

    Tuesday, January 7, 2014 7:28 PM