-
Notifications
You must be signed in to change notification settings - Fork 19
Privacy Act request pending
Ki Mau edited this page Sep 15, 2022
·
4 revisions
The Appellant Notification module will notify an appellant when the appeal has been assigned to the Privacy Team. This happens at the request of the appellant. There are several types of tasks associated with this request: FoiaColocatedTask, FoiaTask, FoiaRequestMailTask, HearingAdminFoiaPrivacyRequestTask, PrivacyActTask, and PrivacyActRequestMailTask. There are three different ways for a pending Privacy Act request to occur:
- The attorney creates and assigns a FoiaColocatedTask/FoiaTask/PrivacyActTask to a Privacy Act Team user on the appeal's case details page. (Note: The FoiaTask has to be a child of a FoiaColocatedTask, so the appeal needs to already have a FoiaColocatedTask in order to create a FoiaTask. Additionally, the PrivacyActTask also has to be a child of a colocated task, but it doesn't have to be specifically a FoiaColocatedTask.)
- The hearing coordinator creates and assigns a HearingAdminFoiaPrivacyRequestTask to a hearing coordinator on the appeal's case details page.
- The Privacy Act Team creates and assigns a FoiaRequestMailTask/PrivacyActRequestMailTask to Privacy Act Team user on the appeal's case details page.
There are three prepended methods used to track the Privacy Act request pending status.
- FoiaColocatedTask/FoiaTask: The method used to create this task is
create_privacy_act_task
located inapp/models/tasks/foia_colocated_task.rb
. - FoiaRequestMailTask/PrivacyActRequestMailTask: The method used to create these tasks is
create_twin_of_type(params)
located inapp/models/mail_task.rb
. - HearingAdminFoiaPrivacyRequestTask/PrivacyActTask: The method used to create these tasks is
create_child_task(parent, current_user, params)
located inapp/models/task.rb
.
- 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