-
Notifications
You must be signed in to change notification settings - Fork 19
Correspondence
The Correspondence page of Caseflow Queue was created to allow Caseflow Inbound Ops Team members and The Board to track and report items (like rejected appeals or correspondence) that relates to a particular Veteran/Appellant, even if no appeal is ultimately docketed, in Caseflow. This is to ensure the completeness and existence of uploaded records. For example, in VACOLS, we have a diary/mail tab that allows the Board to track correspondences even if it does not relate to a particular appeal. This can include, but is not limited to, Congressional inquiries, rejected 10182s and status requests.
This feature introduces a new top-level object aptly called "Correspondence" which is synonymous to the "Appeal" object in functionality, and serves as the root object that all subsequent documents and records are attached to.
- Correspondence Queue
- Correspondence Tasks
- Correspondence Statuses
- Review Package
- Intake Form
- Correspondence Details
- Auto-assign
- Split
- Merge
- Explain Page
A list of Veterans with Correspondence Cases can be accessed by an Inbound Ops Team User, Inbound Ops Team Superuser and an Inbound Ops Team Supervisor from the Caseflow Queue page. This landing page serves as the primary access point to the other Correspondence pages. The Correspondence Queue is a set of two different queues -- Your Correspondence
for the current users' correspondence tasks and Correspondence Cases
for a Supervisor or Superuser to view all Correspondence related tasks.
The Review Package page displays the General Information, and Documents associated with the selected Veteran. There are options a user can perform to edit, delete, and update the status of a Review Package and move it to the next step in the review process
The Intake form allows a user to associate a Correspondence with prior mail, add new tasks, and link a Correspondence to multiple existing appeals or create a new appeal to associate to.
Similar to Queue, Correspondence uses CorrespondenceTask objects to record and maintain the history of actions a specific Correspondence Case has undertaken, and where it currently sits in the review process. The CorrespondenceTask contains information regarding who assigned a task, who the task was assigned to, and the specific type of task to be performed.
This is overview of the tasks available for a Correspondence:
- Correspondence Root Task
- Review Package
- Split Package
- Merge Package
- Reassign Package
- Remove Package
- Intake
- Mail Tasks - This is a set of tasks adding during Intake that are automatically marked completed.
- Tasks not related to an appeal - This is a set of tasks adding during Intake that indicate additional actions need to be taken on the Correspondence.
When tasks are created within Caseflow, all correspondence tasks are children of a single CorrespondenceRootTask, similar to appeals tasks.
- 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