Service - User Contact Manager: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 17: | Line 17: | ||
configTag: "NotificationManagerServiceName" | configTag: "NotificationManagerServiceName" | ||
configKey: "NotificationManagerServiceName" | configKey: "NotificationManagerServiceName" | ||
configValue: {eg: " | configValue: xxx // eg: "NotificationMgr" | ||
} | |||
</syntaxhighlight> | |||
<syntaxhighlight lang="JavaScript"> | |||
{ | |||
configTag: "ContactMethodServiceName" | |||
configKey: xxx // methodTag, eg: "Email" | |||
configValue: { | |||
serviceName: xxx // eg: "ContactMethodEmail" | |||
} | |||
} | } | ||
</syntaxhighlight> | </syntaxhighlight> | ||
Line 31: | Line 41: | ||
: comes from {methodTag}_{methods uniqueId, eg: emailUniqueId} | : comes from {methodTag}_{methods uniqueId, eg: emailUniqueId} | ||
; contactTag | ; contactTag | ||
: user defined tag to identify this user contact | |||
= Creating a new user contact = | = Creating a new user contact = |
Revision as of 11:44, 30 January 2021
Overview
Manages contact methods available to users. Records each users contacts.
Repository
https://bitbucket.org/stb_working/user-contact-manager/src/master/
DynamoDB tables
Standard Config Table Per Service
Configuration tags
{
configTag: "NotificationManagerServiceName"
configKey: "NotificationManagerServiceName"
configValue: xxx // eg: "NotificationMgr"
}
{
configTag: "ContactMethodServiceName"
configKey: xxx // methodTag, eg: "Email"
configValue: {
serviceName: xxx // eg: "ContactMethodEmail"
}
}
UserContacts
Fields
- userId
- (partition key)
- userContactId
- (sort key)
- comes from {methodTag}_{methods uniqueId, eg: emailUniqueId}
- contactTag
- user defined tag to identify this user contact
Creating a new user contact
- This service presents a list of available contact methods
- User choses one and and is directed to that contact method handler to create the actual entry
- Once the user contact is created in the handler service a message gets sent to this service which creates it's own UserContacts record
Creating a new notification group
- This service presents a list of the users contacts
- How do we handle authentication, notification manager has no record of the userId eg for notificationGroups, only UCM has this
- (for now not direct to notification manager, any updates go through UCM, but if can figure out some token system could go direct to notification manager) User choses one and is directed to Notification Manager service
- For the endpoint given to Notification Manager try having notifications go directly to the contact method handler. Another option would be to pass back through this service but I cannot see any benefit in this.
- Notification Manager completes the flow, creating a notification group and associated notification records
Location specific contact methods
- Could add ways of restricting the available contact methods to ones the user is likely to want
- eg: by location (eg country)
- but have a way that the user can choose any method
Notes
- If method handler changes the contactName, a message will be sent to User Contact Manager to update its record, contactName is part of the sort key, not sure if it can be updated, if not need to copy the record to a new record with the updated contactName
- If method handler disables a contact, disable here and send message to Notification Manager service which will disable notifications and tell Activity Switchboard service to remove all associated triggers
Ideas
...