-
Notifications
You must be signed in to change notification settings - Fork 19
Hearings Task Trees
Disclaimer: There are exceptions to all of these cases in the data. The visualizations and descriptions below are meant to be illustrative, not exhaustive.
HearingTasks are parented by a RootTask (legacy appeals) or a DistributionTask (AMA appeals). A distribution or root task can have many hearing task children.
A HearingTask has only one ScheduleHearingTask child.
Note: In the following diagrams the DistributionTask or RootTask parent is generally left out unless it's relevant to the action being described (as is any other part of the appeal's task tree). For simplicity the diagrams always show a DistributionTask as the HearingTask's parent.
Scheduling a hearing completes the ScheduleHearingTask and creates an AssignHearingDispositionTask as a child of the HearingTask.
Selecting the "Held" disposition for a hearing puts the AssignHearingDispositionTask on hold and creates a TranscriptionTask as a child of it.
AMA appeals also have an EvidenceSubmissionWindowTask opened for 90 days and assigned to the Mail organization (unless the appellant waives it).
Note: The HearingDispositionChangeJob will run everyday in UAT and Prod. In Local and Demo, it will need to be manually run in order to update hearings held in the past and create these child Tasks.
Selecting the "Postponed" or "Scheduled in error" disposition cancels the AssignHearingDispositionTask and the parent HearingTask. It also creates a new HearingTask and child ScheduleHearingTask, which might get completed shortly thereafter if the user reschedules immediately.
Selecting the "No show" disposition creates a NoShowHearingTask, which goes on hold along with its parent for up to 15 days.
If after 15 days a user has not already cancelled or completed the task with an action, the TimedHoldTask, parent NoShowHearingTask, and grandparent AssignHearingDispositionTask are all completed. HearingTasks for legacy appeals will be completed at this point, but HearingTasks for AMA appeals will remain on hold while an EvidenceSubmissionWindowTask is opened for 90 days and assigned to the Mail organization.
Selecting the "Cancelled" disposition cancels the AssignHearingDispositionTask and the parent HearingTask. AMA appeals also have an EvidenceSubmissionWindowTask opened for 90 days and assigned to the Mail organization.
If a disposition hasn't been entered after 48 hours, Caseflow creates a ChangeHearingDispositionTask parented by the HearingTask and assigned to the Hearing Admin organization.
Hearings Management team members can also create a ChangeHearingDispositionTask with the "Send for hearing disposition change" action on some tasks (e.g., a no show hearing task).
When a judge or attorney adds an admin action to "Confirm schedule hearing", it creates a top-level ScheduleHearingColocatedTask (i.e., it has no parent).
When a user in the Hearings Management organization chooses the "Hearing does need to be scheduled" action it completes the ScheduleHearingColocatedTask and creates a HearingTask/ScheduleHearingTask parent and child for the appeal.
- 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