CVG · Command Center

Work Requests — Test Walkthrough

An end-to-end script to validate the Construction Impact intake, tracker, PMO board, and triage on the live Experience site. Follow each scenario in order; every scenario lists exact steps, the data to enter, and the expected result.

Environment: CVGBox sandbox · Site: Command Center (Live)

≡Scenarios

0 · Pre-flight checks

Reference test data

A · Guest submits an impact (happy path)

B · Form validation

C · Photo upload

D · Track a request (success)

E · Track a request (negative)

F · PMO board (Kanban)

G · PMO triage / dispatch

H · Tracker reflects PMO response

I · Guest security negative test

0Pre-flight checks

Confirm these once before testing. The first two are the usual reasons a guest submission fails.

#CheckWhereStatus
1Guest User has the Command Center Impact Guest permission setSetup → Users → Command Center Site Guest User → Permission Set AssignmentsVerified ✓
2Reassign guest-created records to a default owner is enabled, and Request has a default owner (user or queue)Setup → Digital Experiences → SettingsVerify
3Construction Impact record type is available & default on the Guest User Profile for RequestSetup → Profiles → Command Center Profile → Object Settings → RequestsVerify
4Site is Active and pages are PublicDigital Experiences → Command CenterVerified ✓
Why #2 matters: with "Secure guest user record access" on, guests can't own records. If no default owner is set for Request, the submission in Scenario A will fail with an ownership/insufficient-access error.

◔Reference test data (seeded in CVGBox)

Use these known-good values. Four sample requests were pre-seeded through the real intake service so the tracker and board have data on day one.

Pick-from values for a new submission

FieldUse this value
ProjectPhase 1 - TMP (has 8 stakeholder companies)
Company / TenantAmerican Airlines · United Airlines · Frontier Airlines · Clear (or “Other / not listed”)
Facility → Level → ZoneConcourse B → Boarding Level → Concourse B - Boarding

Pre-seeded requests (for tracker & board)

Tracking #Reporter emailStatusPriorityCompanyType
REQ-0070walkthrough.tester@example.comNewMediumAmerican AirlinesNoise / Vibration
REQ-0071sample.reporter1@example.comUnder ReviewHighUnited AirlinesDust / Air Quality
REQ-0072sample.reporter2@example.comIn ProgressMediumFrontier AirlinesAccess / Wayfinding
REQ-0073sample.reporter3@example.comResolvedLowClearUtility Interruption

AGuest submits an impact — happy path Guest · Mobile

Open Report page ↗ Open in an incognito window
  1. Open the Report page. The header reads “Report a Construction Impact.”
  2. Select Project = Phase 1 - TMP. The Company picklist should now enable.
  3. Select Company / Tenant = American Airlines.
  4. Enter Your name = Taylor Tenant, Email = your.email@example.com (use an address you can recognize), Mobile optional.
  5. Set the location: Facility = Concourse B → Level = Boarding Level → Zone = Concourse B - Boarding.
  6. Select Type of impact = Noise / Vibration.
  7. What's happening? = Jackhammering above Gate B12 during boarding.
  8. Affected areas / details = a sentence describing the impact.
  9. Tap Submit report.
Expected: a confirmation screen appears — “Request received” — showing a tracking number (e.g. REQ-00xx) and a “New” badge. Write down the tracking number and the email you used for Scenario D.
Pass / Fail — notes: __________________________________

BForm validation Guest

  1. On a fresh Report page, tap Submit report immediately without filling anything.
  2. Try submitting with a Project selected but no “What's happening?” text.
  3. Enter an invalid Email like not-an-email and try to submit.
  4. Clear the Project selection and confirm the Company picklist is disabled.
Expected: Submit stays disabled / blocks until Project, a valid Email, and “What's happening?” are all provided. Company is disabled until a Project is chosen.
Pass / Fail — notes: __________________________________

CPhoto upload Guest

  1. Fill the form as in Scenario A but before submitting, use Take Photo (mobile) or Library to add 1–2 images.
  2. Confirm thumbnails appear and the counter reads Photos · N. Remove one with the ✕ button.
  3. Submit the report.
  4. As PMO, open the new record (Scenario F/G) and confirm the photos are attached under Files / Related.
Limits: image files only, ≤ 5 MB each, up to 10 photos, attached within 30 minutes of creating the request.
Pass / Fail — notes: __________________________________

DTrack a request — success Guest

Open Tracker page ↗
  1. Open the Tracker page.
  2. Enter tracking number REQ-0070 and email walkthrough.tester@example.com (or your own number/email from Scenario A).
  3. Submit the lookup.
Expected: the request’s status (New), impact type, location, priority, submitted date, and a status timeline appear. No login was required.
Pass / Fail — notes: __________________________________

ETrack a request — negative Guest

  1. On the Tracker, enter REQ-0070 with the wrong email (e.g. nobody@example.com).
  2. Then try a made-up number like REQ-99999 with any email.
Expected: a friendly “not found” message both times — never another tenant’s data. This proves the ref + email gate and prevents enumeration.
Pass / Fail — notes: __________________________________

FPMO board (Kanban) PMO · Internal

Requires internal setup: the commandCenterBoard component must be placed on a Lightning App/Home page or tab (see Experience_Site_Setup.md §6a) and the tester must have the Command Center PMO permission set. If the board isn’t placed yet, use the “All Requests list” link and Scenario G instead.
  1. Log into CVGBox as a PMO user and open the Command Center Board.
  2. Confirm four columns — New / Under Review / In Progress / Resolved — populated with the seeded requests (REQ-0070…0073) plus any you submitted.
  3. Check the metric tiles (total, open, high-priority).
  4. Drag a card from New to Under Review.
Expected: the card moves columns and the underlying Command Center Status updates (refresh to confirm it persists).
Pass / Fail — notes: __________________________________

GPMO triage / dispatch PMO · Internal

Open REQ-0070 ↗
  1. Open a Construction Impact request (e.g. REQ-0070).
  2. Launch the Impact Triage action (record page action) — or edit the fields directly if the action isn’t added to the layout yet.
  3. Set Command Center Status = In Progress, Command Center Priority = High, choose an Assignee, and enter a Response note like Crew scheduled tonight; barrier being relocated.
  4. Save.
Expected: the record shows the new status, priority, assignee, and response note. On the board the card reflects the change.
Pass / Fail — notes: __________________________________

HTracker reflects the PMO response Guest

  1. Go back to the Tracker as a guest and look up REQ-0070 + walkthrough.tester@example.com again.
Expected: the status now shows In Progress and the latest PMO response note is visible to the tenant — closing the loop from Scenario G.
Pass / Fail — notes: __________________________________

IGuest security — negative test Security

  1. In the incognito (guest) window, paste an internal record URL, e.g.
    https://citiri-cvg--cvgbox.sandbox.my.site.com/command/s/detail/a1lWA000000xHuTYAU
  2. Also confirm there is no public list of all requests anywhere on the site.
Expected: the guest cannot open any Request record directly — only the ref + email tracker returns data, and only the matching record. No sharing rule exposes Requests to guests.
If a guest can open a record or see a list of all requests — stop and report it. That indicates a guest sharing rule or an over-broad permission was added; it must be removed.
Pass / Fail — notes: __________________________________