Service - Contact Method Email: Difference between revisions
Jump to navigation
Jump to search
(→Notes) |
(→Notes) |
||
| Line 33: | Line 33: | ||
= Notes = | = Notes = | ||
* [[Service - User Contact Manager]] sets the notification group's uniqueID to be {emailUniqueId}_{uuid}, we could split the notificationGroupUniqueId to pull out the emailUniqueId, alternative is we also add the emailID to notification group's additionalData which is what we will do because it is more | * [[Service - User Contact Manager]] sets the notification group's uniqueID to be {emailUniqueId}_{uuid}, we could split the notificationGroupUniqueId to pull out the emailUniqueId, alternative is we also add the emailID to notification group's additionalData which is what we will do because it is more strongly defined | ||
= Working documents = | = Working documents = | ||
Revision as of 03:24, 29 November 2020
Overview
Manages email contact methods for users, details are not part of the public transparency followed across the majority of the project in order to protect against emails being scraped.
Repository
https://bitbucket.org/stb_working/contact-method-email/src/master/
DynamoDB tables
Standard Config Table Per Service
Configuration tags
- ...
Emails
Fields
- userId
- (partition key)
- uniqueId
- (sort key)
- eg a UUID generated when creating the email record, or sent by Service - User Contact Manager
- string
- contactTag
- string name created by user to publicly identify this email contact
- enabled
- true|false
Notes
- Service - User Contact Manager sets the notification group's uniqueID to be {emailUniqueId}_{uuid}, we could split the notificationGroupUniqueId to pull out the emailUniqueId, alternative is we also add the emailID to notification group's additionalData which is what we will do because it is more strongly defined