Service - Activity Switchboard - Revision history

Pong at 04:19, 11 September 2025

2025-09-11T04:19:10Z

Pong at 06:13, 19 March 2025

2025-03-19T06:13:29Z

@@ Line 6: / Line 6: @@
 https://bitbucket.org/izara-core-shared/izara-core-shared-activity-switchboard
 = Object Schemas =
@@ Line 59: / Line 38: @@
 			type: "string",
 			randomOnCreate: true,
 			canUpdate: false,
 			validation: {
@@ Line 88: / Line 58: @@
 ; triggerGroupId
 : comes from: hash{triggers}
 === trigger ===
@@ Line 174: / Line 141: @@
 ; triggerId
-: (partition key)
+: (identifier)
 : comes from: {hash of valueType(property|attribute).propertyName}_{hash of propertyValue}
 : or: serviceName_{hash of serviceName value}
@@ Line 191: / Line 158: @@
 ; propertyValueNumber
 : type of this propertyValueNumber is number from valueNumber in [[Service - Notification Manager]]
 === hasTrigger ===

Pong at 09:10, 17 March 2025

2025-03-17T09:10:43Z

Show changes

Sven the Barbarian at 00:52, 9 March 2025

2025-03-09T00:52:11Z

← Older revision		Revision as of 00:52, 9 March 2025
Line 5:		Line 5:
	= Repository =		= Repository =

	https://bitbucket.org/~~stb_working~~/activity-switchboard~~/src/master/~~		https://bitbucket.org/izara-core-shared/izara-core-shared-activity-switchboard

	= DynamoDB tables =		= DynamoDB tables =

Pong at 03:42, 7 March 2025

2025-03-07T03:42:57Z

← Older revision		Revision as of 03:42, 7 March 2025
Line 59:		Line 59:
	objectType: "triggerGroup",		objectType: "triggerGroup",
	canDelete: true,		canDelete: true,
	~~complexFilterServiceTag: "complexFilter",~~
	overWriteHandlers: { // optional, if not set will create default handlers, if empty will not create handler and main function		overWriteHandlers: { // optional, if not set will create default handlers, if empty will not create handler and main function
	create: ['hdrSqs'], // default: ['hdrApi', 'hdrSqs']		create: ['hdrSqs'], // default: ['hdrApi', 'hdrSqs']
Line 66:		Line 65:
	delete: ['hdrSqs'], // default: ['hdrApi', 'hdrSqs']		delete: ['hdrSqs'], // default: ['hdrApi', 'hdrSqs']
	},		},
	// overwriteGeneratedMainFunction: ["~~create~~"],		overwriteGeneratedMainFunction: ["update", "get"],
	storageResources: {		storageResources: {
	dynamoDB: {		dynamoDB: {
Line 131:		Line 130:
	objectType: "trigger",		objectType: "trigger",
	canDelete: true,		canDelete: true,
	~~complexFilterServiceTag: "complexFilter",~~
	overWriteHandlers: { // optional, if not set will create default handlers, if empty will not create handler and main function		overWriteHandlers: { // optional, if not set will create default handlers, if empty will not create handler and main function
	create: ['hdrSqs'], // default: ['hdrApi', 'hdrSqs']		create: ['hdrSqs'], // default: ['hdrApi', 'hdrSqs']
Line 138:		Line 136:
	delete: ['hdrSqs'], // default: ['hdrApi', 'hdrSqs']		delete: ['hdrSqs'], // default: ['hdrApi', 'hdrSqs']
	},		},
	// overwriteGeneratedMainFunction: ["~~create~~", "~~delete~~"],		overwriteGeneratedMainFunction: ["update", "get"],
	storageResources: {		storageResources: {
	dynamoDB: {		dynamoDB: {

Pong at 05:41, 13 August 2024

2024-08-13T05:41:45Z

← Older revision		Revision as of 05:41, 13 August 2024
Line 74:		Line 74:
	},		},
	fieldNames: { // see Per Service Schemas		fieldNames: { // see Per Service Schemas
	~~triggerGroupId: {~~
	~~type: "string",~~
	~~optionalOnCreate: true,~~
	~~canUpdate: false,~~
	~~validation: {~~
	~~pattern: pattern~~
	},
	~~storageResourceTags: ['dynamoDB']~~
	},
	triggers: {		triggers: {
	type: "array",		type: "array",
Line 115:		Line 106:
	type: "partitionKey",		type: "partitionKey",
	fieldNames: ["receiverTag", "uniqueId"],		fieldNames: ["receiverTag", "uniqueId"],
	~~fieldName~~: "triggerGroupId"		name: "triggerGroupId"
	}		}
	]		]
Line 165:		Line 156:
	},		},
	triggerGroupId: {		triggerGroupId: {
	type: "string",		type: "string",
	requiredOnCreate: true,		requiredOnCreate: true,
	canUpdate: false,		canUpdate: false,
	~~validation: {~~
	~~pattern: pattern~~
	},
	storageResourceTags: ['dynamoDB'],		storageResourceTags: ['dynamoDB'],
	fromServiceNameTag: "ActivitySwitchboard" ,		fromServiceNameTag: "ActivitySwitchboard",
	fromObjectType: "triggerGroup"		fromObjectType: "triggerGroup"
	},		},

Pong at 01:48, 9 August 2024

2024-08-09T01:48:39Z

@@ Line 248: / Line 248: @@
 ; propertyValueNumber
 : type of this propertyValueNumber is number from valueNumber in [[Service - Notification Manager]]
 = Efficiency =

Pong at 02:18, 8 August 2024

2024-08-08T02:18:06Z

Show changes

Pong at 08:50, 9 July 2024

2024-07-09T08:50:59Z

Show changes

Sven the Barbarian at 14:03, 10 May 2021

2021-05-10T14:03:29Z

← Older revision		Revision as of 14:03, 10 May 2021
Line 12:		Line 12:

	=== Configuration tags ===		=== Configuration tags ===

	~~<syntaxhighlight lang="JavaScript">~~
	{
	~~configKey: "PendingMsgCfgPause"~~
	~~configTag: "PendingMsgCfgPause"~~
	~~configValue: xx //number of ?seconds to wait between attempts to pullMsgCfg~~
	}
	~~</syntaxhighlight>~~

	<syntaxhighlight lang="JavaScript">		<syntaxhighlight lang="JavaScript">
Line 26:		Line 18:
	configTag: {serviceName}_{topicName}		configTag: {serviceName}_{topicName}
	configValue: {msgCfg}		configValue: {msgCfg}
	~~configValue: {~~
	~~pending: true~~
	~~nextCheck: {timestamp}~~
	}
	~~configValue: {~~
	~~deleted: true~~
	~~timestampDeleted: {current timestamp}~~
	}
	timestampUpdated = zz		timestampUpdated = zz
	}		}
Line 39:		Line 23:
	: propogated from [[Service - Message Config Manager\|Message Config Manager]] service		: propogated from [[Service - Message Config Manager\|Message Config Manager]] service
	: see [[Standard message config for In Out topics]]		: see [[Standard message config for In Out topics]]
	: if the MsgCfg has not been dug before set it to pending, each time a message comes in a request is made using pullMsgCfg Lambda, if the request is not successful set nextCheck = current timestamp + PendingMsgCfgPause
	: timestampUpdated is used to ensure the latest msgCfg update is applied		: timestampUpdated is used to ensure the latest msgCfg update is applied

Line 46:		Line 29:
	* Groups many triggers, all triggers for a trigger group must pass for the trigger group to pass		* Groups many triggers, all triggers for a trigger group must pass for the trigger group to pass
	* no sort key		* no sort key
			* if multiple values are sent for a trigger we consider this an "or" check, any of the values can match. We do this by saving each value as a separate trigger, then when checking a trigger groups child triggers we have a counter that enables a check if any one of the values matches

	=== Fields ===		=== Fields ===
Line 66:		Line 50:
	; triggerId		; triggerId
	: (partition key)		: (partition key)
	: comes from: ~~{"attributes"\|"property"}_~~{hash of propertyName}_{hash of propertyValue}		: comes from: {hash of valueType(property\|attribute).propertyName}_{hash of propertyValue}
	: or: serviceName_{~~value~~ of serviceName}		: or: serviceName_{hash of serviceName value}
	: or: topicName_{~~value~~ of topicName}		: or: topicName_{hash of topicName value}
	: attributes is for message attributes		: attributes is for message attributes
	: property is from the data sent inside the message body		: property is from the data sent inside the message body
Line 88:		Line 72:
	* msgCfgs get updated from [[Service - Message Config Manager\|Message Config Manager]] service, we do this by subscribing to Message Config Manager's OutMsgCfgUpdate topic		* msgCfgs get updated from [[Service - Message Config Manager\|Message Config Manager]] service, we do this by subscribing to Message Config Manager's OutMsgCfgUpdate topic
	* Only want to process messages from certain In/Out topics, it will be most topics but does not have to be all		* Only want to process messages from certain In/Out topics, it will be most topics but does not have to be all
	* Set which topics to subscribe to by ~~creating a "MsgCfg" record~~ in ~~the Config table, initially the configValue will be empty and needs to be pulled from Message Config Manager~~		* Set which topics to subscribe to by setting activitySwitchboard = true in msgCfg
	* Plan is to set a list of topics in InitalSetup, for each add a record to Config table and invoking [[2020-11-08 - Message Config Manager - Functions#getMsgCfgs]] or getMsgCfg, not sure how to do this to ensure the configs already exist
	* Could also perhaps have a placeholder configValue that states the MsgCfg has not yet been dug, when a message comes in if that is set, request the MsgCfg then, if the request is unsuccessful have another placeholder that has timestamp when last checked, after a certain time re-request (and probably DLQ the message that arrived)
	* If MsgCfg is ever added after initial deploy, also need to add receiveMsg subscription to that topic, perhaps build config Lambda to handle this

	= Ideas =		= Ideas =