-
Notifications
You must be signed in to change notification settings - Fork 19
GovDelivery TMS API
Whenever we send out email notifications from Caseflow, we interact with a third party API known as the GovDelivery Targeted Messaging System (TMS) which helps deliver and track emails send from the application.
As of 5/2023 we are reaching out to GovDelivery with four separate types of email notifications, those being:
As of 5/2023 Caseflow is able to utilize two separate "from" addresses, meaning the address that will be shown to users as far as which VA entity has initiated the message. Those addresses are as follows:
- For the DispatchMailer, HearingMailer and HearingEmailStatusMailer we are using the same from address: [email protected]
- For the MembershipRequestsMailer we are using a VHA specific address: [email protected]
You will note that both email addresses listed utilize the "messages" domain which is important as it is what allows GovDelivery TMS to setup bulk mail delivery functionality on their side
In addition to adding the preferred address in the default from:
portion of the mailer, you will need to take additional steps in order for GovDelivery to recognize it as a valid address on their end. GovDelivery is managed by a company called Granicus. Granicus has a page which outlines the steps that are needed in order for their developers to make the proper updates to allow for a new address to be recognized.
The team has received guidance from OIT that they would like to drive future discussions when this process is necessary. In order to get the process started, team leads should reach out to Joshua Tuscher ([email protected]) who manages the Granicus account for appeals. Joshua can get the process started and can even request an escalation if any delays are experienced.
Be prepared to provide the following account name for the from address(es) to be added under: USVABVA
- 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