none
Email notification bug when requesting on behalf of a user RRS feed

  • Question

  • When our help desk staff submits a request on a behalf of another user the default email sent to the approver is misleading in that it looks like it's the help desk person that is requesting the access instead of the true beneficiary.  I believe this is because of the parameter:  //Requestor/DisplayName in the "Default pending approval email template" which resolves to the person submitting the request instead of the beneficiary.  How can I modify the email template so that it reflects the actual beneficiary's name instead of the person requesting the access?

    Also, are the email templates and object model documented anywhere?  There might be additional details I'd like to include to include in the approval, rejection and completion e-mails.

    Any guidance is appreciated!

    Christian



    • Edited by phunklounge Thursday, January 10, 2019 2:43 AM
    Wednesday, January 9, 2019 6:46 PM

Answers

  • I believe you may need to loop something like the MIMWAL into the workflow to calculate this for you. It has a //Delta grammar that you should be able to use to iterate over the changes to ExplicitMember and store in a WorkflowData variable that you can then reference from your email template. 

    Thanks,
    Brian

    Consulting | Blog | AD Book

    • Marked as answer by phunklounge Wednesday, February 6, 2019 7:14 PM
    Tuesday, February 5, 2019 8:55 PM
    Moderator

All replies

  • Christian-

    The templates are located under Administration>Email Templates in the FIM/MIM Portal. 


    Thanks,
    Brian

    Consulting | Blog | AD Book

    Friday, January 11, 2019 2:23 PM
    Moderator
  • Thanks Brian, what I'm trying to figure out is how to modify the default approver template so that it correctly displays the name of the beneficiary (target) user instead of the person person submitting the request when someone creates a request on behalf of any user.  

    If a data dictionary exists for the various data points (e.g.//Requestor/DisplayName) and the values they resolve to that would go a long way towards answering my question.

    Makes sense?  


    • Edited by phunklounge Thursday, January 17, 2019 5:58 PM
    Thursday, January 17, 2019 5:58 PM
  • change to //Target/DisplayName)

    Nosh Mernacaj, Identity Management Specialist

    • Proposed as answer by Borys Majewski Monday, January 28, 2019 3:05 PM
    Thursday, January 24, 2019 2:16 PM
  • //Target/DisplayName resolves to the name of the resource (security group) that is being requested... what I need is the name of the user that is the beneficiary of the request.
    Tuesday, February 5, 2019 8:53 PM
  • I believe you may need to loop something like the MIMWAL into the workflow to calculate this for you. It has a //Delta grammar that you should be able to use to iterate over the changes to ExplicitMember and store in a WorkflowData variable that you can then reference from your email template. 

    Thanks,
    Brian

    Consulting | Blog | AD Book

    • Marked as answer by phunklounge Wednesday, February 6, 2019 7:14 PM
    Tuesday, February 5, 2019 8:55 PM
    Moderator
  • Thanks Brian, I will give that a shot!
    Wednesday, February 6, 2019 7:14 PM