robbond/pedwfrontend
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merged PR 2404: case stage analysis

Browse Source 
Related work items: #23754
This commit is contained in:
Robert Bond
2026-06-18 16:02:40 +00:00
parent 81a6276f44
commit 60a2ff4594
6 changed files with 941 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
context/current-platform-state.md
+26 -4
View File
@@ -17,6 +17,8 @@ PEDW is in a **late-stage refactor stabilization** phase.
- Broad endpoint contract hardening completed across key clusters.
- Representation Participation Availability investigation completed from a technical discovery/documentation perspective.
- Representation participation behaviour is now documented as one coherent decision model with layered appeal-type, specialist-process, participant-type, consultation, and date-window exceptions.
- CRM Case Progress Display investigation completed from a technical discovery/documentation perspective.
- Case Status tab behaviour is now understood as a portal-owned journey interpretation layer driven by CRM `statuscode`, appeal type, and Rights of Way specialist-process routing.
- Source documents added:
- `docs/representation-participation-availability.md` (developers / architects / maintainers)
- `docs/representation-participation-business-review.md` (business / product / SME validation)
@@ -51,8 +53,28 @@ Top active risks:
- Known divergences and compatibility-sensitive behaviours are documented and should be preserved unless an explicit business decision authorizes change.
- Current state: awaiting business validation of `docs/representation-participation-business-review.md` before any further representation-policy adoption, expansion, or behavioural change work.
## Next likely discovery candidate
## CRM Case Progress Display — Current State
- **Case Lifecycle / Status Decision Model Discovery**
- Investigate how the portal interprets case progress, stages, statuses, closed states, dashboard grouping, and user-facing lifecycle messaging.
- Treat this as discovery only until the new representation participation documentation has been reviewed and business validation feedback is available.
- Technical investigation stream is complete.
- Current architectural conclusion: do **not** treat this area as a new business-policy domain boundary.
- The Case Status tab is best understood as a **portal-owned journey interpretation layer**:
- inputs: CRM `statuscode`, appeal type, specialist process (Rights of Way only)
- resolution model: journey catalogue selection -> user-facing journey representation
- `pinswg_casestage` is not a significant active input to the current status-tab model:
- it was historically associated with DNS/SIPS summary support
- it is not part of active lifecycle resolution for the status tab
- Stage catalogues are best understood as:
- user-facing journey models
- appeal-type interpretation models
- presentation-layer progress visualisation
- Shared catalogue families exist (`PLANNING_S78`, `ENFORCEMENT`, `DNS/SIP`, Rights of Way specialist-process variants) and represent a mixture of:
- genuine shared journey structures
- presentation reuse
- historical consolidation
## Discovery candidate update
- Case Lifecycle / Status Decision Model Discovery is no longer an open next-candidate investigation.
- Current conclusion from the completed CRM Case Progress Display stream:
- this area is primarily presentation architecture + journey interpretation
- further work should only be reopened if a new business-validation or behavioural-change question emerges