-
Notifications
You must be signed in to change notification settings - Fork 19
Home
This wiki serves as a repository for all Caseflow technical documentation.
Target audience: Current and prospective team members and teams external to Caseflow who need to understand the product on a more detailed and specific level.
Documentation always runs the risk of getting out of date, because Caseflow is in constant development. So, this is a work in progress, and is a living document.
- By user
- By product
- By phase of the appeals process
- History/how did we get here
- Functionality & users
A suite of products that process VA appeals across two appeals systems (legislation) - legacy and Appeals Modernization Act (AMA).
Caseflow is a lot of different things, and will continue to evolve over time
- Form/data intake
- A case/task management system for many distinct users & roles, inside and out of VA
- Creates tasks for other VA systems, too
- Hearing scheduler (across many of variables)
- Document viewer and annotator
- Appeal system of record - centralizes Veteran and appeal data from disparate source systems
- API that shares Veteran and appeal data to other systems, including VA.gov for Veterans themselves
Caseflow is referred to as a suite of products. The longer we build it, the blurrier the lines among products become. Caseflow is the appeals processes in code.
-
Caseflow Intake - Form/data intake
- Issues
- Non-compensation queues
- Add/Remove/Edit issues
-
Caseflow Queue - Case/task management system
- Case details
- Queue table view
- Case timeline
- Case search
- Automatic case distribution
- Add/Remove/Edit issues
- Tasks
- Organizations
- Caseflow Reader - Document viewer & annotator
- eFolder Express
-
Caseflow Hearings
- Hearing Prep
- Hearing Schedule
- Appeal Status API - API to other systems, like VA.gov
Legacy appeals only:
- Caseflow Certification
- Form/data intake
- Caseflow Dispatch
- Front-End Architecture
- Work management
- Manager view
- Missing decisions
Non-user facing products:
- Caseflow Monitor
Go to www.demo.appeals.va.gov (Caseflow demo site) on GFE or via CAG and try various Caseflow users.
- Board data / Tableau team
- VA.gov (Appeals Status)
- Lighthouse API team
In addition to sprint teams, we have a few special-interest groups that Caseflowers participate in. They include:
- Backend Working Group
- Data Working Group
- Front-end Working Group
Additional documentation with improved formatting that automatically updates can be found on our Github pages site.
- 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
- Tier 4
- Bat Team
- Technical Documentation
- Backend Code Patterns
- Backend Working Group
- FACOLS, VACOLS DB Schema
- Asyncable Models
- External Data: where and why
- Data Fetching Scripts
- Caseflow Data Model and Dictionary
- User Access Permissions
- Controller Schemas
- Constants
- 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