none
FIM Set membership not evaluating RRS feed

  • Question

  • Hi

    In the FIM Portal, we use a number of sets and MPRS to run workflows and previously have had no problems.

    We're having a difficulty with a particular set of "Requests" where we want to run a workflow if a Request is denied to email a 3rd party.   Our set has the following criteria:

    -----------------------------------------------

    Select request that match all of the following conditions:

    Request status is denied

    TargetResourceType is VisitorConfigurator (a custom resource type).

     ------------------------------------------------

    If you 'view members'  in the RCDC it looks to have the right members, although we have now discovered that the RCDC merely displays what it _should_ have, not what it actually has.   The workflow is never run when the Authoriser denies the request.   However:  When the FIM_TemporalEventsJob is run at 1AM (or manually) we find that the set gets fixed, we see a request passes through called "Set Correction For Set deniedRequests"  and our workflow magically runs!

    We have added an additional binding to the Request resource type for the Email attribute - this is what is going to be used for our 3rd party email address.   We have another set which is actually used to send the email:

    -------------------------------------------------------------------
    Select request that match all of the following conditions:

    E-Mail starts with %
    -------------------------------------------------------------------

    This works fine!   So, it seems if we try to create a set based on the original attributes it doesn't work but with our added one it does.  We've looked at permissions and we think we have everything covered there, and if it weren't the SQL job wouldn't work.   We are now at a bit of loss as to how to move forward!

    Any ideas?

    Regards

    Andy Swiffin and Ian Swift, University of Dundee


    Wednesday, October 22, 2014 11:14 AM

All replies

  • Andy,

    I believe this is the expected behavior.  Because the request status is changed by the FIMService, and not some other actor, the sets using that attribute are not re-calculated unless FIM_TemporalEventsJob is run.  I've run into this before trying to do the exact same thing.  So far I have not found any clever way around this.

    Regards,
    Andrew

    Wednesday, October 22, 2014 4:55 PM
  • I believe this is the expected behavior.  Because the request status is changed by the FIMService, and not some other actor,

    ...

    Thanks very much for the reply Andrew.  That's given us something to think about!

    I am just trying to get my head around it though,  When the FIM_TemporalEventsJob runs it sets a value on our added email address attribute on the request object.   This is then causing the request to fall into our second set  which is sending the email to that 3rd party.  This part of our process works fine.  Surely this is also the FIMService who is doing this?  

    Cheers

    Andy

    Thursday, October 23, 2014 8:34 AM