Verify the selector against arrival, ordinary, departure, and lodge-transition CIS dates.
Before you start
- Act as
- A guide assigned to the test CIS
- Test data
- A CIS with arrival, ordinary, departure, and internal lodge-transition dates
Run the scenario
- 1GuideTrailhead Mobile · Calendar
Use two test CIS trips with the same Guide doing OUT and IN on one date. Check before and after creating half-day Programs, tap both halves, then compare identical lodge colors, an internal lodge transition, and an IN before the first stay.
Expected evidence
OUT is upper-left and IN lower-right. Each opens its own Program or selects the date for its group card. Same-color pairs retain separate agenda actions; internal transitions stay single-color; the early IN appears on its transfer date. Two IN duties, two OUT duties, a third assignment, or a full-day entry do not get the split.
- 2GuideTrailhead Mobile · Create Program
Open each CIS date and inspect the Program choices.
Expected evidence
For the transfer Guide, arrival shows IN only, IN + Fishing, and IN + POA; ordinary shows Fishing and POA; departure goes to OUT only; transition shows all three Transition variants.
- 3GuideTrailhead Mobile · Program review
Select each allowed variant and inspect its review context.
Expected evidence
IN/OUT show authoritative transfers, Fishing shows a Beat, POA shows its activity, and Transition shows both lodges and the read-only route.
Scenario completed
One valid Program variant is selected
- Program variant
- Not selected→Context-valid variant selected
If it does not match
- A missing or ambiguous IN/OUT transfer blocks submission and must be corrected in CIS.
- Fishing + OUT and POA + OUT are not supported variants. A full-day IN + Fishing or IN + POA cannot share a half-day OUT workload.