Using S-tags in global AutoResponder for Delayed Self Pledge payment

Options

Hi all,

We were recently informed by BB Support that when a TeamRaiser DSP is processed, Luminate is sending out the global autoresponder for a donation form Installment Final (payment) Thank You. They confirmed this is a bug, as LO should be sending that same AR, but for the specific donation form in use by the TeamRaiser. As a workaround, they suggested customizing the global AR to conditionally display information about the Participant and TR.

The problem we're having now is finding appropriate S-tags to use. It seems that only a few of the S120 parameters return information, and none of them identify the TeamRaiser or Participant. Does anyone have experience with customizing these global ARs?

Thanks in advance,

Erik

Tagged:

Comments

  • Not sure if I've got enough detail here to intelligently reply, so you'll want to test this out to see how it goes. All you really need is to get the event ID and you should be able to use E-tags to get anything else. It'd be something to the effect of…

    [[?xx-1xnullx::x[[S120:dc:teamRaiserId]]x::
    non-TR content.
    ::
    TR content, and you can use [[E42:[[S120:dc:teamRaiserId]]:param]] for all kinds of stuff
    ]]

    As for which tags to use, that's where things tend to get wonky. [[S120:help]] is supposed to give you a rundown of what's possible with examples for each, but the problem is that your admin previews usually get different access to the gift info than the actual system that sends the “real” email. Even if you figure it out on the admin side, it might still fluke when the thing actually sends.

    So have fun with that. Most of TeamRaiser's immediately-sent donation-related emails are using something pretty close to the Donation2 system, so I'd recommend starting there:

    • Make a donation form and add your tags to its thank you page.
    • Go to the live form, and change the url to replace form1 with the word completed, and add &df_preview=true to the end.
      • That's a fairly solid render of a vanilla donation form, and should output most tags you can get in a non-TR context (might be what's rendering your final gift autoresponder).
    • Now add &FR_ID=1003 and PROXY_ID=123451234 …you can replace those numbers with an actual TeamRaiser ID and registered constituent ID, but it probably doesn't actually matter.
    • Cross your fingers and hope that the df_preview system is the same rendering engine as the donation autoresponders.


    LO PDF Receipt documentation has some other tags that I know do work, wouldn't be too surprised if they work in the donation context even though they're not supposed to.

    LO's display applications documentation has a buncha links to subsystems, but good luck with it. Any time you see a reference to friendraiser, you're looking at some pretty old info.

    Even if you can get the event ID to work, S120:help and the LO documentation don't show anything related to participant ID. [[S120:dc:participantName]] is supposed to give the name, and participant_name definitely works on donation receipt PDFs, but dunno that I've ever seen something that'd spit out the constituent ID of the participant.

    You would be able to get donor info with [[S1]], of course.

  • Thanks for the info, Jeremy. Since LO 22.3 contained a patch that corrected the bug, DSP payments are now triggering the applicable AR from the donation form specified in the TR settings. So, we no longer need to modify the Global AR.

Categories