Schedule Exclusions (on the Category) Issue with Classic Check-In

[MarkCotterman]

Description

We found an issue with Schedule Exclusions in the Classic Check-In that does not seem to be an issue with Next Gen Check-In. This was not an issue with Classic Check-In until we noticed it recently.

• Classic Check-In, Schedules with Exclusions still are available in the Classic Check-In process. This is not expected and has not been the case in the past. And once a child is checked in they cannot be checked out if there is an Exclusion.

• Next Gen Check-In. Schedules with Exclusions do not show as available for check-in using the Next Gen Check-In process, as expected.

Actual Behavior

Actual Behavior
Schedule is setup with an Exclusion for today. Using Classic Check-In the Schedule is available for Check-In.

Testing is taking place on 2/26/2025. Here is the Exclusion.

Here is the Schedule where you can see the date and the Exclusion

Here you can see the Classic Check-In allowed me to check into this Exclusions Test Schedule even though it has an Exclusion on it.

We have Check-In Configuration set to allow Check-Out. Once the above check-in is complete I go back through the Check-In kiosk and I am not offered the opportunity to Check-Out my child. I get the following message.

However, If I remove the Exclusion, the Check-Out Process Works. Here are the Screen prints allowing me to Check-Out using Classic Check-In with no Exclusions on the Schedule. So the Exclusion is letting me check-in when I should not be able to. Then it is not letting me Check-Out which is probably the correct behaviour if the system should not allow check-in to begin with.

If I go through the same exact process with Next Gen it works as expected for Check-In and Check-Out. I receive a message that I cannot check-in my kid.

If I remove the Exclusion and rerun Next Gen Check-In I am able to check-in my child, which confirms it is the exclusion that is making the child ineligible.

Then when I go back through the process in Next Gen it allows me to check out the child I just checked in.

Expected Behavior

Expected Behavior
The expected behaviour is how the Next Gen Check-In works as explained above. If there is an Exclusion a child cannot be checked into that Schedule.

Steps to Reproduce

• Add an exclusion to an active schedule that is setup in Checkin Configuration
• Use Classic Check-In to check in a child
• The child will be able to check in
• Then go back through the process and try and check out the child and you are not able to
• Follow these same steps with Next Gen and you are not able to Check-In with the Exclusion in place, as expected

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 Version: Rock McKinley 16.8 (1.16.8.1)

Client Culture Setting

en-US

[KarenRossi84]

@MarkCotterman we are on 16.8 and I am trying to trigger this to happen in our environment but so far have not been able to re-create it. In my tests the children were not able to check into classic check in when an exclusion was added.

I do notice that your screenshot pictures do look quite different than ours. Is it possible you are using a custom block by chance?

For instance, this is what the block looks like when we are creating a new schedule.

I see that your schedule above appears to be a one-time schedule but I can only add exclusions to recurring schedules.

If you are not using a custom block maybe you can point me in a different direction to reproduce. We are using the obsidian schedule detail block. This could really bite us on Easter if it is happening.

[MarkCotterman]

@KarenRossi84 Hi Karen, After reviewing your comment I went back and checked the behavior when an exclusion is created on the Schedule (rather than the Schedule Category) and that seems to work fine in both Classic and Next Gen.

We have many Schedules so we put our Exclusions on the Category level. Below is a screen print that provides a visual of what I am talking about. If you go to the Category level where your schedules are listed and you enter an exclusion to be applied to all schedules in that category I expect you will have the same issue. If you only put exclusions on the Schedules themselves, that seems to work fine. Here is what an exclusion looks like on the Category level.

If I am seeing your screen correctly, here is what an exclusion looks like within a specific schedule that I think you must be using.