Skip to content

NextGen Checkin-Giving group choice and showing an inactive group #6206

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
2 tasks done
kimlongcr opened this issue Mar 4, 2025 · 1 comment
Closed
2 tasks done

Comments

@kimlongcr
Copy link

Description

If you have a group under an area that is inactive AND that group is still checked on a checkin configuration schedule, it will prompt them to pick a location. We have an Adventure Club area that used to have a bunch of groups under it. We changed from multiple groups to one so it now looks like this:
Image

However, when we inactivated the groups, they were still selected on the schedule (had to reactivate one to see this) :
Image

Even when marked inactive, if they are selected on the schedule, they are now showing up to pick within NextGen checkin:
Image

Actual Behavior

Being asked to checkin to a group that is inactive.

Expected Behavior

Only active groups show up in NextGen checkin to select.

Steps to Reproduce

Setup:

  • Create an area in a checkin configuration that has two active groups
  • Add both groups to the same schedule
  • Inactivate one of the groups

Test

  • Checkin a kid that meets the criteria of the active AND inactive groups in the checkin configuration you created
  • You'll be prompted to pick between the active room and the inactive one

Note: I tried for 30 minutes to recreate this in rmslatest but I couldn't even get checkin to work at all to let me check kids in to any room so I gave up

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

Rock McKinley 16.8 (1.16.8.1)

Client Culture Setting

en-US

@cabal95
Copy link
Member

cabal95 commented Mar 4, 2025

Hi @kimlongcr , I believe this is a duplicate of #6137 and has been fixed in 17.0.

As you probably already figured out, the temporary workaround is to remove the group from the schedule before you inactivate yet.

@cabal95 cabal95 closed this as completed Mar 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants