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
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.
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
Hmm...well, maybe someone from TNEW will chime in. We're not even live yet with TNEW, so I may just be wrong or misunderstanding... are you on v3? Because in ltr_tnew_contrib_type_controls I can set up many checkboxes (or notes panels, or address panels) and label them however and it all goes into a CSI and as far as I know doesn't link back to anything.