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
memory-bank/productContext.md
+17 -3
View File
@@ -26,6 +26,7 @@
## Business logic patterns visible in code
- Case summary UI varies by appeal type and case attributes.
- Case status/progress display is portal-shaped rather than a raw CRM passthrough: the portal selects a journey catalogue from CRM `statuscode`, appeal type, and limited Rights of Way specialist-process input to present user-facing progress.
- Representation actions are conditionally shown by appeal type, role, and date windows.
- Representation participation now appears to form one broader business decision model: whether a participant can engage in representation or consultation activity for a case at that point in the process.
- Locale-sensitive behavior affects links, routes, labels, and email template choice.
@@ -40,11 +41,24 @@
- `docs/representation-participation-availability.md`
- `docs/representation-participation-business-review.md`
## Current case progress display state
- Technical investigation for CRM Case Progress Display is complete.
- Current behaviour is best understood as a **user-facing journey representation**, not a business-policy decision model.
- The Case Status tab is driven by:
- CRM `statuscode`
- appeal type
- specialist process for Rights of Way variants only
- `pinswg_casestage` should not currently be treated as a significant input to status-tab lifecycle behaviour.
- Shared catalogue families exist and reflect a mixture of:
- genuine shared journey structures
- presentation reuse
- historical consolidation
## Likely next discovery candidate
- Case Lifecycle / Status Decision Model Discovery
- expected focus: case progress, stages, statuses, closed states, dashboard grouping, and lifecycle messaging
- should be treated as discovery-only pending review of the new representation participation documentation
- No immediate successor discovery candidate is implied by the completed CRM Case Progress Display stream.
- If reopened later, work should focus on business validation or future behavioural change questions rather than first-pass technical characterization.
## Important user-facing behaviors