[Beta 1.16.7.4] Next-Gen Check-In ignores the Display Settings templates and the Header Text settings in the Check-In Configuration

[bobrufenacht]

Description

Next-Gen Check-In ignores the Header Text and Display Settings. Changing the lava in those fields does not seem to change the Next-Gen screens.

Actual Behavior

Changing Header Text and Display Settings do not seem to change the displays on Next-Gen Check-In.

Expected Behavior

I would expect to output to behave as described in the help text.

Steps to Reproduce

• Go to the check-in configuration.
• Update the header text fields and the Display Settings templates (I just added 123 to the end).
• Reload and rerun check-in.
• field displays are unchanged.

Issue Confirmation

• Perform a search on the Github Issues to see if your bug or enhancement is already reported.
• Reproduced the problem on a fresh install or on the demo site.

Rock Version

1.16.7.4

Client Culture Setting

en-US

[nairdo]

Hi @bobrufenacht, We wanted to let you know that the Display Settings features are not used by NextGen check-in. You can find this mention in item 19 under Settings in the documentation.

One of the key reasons for this is that NextGen is designed to be platform-agnostic, ensuring compatibility not only with web but also with Rock Mobile. This approach allows us to provide a seamless experience across different platforms without being limited to HTML-only configurations.

If you have any further questions, please feel free to reach out. Otherwise, we will proceed to close this issue.

[bobrufenacht]

@nairdo It makes sense to me not to support HTML for platform-agnostic reasons. However, it does seem like being able to change the text is a "lost feature." I think the primary reasons for those fields was to change text more than change formatting (although I'm sure that happened as well). But I agree that a second set of parallel options would also be confusing. Would it be possible in a platform-agnostic version to strip the HTML but use the text (maybe that gets documented in the help text)? Those fields still exist but are now non-editable.

[zackdutra]

@nairdo could you confirm if what you are saying is that this recipe no longer works? We use it for all of our event check in. This might hold us back off v17 until we find a workaround. https://community.rockrms.com/recipes/385/event-specific-custom-check-in-success-messages

[nairdo]

@zackdutra I've not used that recipe. I'm just saying the Display Settings features are not used by NextGen check-in. The old check-in system still works as-is in v17.

[nairdo]

Would it be possible in a platform-agnostic version to strip the HTML but use the text (maybe that gets documented in the help text)?

@bobrufenacht We reviewed this briefly today and we would be interested in seeing what other organizations are looking for this. Please submit the idea over at https://community.rockrms.com/ideas-changes so the community can vote on it.

Thanks again for all you're doing to make Rock Better Together.

[zackdutra]

@nairdo would this be open for discussion without submitting it into the abyss of the ideas page? It's a clearly cut feature, loss of functionality from what we had before - a breaking change. We're heavily relying on this. I let the team know today, and now none of them want to upgrade to next gen. It's really not an idea, we're just asking to not lose functionality that we were relying on to facilitate events of over 1,000 attendees at a time.

[nairdo]

@zackdutra I'll research the history of that particular topic (from the Next-Gen check-in discussions) and I'll get back to you in a few days.

[zackdutra]

Thank you @nairdo

[zackdutra]

@nairdo I also wanted to convey that this does not need to be accomplished in the exact same way.
The recipe posted above provides a great deal of value during check in, and I don’t believe that’s limited to just our church. If Spark would like to accomplish the same end goal another way, I’d be very open to giving input on that as well.

[nairdo]

Zack (@zackdutra) , I completely understand where you're coming from. Most of us here have been in your shoes at some point (working at the church), and we really value the effort and thought you've put into your setup.

As we work on next-generation solutions, we're often faced with tough decisions about which features make it into the initial releases. Time constraints and competing priorities mean some features -- like the one you're referencing -- don't always make it in right away. That said, this doesn't mean it's off the table forever. In fact, we're actively exploring ways to create hooks into the check-in process, so you could trigger actions at specific points during check-in.

For now, we'd love to hear more about what you specifically need and when during the check-in process you'd need it. So we'd still ask that you submit the idea. Your input could help shape how we approach and implement this feature.

It's also worth noting that the "classic" check-in system will remain available in Rock for several years. You don't need to switch to the Next-Gen system immediately for event check-ins. That said, we'd still encourage you to try it in other areas, like Children's check-in, where it's delivering positive results. This would let you gain experience with Next-Gen during its beta phase while keeping your event check-ins running as they are.

Regarding the 'ideas abyss'... Please know that every single idea submitted is reviewed as it comes in. Some ideas are sent to the development team right away, while others require more time to evaluate (or consider the vote count). The volume of submissions can be overwhelming, but we are committed to giving each one consideration. If you're interested, we'd love to invite you to help manage the Ideas board with us. We can provide access and guidelines if you're willing to partner to serve the community in this way.

Thank you for being an advocate for the whole Rock community. Your input helps make Rock stronger, and we share your commitment to looking out for what's best for everyone.

[zackdutra]

Hi @nairdo - thank you for the thought out and well stated response.

I've gone ahead and submitted the idea here: https://community.rockrms.com/ideas/2058/custom-success-messages-badges-for-check-in

Unfortunately having next gen check in without the custom success message feature creates quite a dilemma for us. Next gen check in would have been most useful for large events (1,000+ people). We were excited to see the speed improvements delivered by the next gen technology. Lines can back up quite a bit for these events, and we often need 30+ volunteers at each event to process check in without creating a back up, due to the speed at which classic check in runs. At the same time, these events require the success message to catch those individuals who should not be able to check in and need to be sent to a registration help desk, otherwise we would regularly end up with students going to camp without waivers signed, payments completed, etc.

We of course are looking forward to using next gen for weekend services, but that really wasn't where the big value add was for our organization.

I appreciate your time and the careful review of the idea. Please feel free to contact me with any questions.

[zackdutra]

@nairdo I was wondering if it would be possible to have the idea reviewed now that votes have come in. It seems to be a well supported idea. Please let me know if you have any questions.

[nairdo]

Hi Zack @zackdutra The team evaluates submissions based on factors like support, feasibility, alignment with core goals, and vote count. While I’m not directly involved in that process, I can assure you that your idea will receive the careful consideration it deserves.