Hey Folks! I posted this in Technical yesterday, but would love to hear from some development foliks on the auto-renewal process. any input is greatly appreciated. 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
Hey Folks!
I posted this in Technical yesterday, but would love to hear from some development foliks on the auto-renewal process. any input is greatly appreciated.
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