Hey Folks!
So, i pretty much know the deal here. Pledges only, not through the API, use the utility, RTFM. Right, i know. But that doesn't translate well to management. And I always like a good challenge :)
Oh, did I mention i'm on TNEW!
Right now, if I wasn't to provide a method to opt out, I was thinking of having every online membership contribution (Gift) create a CSI, which would prompt a local user to create a corresponding pledge. If a person phoned to opt out, we could suppress them from the auto renewal utility with an attribute and only run the utility on a list, filtering that attribute.
Does anyone have any thoughts on that process? Like it or don't?
So, then to complicate things; i'm also exploring the option to opt-out online. But the 2 methods i've thought of both have their own issues;
1: re-purpose TNEW's checkbox on the membership "Decline Benefits" to be "don't auto renew"
That's kinda okay, but it is membership specific in record, although i could search for any on that person.
2: LWP Validate Cart
I could write a procedure which prompts the user to accept, more an opt in, and store that as an attribute. But it doesn't guarantee that they actually complete the order.
I hope that is clear. I'd really like to talk with anyone using the auto-renew utility, and discuss processes and workflow. Or hear from anyone on the above.
Thanks,
James
Hi James,
We are currently on TNEW.
For each Contribution Type, in LTR_TNEW_CONTRIB_TYPE_CONTROLS you have the option of up to six slots for a combination of Address, Notes and Checkbox control types. And you can label and purpose the checkbox however you want. So theoretically you could have six checkboxes for one fund if you want. As Amanda indicates, this will all get pushed into a CSI and then it would be the responsibility of staff to act on the true/false results that come from the parameters you have set up for each checkbox.
I am currently re-working our donation page in Test. With one of our funds I have two checkboxes – One for “Please check if you would like your donation to be anonymous” and another for “Please check if you would like to donate monthly”.
Have you seen the new online TNEW documentation? I reference it all the time and it is very detailed:
http://www.tessituranetwork.com/tn_express_web_user_guide/TNEW.htm
For documentation on this topic go to Setup and Configuration>Contribution Control Slots
Duane
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of James Boncek Sent: October 6, 2011 12:12 PM To: Duane Woods Subject: Re: [Tessitura Technical Forum] Online Membership Auto-Renewal
Thanks Amanda. Least i'm not talking to myself.
As i understand, TNEW only offers that 1 checkbox per contribution/fund. Also, as i understand, this links directly to the "Decline Benefits" - however, i could rename it, hence, the repurposing. It i could just add another checkbox to a local table, i'd be all set, but its not exactly that easy....i'm trying to avoid another validation point in my LWP_Validate_Cart
From: Amanda Freeman <bounce-amandafreeman5080@tessituranetwork.com> Sent: 10/6/2011 10:56:36 AM
I might be misunderstanding what you mean, but I don't think you'd need to repurpose the checkbox. Why not just have a second checkbox for "don't autorenew"? Or make the second checkbox an opt-in checkbox. Either way it'll end up in a CSI and either prompt the person in charge of checking them to either create a corresponding pledge, or not do so depending on which direction you go.
-- View this message online at http://www.tessituranetwork.com/COMMUNITY/forums/p/5641/18097.aspx#18097 or reply to this message This message has been scanned by LastSpam eMail security service, provided by Protek.
Thanks folks, I get it now. And Duane, I forgot about the new online version! I got accustomed to using the old word doc.
Seems like this will work out alright! Thanks again.