OpenCyber Academy
Rapid course · Lesson 18 · English
Course code: OCA-004Lesson 18: OCA-004-A018

A returned phone field fails the field check

Open, free learning for anyone who wants to protect people and technology. No account is required to read this text or its worked answers.

Lesson map

Lesson 18 published. Map, example, EX072.

flowchart TD
  F["Two-week form: five fields"] --> P["A later screen shows phone again"]
  P --> X["Field check fails. The action opens"]
  X --> K["Do not assume the other four rejected names returned"]

One name coming back is a failure. It is not a census of the whole template.

Logical drawing

published lab
    phone marked NOT NEEDED on the ten-name file
two-week form
    five fields, phone absent
later screen
    phone is on the form again
        |
        +-- the field check fails
        +-- gender, postcode, prescription items and the location trail are not assumed back
        +-- the ten-and-five print is not edited

Learning outcomes

After this chapter, you should be able to:

  1. Treat a returned phone field as a failed field check.
  2. Leave the action open.
  3. Avoid assuming that every other rejected name returned with it.

18.1 The template can grow back one box at a time

Phone was one of the five names the published script marked NOT NEEDED. The two-week form no longer asked for it. A later sign-up screen shows a phone box again, which a colleague blames on the vendor's default template. The field check asks whether the rejected names are absent. Phone is not absent, so this screen fails. Sofia records the returned field and leaves the action open. She does not edit collected in the lab so that the historic print changes, and she does not write that gender, postcode, prescription items and the location trail have also returned. Those four are unknown until someone looks. This lesson looks only at the phone box that is actually on the screen.

18.2 Worked example

Lesson table; scroll horizontally to read all columns →

What the later screen shows Field check Decision
The five allowed names, phone absent Not this failure Do not invent a pass for other shops
Phone present again Fails Leave the action open
"The other four rejected names must be back too." Not observed Do not write that
Rewrite the published print as 11 names The original file Refuse

Synthetic case. No telephone number is written on the screen in this lesson.

Errors and limits

A failed field check does not describe the values inside purchase_history. The content check remains its own test, which Chapter 5 keeps tied to the file in front of her.

Apply

Worked answers

EX072. The field check fails and the action stays open. The published print stays 10 collected and 5 not needed. Do not assume gender, postcode, prescription items and the location trail returned.