feat: Update daily logs and work item documentation for PDIAP-15765 and add new daily entry for 2026-04-17

This commit is contained in:
2026-04-17 07:37:33 -06:00
parent 374991a568
commit a1cec956ab
5 changed files with 39 additions and 16 deletions

View File

@@ -4,7 +4,7 @@ project: fidelity
date: 2026-04-16
focus: [ao-discourse, xflow-debugging]
work-items: [pdiap-15765]
blockers: [code-owner-approval-required]
blockers: []
updated: 2026-04-16
tags:
- daily
@@ -41,3 +41,6 @@ tags:
- Jeff asked Rashmi to revert the Youth-flow service change so the iOS-side PR can remain the single fix path for that issue.
- David confirmed Rashmi reverted the QA change by publishing the earlier flow version, and local Fid4 validation with the iOS PR showed the `birthDate`-based validation now works as expected.
- Jeff's preferred external summary is now very explicit: we went back and fixed their original iOS-only issue on the iOS side, while the separate `HybridBrokerageAccountOpening` / `JointIdentityCheck` issue is a new service-side problem that still needs its own follow-up.
- The `PDIAP-15765` PR later received final approval, was merged, and the release pipeline produced XFlow `2.8.48`.
- After the XFlow release, David updated XFlowViewMaker to `2.8.48`, opened the follow-up PR, and sent it for review so the fix can propagate through the consumer path.
- David also sent the final AO working-group update with links to the Jira story, Discourse ticket, and PR.

View File

@@ -0,0 +1,21 @@
---
type: daily
project: fidelity
date: 2026-04-17
focus: [ao-discourse, consumer-integration, rest-migration]
work-items: [pdiap-15765, pdiap-15838]
blockers: [xflowviewmaker-code-owner-approval]
updated: 2026-04-17
tags:
- daily
- fidelity
---
# 2026-04-17
## Standup Draft Clarification
- David clarified that the XFlowViewMaker follow-up work for `PDIAP-15765` is further along than the earlier summary implied.
- The XFlowViewMaker PR is already open and has some approvals.
- One code-owner approval is still required before the PR can merge.
- After that approval, the remaining work is to run the pipeline and update Fid4 so the XFlow `2.8.48` change propagates through the consumer path.
- `PDIAP-15838` remains the next story after the `PDIAP-15765` propagation steps are in a good place.