Service - Contact Method Email: Difference between revisions

From Izara Wiki
Jump to navigation Jump to search
(Created page with "= 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...")
 
No edit summary
 
(10 intermediate revisions by 2 users not shown)
Line 2: Line 2:


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.
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/izara-core-shared/izara-core-shared-contact-method-email


= DynamoDB tables =
= DynamoDB tables =
== EmailAddress==
=== Fields ===
; userContactId
: (partition key)
: string
: a UUID generated when creating the email record, or sent by [[Service - User Contact Manager]]
; email
: string
= Object Schemas =
== objType ==
=== email ===
<syntaxhighlight lang="JavaScript">
{
objectType: "email",
    extendObjType: { // core object that this object extends
      objectType: "userContact",
      serviceTag: "UserContactManager",
    },
    storageResources: {
    myGraph: {
storageType: "graph",
graphServerTag: "GraphHandler"
}
    },
    fieldNames: {}
}
</syntaxhighlight>
=== emailAddress ===
<syntaxhighlight lang="JavaScript">
{
objectType: "emailAddress",
    overWriteHandlers: { // optional, if not set will create default handlers, if empty will not create handler and main function
create: ['hdrSqs'], // default: ['hdrApi', 'hdrSqs']
update: [],        // default: ['hdrApi', 'hdrSqs']
get: [],         // default: ['hdrApi', 'hdrInv']
delete: [], // default: ['hdrApi', 'hdrSqs']
},
    overwriteGeneratedMainFunction: ["update", "get", "delete"],
    storageResources: {
dynamoDB: {
storageType: "dynamoDB",
tableName: "EmailAddress"
}
    },
    fieldNames: { // see Per Service Schemas
userContactId: {
type: "string",
// randomOnCreate: true,
canUpdate: false,
storageResourceTags: ['dynamoDB'],
fromServiceNameTag: "UserContactManager" , // service responsible for object schema
fromObjectType: "userContact" , // objectType at fromServiceNameTag
},
email: {
type: "string",
requiredOnCreate: true,
canUpdate: false,
validation: {
pattern: pattern
},
storageResourceTags: ['dynamoDB']
}
    },
    identifiers: [
{
type: "partitionKey",
fieldName: "userContactId"
}
    ]
}
</syntaxhighlight>
==== fieldNames ====
; userContactId
: a UUID generated when creating the email record, or sent by [[Service - User Contact Manager]]
; email
: string
= 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


= Working documents =
= Working documents =

Latest revision as of 02:26, 11 March 2025

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/izara-core-shared/izara-core-shared-contact-method-email

DynamoDB tables

EmailAddress

Fields

userContactId
(partition key)
string
a UUID generated when creating the email record, or sent by Service - User Contact Manager
email
string

Object Schemas

objType

email

{
	objectType: "email",
    extendObjType: { // core object that this object extends
      objectType: "userContact",
      serviceTag: "UserContactManager",
    },
    storageResources: {
    	myGraph: {
			storageType: "graph",
			graphServerTag: "GraphHandler"
		}
    },
    fieldNames: {}
}


emailAddress

{
	objectType: "emailAddress",
    overWriteHandlers: { // optional, if not set will create default handlers, if empty will not create handler and main function
		create: ['hdrSqs'], // default: ['hdrApi', 'hdrSqs']
		update: [],         // default: ['hdrApi', 'hdrSqs']
		get: [], 	        // default: ['hdrApi', 'hdrInv']
		delete: [], 		// default: ['hdrApi', 'hdrSqs']
	},
    overwriteGeneratedMainFunction: ["update", "get", "delete"],
    storageResources: {
		dynamoDB: {
			storageType: "dynamoDB",
			tableName: "EmailAddress"
		}
    },
    fieldNames: { // see Per Service Schemas
		userContactId: {
			type: "string",
			// randomOnCreate: true,
			canUpdate: false,
			storageResourceTags: ['dynamoDB'],
			fromServiceNameTag: "UserContactManager" , // service responsible for object schema
			fromObjectType: "userContact" , // objectType at fromServiceNameTag
		},
		email: {
			type: "string",
			requiredOnCreate: true,
			canUpdate: false,
			validation: {
				pattern: pattern
			},
			storageResourceTags: ['dynamoDB']
		}
    },
    identifiers: [
		{
			type: "partitionKey",
			fieldName: "userContactId"
		}
    ]
}

fieldNames

userContactId
a UUID generated when creating the email record, or sent by Service - User Contact Manager
email
string

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

Working documents

Contact Method Email