Skip to main content

CR Overview

This page is the landing page for CR-related business flows.

API Endpoints

No single designated endpoint.

Use child pages for exact routes such as:

  • POST /data/caution-report/create
  • GET /data/caution-report/all
  • GET /data/caution-report/by-id/:id
  • PUT /data/caution-report/update/:id
  • PUT /data/caution-report/update/status/:id
  • POST /data/caution-report/trigger/dispatch-tmf

What this section covers

Use the CR subsection when you need to understand:

  • how a caution report moves through its lifecycle
  • when CR data should be created, updated, or reviewed
  • when CR work should continue into TMF-related handling
  • which flowchart to open for a specific CR scenario

Best reading order

  1. start with the main CR diagram: CR Overview PDF
  2. read CR Lifecycle for the end-to-end flow
  3. read CR Creation for normal portal create behavior
  4. read CR GOTH Create for integration-driven GOTH create behavior
  5. read CR Notes for note read and create behavior
  6. read CR List Count for diagnose-code summary count behavior
  7. read CR Update Notes for note edit behavior
  8. read CR Ticket History for lifecycle and audit history behavior
  9. read CR NEPS Module for building lookup and polygon support behavior
  10. read CR to TMF Handoff for downstream TMF-related behavior
  11. read CR TMF Workorder Lookup for post-dispatch status and activity lookup

Main CR business topics

TopicUse it for
Lifecycleunderstanding create, view, update, notes, and status flow
List countunderstanding diagnose-code summary cards versus paginated list total
GOTH createunderstanding the external GOTH-sourced create path and duplicate handling
Note updateunderstanding when an edited note must also succeed in TMF
Ticket historyunderstanding timeline status history versus audit trail history
NEPS moduleunderstanding coordinate-to-building lookup in CR create flow
TMF handoffunderstanding when downstream TMF-related work should begin
TMF workorder lookupunderstanding live TMF reads versus local CR workorder history

Suggested next additions

  • CR creation rules
  • CR status transition matrix
  • note ownership and approval rules