GOAABox

Project Stage Tagging — UAT Guide

Test Identified Readiness / Construction Phase stamps on Issues, Risks, and Tasks, plus Task Blocking, layouts, list views, and reports in GOAABox.

Contents

1. Create Issue from Project via quick action

Automation stamps phases on create when Project is set and the as-of date is today (it uses the project's current phases). Quick action: New Issue (Log_Issue).
  1. Open Sample P1X-Style Project (Readiness = Organizing, Construction = Planning).
    Open project
  2. On the record page action bar (top right), open the actions menu if needed (▼ / Show more actions) and click New Issue.
    If you don't see New Issue Confirm you are on the GOAA Project Page Lightning page and your profile has the Project quick action Log_Issue. Admins: App Builder → GOAA Project Page → Mobile & Lightning Actions.
  3. In the create panel, enter:
    • Issue Name: UAT Stamp Issue — Sample (do not use a Post Opening prefix)
    • Date Identified: today (or leave the default if prefilled)
    • Project should already be the current project
    Save.
  4. After save, Salesforce usually opens the new Issue. If not, open the Issues related list on the Project and click the one you just created.
  5. On the Issue record, find the fields near Project / Date Identified (Stakeholder Issue layout): Identified Readiness Phase and Identified Construction Phase.
    Expected: Readiness = Organizing, Construction = Planning, Source = Automation, Confidence = Medium.
  6. Prefix test: create another Issue named Post Opening - UAT prefix on the same project.
    Expected: Identified Readiness = Post-Opening, Source = Prefix, Confidence = High (prefix wins over current phase).

2. Create Risk from Project via quick action

Same stamping rules; the as-of date is CITIRI__Log_Date__c. Quick action: New Risk (Log_Risk).
  1. Stay on Sample P1X-Style Project (or reopen it).
    Open project
  2. From the action bar, click New Risk.
  3. Name: UAT Stamp Risk — Sample. Confirm Log Date is today. Save.
  4. Open the new Risk from the save redirect or the Project Risks related list.
  5. On the Stakeholder Risk layout (near Project), check Identified Readiness / Construction Phase.
    Expected: Readiness = Organizing, Construction = Planning, Source = Automation.

3. Create Task from Project via quick action

Standard Task (not Project Task). Quick action: New Task. As-of date is Date_Recorded__c. Also covers the Blocking checkbox.
  1. On Sample P1X-Style Project, click New Task in the action bar.
    Open project
  2. Subject: UAT Stamp Task — Sample. Set Status / Due Date as required by the layout. Check Blocking if it appears on the create form; otherwise set it after save. Save.
  3. Find the Task via the Project's Activity related list, or the Tasks tab.
  4. On the Task layout, check Identified Readiness / Construction and Blocking.
    Expected: Readiness = Organizing, Construction = Planning, Blocking checked.

4. Edit stamps on existing records

Users with the GOAA Phase Stamp Edit permission set can manually override any stamp. These are real backfilled records whose stamps match their project, so an override is easy to spot. Automation only re-stamps when Project or the identified/log/recorded date changes — editing the phase by hand sticks.
RecordProjectCurrent stampOpen
Issue — Level 4 demising wall dependency Terminal C P1X Gates 250-253 Transition / Substantial Completion Open
Risk — CBP Approval Delay Terminal C P1X Gates 250-253 Transition / Substantial Completion Open
Task — ADA door force testing Terminal C P1X Gates 250-253 Transition, Blocking = false Open
Issue — Kim Boots Sample Issue CitiriOS Training Organizing / Planning Open
  1. Open Level 4 demising wall dependency and click Edit. Change Identified Readiness Phase from Transition to Activation. Save.
    Open Issue
    Expected: save succeeds and the value stays Activation — automation does not revert it.
  2. Open CBP Approval Delay and change Identified Construction Phase to a different value (e.g. Construction). Save.
    Open Risk
    Expected: the manual value persists.
  3. Open ADA door force testing, check the Blocking checkbox, and Save.
    Open Task
    Expected: Blocking = true; this task now appears in the Open Blocking Tasks list view and report.
  4. Re-stamp check: on Kim Boots Sample Issue, change the Project to Terminal C P1X Gates 250-253 and Save.
    Open Issue
    Expected: stamps re-calculate to Transition / Substantial Completion because the Project changed.

5. List views

List views support stage filtering without a dashboard in v1.
  1. Issues — check both stamp views.
    Issues — Needs Identified Phase Issues — By Identified Readiness
    Needs view: 12 issues with blank readiness (these have no project phase to inherit). By Readiness: columns show both stamp fields.
  2. Risks — same two views.
    Risks — Needs Identified Phase Risks — By Identified Readiness
    Needs view: 7 risks with blank readiness.
  3. Tasks — blocking and cleanup views.
    Tasks — Open Blocking Tasks — Needs Identified Phase
    Open Blocking starts empty — it fills once you check Blocking in step 4 (and on your new UAT task).

6. Reports

Four reports are deployed in the GOAA Phase Stamp Reports folder (public, all internal users). v1 reporting is standard reports — no dashboard.
All Reports
ReportWhat it showsOpen
Issues by Identified Readiness Phase Issues grouped by the readiness phase at identification, with construction phase, source and confidence. Run
Risks by Identified Readiness Phase Same grouping for Risks, based on Log Date. Run
Open Blocking Tasks by Owner Tasks where Blocking = true and Status ≠ Completed, grouped by assignee. Run
Issues Needing Identified Phase Cleanup queue — issues still blank after backfill. Run
  1. Run Issues by Identified Readiness Phase and confirm the groupings match the current data spread (Organizing 49, Transition 17, Completed 14, Activation 7, and so on).
  2. Run Open Blocking Tasks by Owner after checking Blocking in section 4.
    Expected: the task you flagged appears under its owner.
  3. Run Issues Needing Identified Phase and compare the count to the Issues "Needs Identified Phase" list view — they should agree.

7. Re-running the historic backfill

Already run — Issues, Risks, and Tasks are stamped. Because the project phase fields have no field history yet, historic rows inherit the project's current phase and are marked Confidence = Low. Records whose project has no phase are left blank so they stay in the cleanup queue. As phase history accumulates, re-running will upgrade those rows to ProjectHistory / High.
  1. Assign yourself the GOAA Phase Stamp Backfill permission set, run the batch, then remove the assignment — it grants Bypass_Phase_Stamp, which turns off live stamping for that user while assigned.
    Permission Sets
  2. Run in Developer Console → Debug → Open Execute Anonymous Window: 
    Database.executeBatch(new PhaseStampBackfillBatch('Issue', true), 200);
Database.executeBatch(new PhaseStampBackfillBatch('Risk', true), 200);
Database.executeBatch(new PhaseStampBackfillBatch('Task', true), 200);
    The second argument is overwriteExisting — use false to fill only blanks and preserve manual overrides.
    Monitor Apex Jobs
  3. Spot-check a Terminal C P1X record — readiness should read Transition, matching that project.
    Open Terminal C P1X Gates