Prove both sides of the license gate on a safe test Program: one rejected attempt and one eligible retry.
Before you start
- Act as
- An assigned Guide on a real test device
- Program
- A safe upcoming Fishing day with no existing Program
- License setup
- One selected Beat requires a Guide-held license absent or invalid on that date
Run the scenario
- 1GuideTrailhead Mobile · Create Program
Select the test Beat and send the Program once.
Expected evidence
Creation is blocked with localized guidance plus human Guide, license, and Beat labels.
- 2OperationsTrailhead Management · Programs and CIS history
Confirm the rejected attempt created no Program or downstream record.
Expected evidence
Program, allocation, reminder, notification, and CIS timeline remain unchanged.
- 3OperationsTrailhead · Guide and Access records
Add a matching valid holding or choose another eligible Guide or Beat.
Expected evidence
The source records now satisfy every Guide-held requirement on the Program date.
- 4GuideTrailhead Mobile · Program review
Refresh and send the corrected draft once.
Expected evidence
Exactly one Program is created and proceeds to its normal readiness or conflict result.
Scenario completed
Invalid write blocked and eligible retry accepted
- Invalid Program draft
- Ready to send→Blocked with exact license action
- Corrected Program draft
- License-ready→Program created once
If it does not match
- Use a safe test day and source records; do not remove a real operational license requirement to make the retry pass.
- If the invalid attempt creates any downstream record, stop and preserve the evidence as an atomicity failure.
- The rejection is non-retryable until eligibility changes; do not tap repeatedly or create a replacement Program.