-
Notifications
You must be signed in to change notification settings - Fork 18
Completing an intake
When an intake is completed, all data for that intake is saved in the Caseflow database and the user will be shown a confirmation screen which displays the outcome of the intake. The user may then take any follow up actions based on that result, such as mailing any required correspondence to the veteran. Caseflow will also begin to attempt to process any resulting actions in other VA systems.
- Creating one or more end products (EPs) in VBMS
- Creating contentions on each of those EPs
- Connecting those contentions to the rating issues they contest
- Closing one or more legacy appeal issues, and one or more legacy appeals.
These operations are complex and must be performed in a very specific order. They can also fail for a variety of system reasons. In order to maintain the integrity of these operations in spite of failures, retrying just the parts that failed and maintaining robust data about when they failed and for what reason, we process completed intakes as part of an asynchronous job. The full list of asynchronous jobs that have not successfully processed can be found at https://appeals.cf.ds.va.gov/jobs. An engineer should be monitoring and resolving these jobs daily. Additionally, any decision reviews that have not yet processed are visible on the the Caseflow search page.
- Home
- Acronyms and Glossary
- Caseflow products
- Caseflow Intake
- Caseflow Queue
- Appeals Consumer
- Caseflow Reader
- Caseflow eFolder
- Caseflow Hearings
- Caseflow Certification
- Caseflow APIs
- Appeal Status API
- Caseflow Dispatch
-
CSUM Roles
- System Admin
- VHA Team Management
- Active Record Queries Resource
- External Integrations
- Caseflow Demo
- Caseflow ProdTest
- Background
- Stuck Jobs
- VA Notify
- Caseflow-Team
- Frontend Best Practices
- Accessibility
- How-To
- Debugging Tips
- Adding a Feature Flag with FeatureToggle
- Editing AMA issues
- Editing a decision review
- Fixing task trees
- Investigating and diagnosing issues
- Data and Metric Request Workflow
- Exporting and Importing Appeals
- Explain page for Appeals
- Record associations and Foreign Keys
- Upgrading Ruby
- Stuck Appeals
- Testing Action Mailer Messages Locally
- Re-running Seed Files
- Rake Generator for Legacy Appeals
- Manually running Scheduled Jobs
- System Admin UI
- Caseflow Makefile
- Upgrading Postgresql from v11.7 to v14.8 Locally
- VACOLS VM Trigger Fix M1
- Using SlackService to Send a Job Alert
- Technical Talks