-
Notifications
You must be signed in to change notification settings - Fork 19
Hearing Postponement Request Mail Task
Hearing postponement requests are requests for a hearings user to reschedule a hearing to a later date. When requests get received from the mail portal there must be a way to route this to the hearing admin so they can process this request efficiently. Hearing postponement request mail tasks are made for this purpose.
Once a request gets received, a user from the MailTeam organization must go into the corresponding appeal and create a new HPR task. Once this task gets selected from the task dropdown they will be required to input a valid link to the eFolder document in addition to the instructions before they are able to create the task. You will not be able to submit it if the url does not correspond to an existing document
Once an HWR Task gets created a hearings admin will be able to act on it by completing it, reassigning the task, changing the task or just cancelling it. If the user marks it as complete they will need to input whether or not the judge granted or denied the request and the date of the ruling. If the ruling is granted then the user will have the option to either reschedule immediately or send it back to the schedule list to reschedule it at a later point.
The task on creation will associate with the latest hearing task. If the hpr task gets completed this will create a whole new hearing task with either its own schedule hearing task or assign disposition task depending on if it got rescheduled or not. If the associated hearing is postponed in any other way, this will close out the current hpr task.
)
- 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