-
Notifications
You must be signed in to change notification settings - Fork 19
Appellant Notification Module
This module is what each of the individual event modules inherit from. Each event module has access to its own methods and the ones defined in this parent module.
The AppellantNotification module contains three custom errors, an error handling method, a method that creates the payload, and a method that sends the payload. Each event module will call AppellantNotification.notify_appellant(appeal, @@template_name)
with the appeal that is having an event triggered and the template name coming from the event module. This method internally calls the error handling method first and will return a status of "Success" if there are no errors. If there is no participant_id or no claimant found, it will return "No participant_id" or "No claimant" respectively. In the worst case scenario, when this method is somehow called without being passed an appeal, it will raise a NoAppealError exception and stop execution.
After a status is created and returned as part of a hash that contains all necessary information for creating the payload, an object is instantiated from within #create_payload
. This object (VANotifySendMessageTemplate) is what is returned from #create_payload
and gets converted to JSON as it is passed to SendNotificationJob where it is eventually pushed to the SQS queue for VA Notify to access.
- 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