-
Notifications
You must be signed in to change notification settings - Fork 19
Substitute Appellants
In the unfortunate case where a veteran passes away before their case is resolved, a dependent (e.g., a surviving spouse or a child) can legally step into the shoes the veteran and continue on with the case. This can also happen after a case has been resolved and the case has been dismissed through a death dismissal. This dependent is referred to in Caseflow as a substitute appellant. (The process is sometimes called "Appellant substitution.")
(Note that this was initially referred to internally as "granted substitution" and there may be some lingering references to this. Early feedback was that this was confusing terminology, because the granting of the substitution was performed by a Regional Office, not by the Board. Entering a substitute appellant into Caseflow is not "granting" the substitution, and we therefore avoid that term.)
Only Clerk of the Board users may add a substitute appellant to an appeal. In dev or demo environments, the "Clark Bard" user (COB_USER) can be used, and you can search for the file number 54545454.
Information on Substitute Appellants is stored in the AppellantSubstitution
model.
Here is a chart that shows different scenarios in which an appellant substitution may occur.
A same appeal substitution is when an appeal's information is updated after the appellant substitution occurs, but no new appeal is created. In this scenario, the appellant substitution object's source_appeal
and target_appeal
are the same object.
A separate appeal substitution is when a new appeal is created after the appellant substitution occurs. In this scenario, the appellant substitution object's source_appeal
and target_appeal
refer to separate objects.
For pre-dispatch and post-dispatch there are different checks.
Each pre and post-dispatch checks require all bullet points in addition to the general checks to be true
- does the appeal support substitution?
- is it an AMA appeal?
- is the appellant the veteran?
- is the case type “original”?
- does the appeal not have a substitution?
- is one of user’s organizations Clerk of the Board?
- is feature toggle listed_granted_substitution_before_dismissal enabled?
- is the user a COB Admin or is veteran appellant is deceased?
- veteran has a date of death and appellant is veteran?
- is the user a COB Admin or does the appeal have any decision issues with “Dismissed, Death”?
- 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