none
MPR firing multiple times when attempting to remove reference attribute value using standard workflow RRS feed

  • Question

  • Hi,

    Hoping someone out there may have experienced this same issue.  I'm attempting to remove the value of a reference attribute attached to the "User" object in the FIM portal using an MPR / standard workflow.

    Based on the following link I have set up a workflow step to set the reference attribute to a space character

    https://social.technet.microsoft.com/Forums/en-US/bc2f6c99-5702-48ba-87b3-41eeb12dc40f/delelting-a-reference-value-in-fim-2010?forum=ilm2

    This kind of works in the sense that the attribute value is successfully removed, but a side effect is that the MPR looks like it is being called multiple times (when I look in "search requests" it is just filled with MPR calls to remove the attribute value on the same identity, the only option I have to stop them is to disable the MPR).

    I've tried using out of the box Function Evaluator and also using the Tools4FIM Function Evaluator to remove the reference attribute value, both display the same behaviour (the value is removed but multiple MPR calls are spawned).

    If I change the MPR to remove the value from a non-reference attribute (eg, a simple indexed string attribute) then the MPR is only called once as expected, so it seems to be specifically when trying to remove the value of a reference attribute.

    Details of how the MPR / Set / Workflow is configured is as follows :

    Requestors and Operations:

    set "Specific Set of Requestors" to "All Objects"

    Tick "modify a single-valued attribute" only

    Target Resources:

    Target Resource Definition Before Request is my configured Set of users

    Target Resource Definition After Request is the same Set as above

    Select specific attributes is selected and only the reference attribute is in the list of attributes

    Policy Workflows

    Has just the single workflow configured to run (Function evaluator step to set the reference attribute value to a single space character)

    Just wondering if anyone has seen the same thing ?

    We're using FIM 2010 R2 SP1 (4.1.3508.0)

    Wednesday, June 8, 2016 9:57 AM

Answers

  • What triggers this MPR? Basically what has to happen for the MPR to clear that value? It seems to me that is based on an update of the attribute itslef which makes it true everytime you put a space and it keeps looping indefinitely.

    Nosh Mernacaj, Identity Management Specialist

    • Marked as answer by CHAM01 Thursday, June 9, 2016 11:46 AM
    Wednesday, June 8, 2016 7:21 PM

All replies

  • What triggers this MPR? Basically what has to happen for the MPR to clear that value? It seems to me that is based on an update of the attribute itslef which makes it true everytime you put a space and it keeps looping indefinitely.

    Nosh Mernacaj, Identity Management Specialist

    • Marked as answer by CHAM01 Thursday, June 9, 2016 11:46 AM
    Wednesday, June 8, 2016 7:21 PM
  • That would make sense. As I say I followed the guidance from here :

    https://social.technet.microsoft.com/Forums/en-US/bc2f6c99-5702-48ba-87b3-41eeb12dc40f/delelting-a-reference-value-in-fim-2010?forum=ilm2

    Not sure if they found the same thing. I'm not aware of any other way of clearing out a reference attribute value, that is essentially what I'm trying to achieve (to delete the value in the attribute)

    Thursday, June 9, 2016 9:20 AM
  • Again, the issue is not with "how the value is cleared" but how you are triggering the MPR. What triggers this MPR? Basically what has to happen for the MPR to clear that value?

    Nosh Mernacaj, Identity Management Specialist

    Thursday, June 9, 2016 9:34 AM
  • Hi, sorry, I was being a bit slow on the uptake. You were correct in that I was updating the reference attribute whenever it was changed so as you say it was just putting itself into an infinite loop. Luckily I'm also updating a different attribute at the same time, so I've update the MPR to trigger only when the other attribute is modified, that way it only fires once and doesn't get into the infinite loop.

    Thanks for your help!!

    Thursday, June 9, 2016 11:46 AM
  • The devil is in the details, always. :)

    Nosh Mernacaj, Identity Management Specialist

    Thursday, June 9, 2016 11:58 AM