[V0.1] Create sample dataset for in-motion pension claims

[aplatt-coforma]

We want to validate the user data that will be provided to the VBA OIT group for manually setting the ITF date for:

1. Veterans who have an in progress pension form (between launch 1/31 and 'today')
2. Veterans who recently submitted a pension form (between launch 1/31 and 'today') - exclude those whose submission date is the same as the start date. Importing ITF would not change benefit effective date for those cases.

Tasks:

• Look for prior file that were generated for a similar task in Nov/Dec 2023: https://github.com/department-of-veterans-affairs/va.gov-team/issues/69157 https://github.com/department-of-veterans-affairs/va.gov-team/issues/64403

• Pull sample data in CSV file format representing both groups 1 and 2 above

• Coordinate with Sanja on this. Suggested data points to include:

  1. user identifier that makes sense to VBA (SSN, file number)
  2. Date/time form was started (UTC)
  3. 'vagov' as source of each row

Note: refer to linked ticket for details on how the batch will be run post launch

AC:

• Provide a sample dataset that VBA can validate and give the go-ahead on. This enables us to be ready to provide the full data set soon as V0 is launched to manually set ITF.
• Review batch ITFs in VBMS ProdTest - worth with P&F to validate. P&FS analysts or Emily can help (anyone with VBMS prod access)
• PII to be shared via Sharepoint

Open question:

• Can we use this method when there's a queue exhaustion and we are unable to set an ITF via API?

Prior reference: https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/teams/benefits/scripts/pensions/in-progress-forms.md

[sanjabaj2]

Should #2 also be for all submitted applications since Jan 31st? Last time the ITF upload process also included verification of any approved pension benefit to identify if an earlier ITF could be applied. So, maybe add submission date to the excel?

[buddhima-coforma]

Yes we can do that @sanjabaj2

Ref #85071

[aplatt-coforma]

Moved to Blocking column since we are waiting for feedback on our sample data pull.

[aplatt-coforma]

Closing now that the sample data has been provided. We've gone 100% with the v0 experience on PROD and monitoring for issues.

81413 will be the ticket that we use to track the actual PROD file pull. We are block on that ticket by 1 new request from Sanja. @mjknight50 will create the ticket for that new request and I will link to #81413