Is it possible or will it be possible for an MPR to be linked to Transitions in more than ONE Set? RRS feed

  • Question

  • Hellos.

    Can it be arranged for a single MPR to be fired if a user Transitions out of Set A *AND* Transitions into Set B.

    In other words the Workflows associated with this MPR should be run *only* if user Was in Set A and is Now in Set B.

    Our customer is not unusual. He uses 3 status levels: Active, Passive, Suspended.

    There are then 3! possible changes. Initially they only wanted Notification (and other stuff done) when a User became Suspended or when a User no longer was suspended. This was easy. Just the one Set of Suspended people and 2 rules. Transition In and Transition out of it.

    However, the customer now wants to be Notified when a Person leaves the Passive state and becomes Active. However, He might move Passive to Active *OR* he might move Passive to Suspended. I thought of just creating a new Set of Passive people and having a pair of MPRs for Transition In and Transition Out of this.

    But. If he moves Passive -> Suspended. I get both Workflows running, one for change from Passive and another for becoming Terminated. I *guess* FIM kicks them off at same time and they run in parallel. I am also afraid they interfere with each other.

    What is best way to arrange a single Workflow to run and only run when user Leaves Set A and Joins Set B?

    Wednesday, March 26, 2014 8:01 AM

All replies

  • Can you use a request MPR rather than a transition MPR?

    Wednesday, March 26, 2014 3:38 PM
  • Can you use a request MPR rather than a transition MPR?

    Wednesday, March 26, 2014 3:39 PM
  • In this case, I would re-think states here and create only Transition In notifications:

    • -> Transition In: Status: ACTIVE
    • -> Transition In: Status: PASSIVE
    • -> Transition In: Status: SUSPENDED

    So it would not send double notification (leaving state A and entering state B). If you don't want such notification for newly created users, maybe think about request MPRs as Mark suggested? Then you can set different workflow (and notification) for each state changes.

    If you found my post helpful, please give it a Helpful vote. If it answered your question, remember to mark it as an Answer.

    Wednesday, March 26, 2014 4:56 PM
  • The problem with request MPRs and Transition In MPRs is that they do not provide the previous value. I know that it changed and what it's current value is but I cannot determine what the value used to be.

    At least with Transition Out Sets I know both previous and current values!

    I guess I am forced to buffer the previous status in some FIM custom attribute and use as you suggest the Transition In sets whose WF (re)sets that custom attribute.

    Thursday, March 27, 2014 8:28 AM