Gateway Replacement Workflow
Gateway Replacement Workflow
Lab: Gateway Replacement Workflow
A maintenance team adds NFC labels to gateways. A technician tap should open the correct gateway service record, show replacement steps, create an audit record, and allow replacement only when the work order and session permit it.
Lab Plan
Read the plan as a sequence of evidence handoffs. Begin with the objective and the approved HTTPS tag payload, then exercise both reader paths so the mobile and service-desk routes are not silently treated as equivalent. Next, apply every policy check before the replacement action: host, schema, released-tag record, technician session, work-order state, and idempotency each closes a different boundary. Run the listed failure tests after the successful path, because an unknown tag, duplicate tap, offline app, unsupported schema, or already-replaced gateway must produce an intentional result. Finish by collecting the decoded payload, decision, audit row, fallback result, and retest trigger as one release record. That order connects the lab to the chapter’s central claim: an NFC tap starts the workflow, while application policy decides what may happen.