-
Type: Improvement
-
Status: Done (View Workflow)
-
Priority: Major
-
Resolution: Completed
-
Affects Version/s: CFA 2020R3
-
Fix Version/s: CFA 2020R3
-
Component/s: AWS, Forecasting
-
SCRUM Team:Brotherhood of Mutants
-
Sprint:CFAMX 2020R3 Sprint 5, CFAMX 2020R3 Hardening
As a support team member who is investigating missing forecast data I want an audit log to be written that is a part of the Forecast Status call so that when an issue is reported I can have more data available to me to troubleshoot the issue
Notes
- We need to track the web service response that we receive the Forecasting Status call so that we can investigate where things are failing
- Right now, we don't know whether messages are failing on our side, if the files are not being presented to us, or if the files that are being presented to us are out of date.
- Can we insert, as an audit record, the following details:
- Business Day
- Generation Date - From AWS, the status response
- External Generation Date - From our database
- Having these 3 values would allow us to figure out:
- What data was returned to us
- Whether we already had the forecast or not
- Should we have imported the forecast or not
Acceptance Criteria
- Confirm that after running the Forecast Import process, the details contained in the response from the Status call are written as an audit record
- Confirm that the audit contains:
- ** Business Day
- Generation Date - From AWS, the status response
- External Generation Date - From our database
- Is Clone Of
-
CFAMX-10173 CLONE 2020R2.1 - Add logging to track the Status response of the Forecast API call
- Done