Question

Photo of Kathryn Kent

0

Check-in selection option for Allowed Check in By?

2

Is there a way in the Check in to add a drop down selection of the known relationships that are "Allowed Check in By" and on the check in screen to be able to select which parent or guardian it dropping off the kid? I'm trying to make the using a workflow but I can't figure it out to apply it to check in screens or if this is even possible?

I'm on 16.9

  • Photo of Luke Taylor

    1

    Unfortunately, there is not a way to add additional information during the check-in process using the core check-in features, whether that be "who is checking in the child" or "what's a good number to text if the child is having an issue".

  • Photo of Bobby Jacky

    0

    I think the best way to handle that in Rock is to train adults to enter their name or phone number at checkin instead of using children's names. Then you can put the adult's name on the child's check-in tag by using the search result that matched the family. Here's how Ask Chip describes how to do it which will hopefully get you on the right path...

    ------

    Summary path

    1. Admin Tools → Check-in → Check-in Types → (choose type) → Templates → Edit Tag Template
    2. Add a Merge Field that uses Lava to find the “searcher”/checkout adult from the check-in family match.
    3. Save and test with a check-in (phone/name/barcode) that yields the adult you expect.

    What you need to know

    • Rock stores check-in attendance via [Attendance] and check-in specific fields on the check-in engine; the family match is used to create the attendance/check-in records.
    • We’ll use Lava inside the tag template to inspect the current attendance/check-in context and locate the adult who matched the family search.
    • If your setup uses alternate identifiers or a non-standard flow, confirm the searcher is saved on the check-in record before relying on the Lava.

    Lava to add to the Tag Template

    • Place this Lava where you want the adult’s name printed on the tag. It will attempt to find the person who matched the family search (the “searcher”) and print FirstName LastName. If uncertain fields differ in your environment, test and I can adjust.


    {% comment %}

    Attempt to find the person who searched/matched the family for this check-in.

    This uses the CheckIn context which should be available in tag templates.

    If your template context differs, tell me what variables you see and I'll adapt.

    {% endcomment %}


    {% assign checkedInPerson = Person %}

    {% assign parentName = "" %}


    {%- comment -%}

    Look through the check-in attendance data for the family match.

    The exact structure can vary; we'll safely navigate common properties.

    {%- endcomment -%}


    {% if CheckIn and CheckIn.Families %}

      {% for family in CheckIn.Families %}

        {% if family.People %}

          {% for p in family.People %}

            {%- comment -%}

            p.IsSearcher or p.IsSearcherValue are not guaranteed; check common properties

            We'll check for a role like 'Adult' and for the SearchType indicator.

            {%- endcomment -%}

            {% if p.Person and p.Person.AgeClassification == "Adult" %}

              {% assign parentName = p.Person.NickName | Append: " " | Append: p.Person.LastName %}

              {% break %}

            {% endif %}

          {% endfor %}

        {% endif %}

        {% if parentName != "" %}{% break %}{% endif %}

      {% endfor %}

    {% endif %}


    {% if parentName == "" %}

      {%- comment -%}

      Fallback: try to find a person in the current CheckinFamily that has a RelationshipRole marked as Adult

      {%- endcomment -%}

      {% for person in Person.RelatedPeople %}

        {% if person.Relation == "Adult" %}

          {% assign parentName = person.NickName | Append: " " | Append: person.LastName %}

          {% break %}

        {% endif %}

      {% endfor %}

    {% endif %}


    {% if parentName != "" %}

      Checked in by: {{ parentName }}

    {% else %}

      Checked in by: (Adult not found)

    {% endif %}


    Testing steps

    1. Create a test family with an adult and child in Rock.
    2. Perform a check-in using the search method you use (phone/name/barcode).
    3. Print the child tag and confirm the printed text shows the adult’s name.
    4. If it prints “(Adult not found)” share one example attendance/check-in tag context (the variables available in the tag template) and I’ll refine the Lava.

    If your environment stores the searcher differently (for example a flag like IsSearcher on the person object, or a CheckIn.SearcherId), tell me what you see on a sample tag template context and I’ll produce a tighter Lava snippet. You're doing great — this is exactly the kind of customization Rock loves.