We are WordFly users. We have WordFly pages.
Back in the day WordFly pages was touted as a way to easily take RSVPs for unpaid event. I'm trying to get this setup with Special Activities as the destination for the pages responses not CSIs or just buried in the Pages Custom Tab.
It appears that my predecessor at Spoleto Festival had done this successfully but we have had some turn over and some of the detail seem to be missing and different from when I was working with this in 2019 time period.
I discovered the following configuration in ITR_WF_PAGE_FIELD_MAPPING referencing an Update Type of "(BETA) Special Activity".
I've also discovered some comments about having to change code back in the 2019 period before Pages became important for refunds coming into the COVID-19 period.
Is there anyone actively using pages to automatically take RSVPs into Special Events. I'm not finding a lot of documentation and clarity around this aspect of the Tessitura Setup.
Would love to have a conversation with anyone doing this successfully.
--Tom
I know it's not what you want to hear if there is a goal of it not being about CSIs, but I would absolutely still use Pages to collect quick registrants for simple, free events. CSIs get the data collected and it's connected to individual constituents after all. HOWEVER, if you have to have a capacity limit on it and that's tight, nothing about Pages will cut off registrations based on count--typically the dealbreaker for me in this situation. The other dealbreaker I tend to encounter with Pages is that you can really only use it in connection to a deployed email, since you more or less need the deployment in order to have a response sync to Tess.
It feels very odd to offer this recommendation in a thread about WordFly functionality, but I do heartily recommend L2's Flex2 product. We implemented it for the 'Stream2' variation that handles sales and authorization for Brightcove-based streaming, and all form types are available to you once you're up and running. There will be additional cost (and still no connection to Special Activities), but it's a very smart tool for a quick experience on the patron side and pretty solid data flow into Tess. Managing all it offers can be high maintenance, though with great payoff--just frustrating to keep on top off if you have a lot active at a time and realize a change that needs to be made across everything. Note that it does not have the ability to restrict access based on constituency/rank/etc, as that's not the point. If that's key, you will need to manage it through how you distribute the form url.
Thanks Jamie O'Brien. There are some good thoughts here. We are investigating several directions. No conclusion at this time.