-
Type: Story
-
Status: Closed (View Workflow)
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: CFA 2022R1
-
Component/s: None
-
Labels:None
-
SCRUM Team:Great White
-
Story Points:3
-
Work Type Classification:Sustaining
Feature Goals
The overall goal of this feature request is to send all the EOM data, including resending data that was already sent when when an individual section is updated/completed, when the EOM is marked.
The reason for this request is to help CFA solve a missing EOM data issue that they have been having. We know that InFORM is sending all the EOM data overall. Some of the data is sent when individual sections are completed and some of the data is sent when end of month is marked. It seems that CFA is losing some of the data that is sent before EOM is marked when we send out final EOM data payload when EOM is marked. The hope is that, by sending everything all at once, we can solve the case of the missing data.
Details
List of all service calls in the EOM process: https://cfacorp.atlassian.net/wiki/spaces/IN/pages/212730163/EOM+-+Web+Service+Calls
(Export of the above Confluence page)
EOM_Sent_Data.pdf
Additional Details
Oct 2021 - EOM Web Service call testing.docx
Acceptance Criteria
Confirm
- All EOM data is sent when EOM is marked including those data points that are not currently sent at EOM
- No data is omitted
- Existing data is sent as expected
- Nothing changes other than the mark EOM data sent.
- Confirm Swagger endpoints work in training.
- Clones
-
CFAMX-16842 EOM - Sending of all EOM data during final submission
- Closed
- implements
-
CFAMX-16838 EOM - Sending of all EOM data during final submission
- In Development
- is related to
-
CFAMX-16841 Documentation - EOM - Sending of all EOM data during final submission
- Closed
- relates to
-
CFAMX-18516 EOM MXC Staging - Slowness when Adding data to most sections and failures
- Done