nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Web View Event Registration Testing Process

Tioga Anderson

Hello,

We are moving away from Netcommunity so we are trying out the Web View Event forms to see if it'll work for us and save some funds by not having to purchase another event platform like GiveCampus. It's mostly golf events (golfers and sponsors listed on same registration forms) and small alumni gatherings (expect homecoming).

With the Netcommunity events, we have a process in place where all stakeholders in the event test the registration multiple times (different combinations of ticket prices, sponsorships, donations, etc.). It's total overkill but I think it's unlikely to change (they've been burned too many times in the past). This is a problem because as far as I've seen the Web View forms create actual gift records and new constituents even with the form in 'test' mode, which I then have approve the batch so I can then delete the 'gifts' and cleanup the event record to remove the fake registrants and guests etc.

Does anyone have a good 'testing' or 'review' workflow for making sure registration pages are good before making them available to the public? Is there a way for it not to make actual gifts and records in test mode that I'm just missing?

Thanks!

Find more posts tagged with

Events

Accepted answers

Alex Wong

We use RE NXT event registration form partially for now. We use Online Express for "complex" event where we sell more than one type of registration fee on the form. Reason for this is b/c RE NXT event registration form does not allow different CFAP (campaign, fund, appeal, package) per registration fee type. So we only use RE NXT event registration form when we only have ONE type to sell and so the gifts created will have the CFAP for this one type.

As for testing/review process, you are not going to be able to do a "full" transactional test in "test mode". So we do not do that, after making sure the "configuration" is good and tested, we don't do real transaction test. Instead, review is mostly around the page's look and feel (we embed the form into WordPress page on our website). IF requestor wants a custom auto-responder confirmation email, we send the screenshot of the auto-responder confirmation email for requestor to approve. Once page and auto-responder is approved, the page goes live.

All comments

Crystal Bruce

Tagging in All-Star @Austen Brown to see if she has a good workflow for reviewing before making public!

Alex Wong

Tioga Anderson

Thanks Alex, the CFAP won't be an issue for us, we do use different appeal codes depending on certain ticket types, but the gift processor is aware they need to update these in those cases. Maybe I'll let them do the rigorous testing at first and just deal with the cleanup and then try to transition away from that once they are comfortable with the new forms.

Are the OLX forms worth looking into at this point? I'm also considering OLX as a no-cost alternative to Netcommunity email but I'm leery of adopting OLX if it's just going to disappear in a year or two.

Alex Wong

OLX is not going to have a future, so don't bother going into it.