Config Change Emails - Revision history

Thomas Peterson: /* Sign up for Emails */

2024-10-23T20:45:57Z

← Older revision		Revision as of 20:45, 23 October 2024
Line 24:		Line 24:
	[[File:AreasPage-ConfigEmail.png\|border\|700px\|alt=Image showing where to edit the config change contacts list]]		[[File:AreasPage-ConfigEmail.png\|border\|700px\|alt=Image showing where to edit the config change contacts list]]

	*After adding or editing the "persons to notify list", select "Save" in the lower portion of the box		*After adding or editing the "persons to notify" list, select "Save" in the lower portion of the box

	If the desired contact is not found, then add a new contact by going to the Contacts tab under Callout Scheduling, as shown here [[Portal Callout Scheduling]]. You can also use the contact list to make sure that the contact to be used has an email address specified. Note that on the contact page the email address can be entered even though the email checkbox is left off, if this is the case the contact will not receive email callouts but can still receive the config change emails.		If the desired contact is not found, then add a new contact by going to the Contacts tab under Callout Scheduling, as shown here [[Portal Callout Scheduling]]. You can also use the contact list to make sure that the contact to be used has an email address specified. Note that on the contact page the email address can be entered even though the email checkbox is left off, if this is the case the contact will not receive email callouts but can still receive the config change emails.

	A contact can be used to sign up for emails across multiple areas.		A contact can be used to sign up for emails across multiple areas.

Thomas Peterson: /* Sign up for Emails */

2024-10-23T20:45:39Z

← Older revision		Revision as of 20:45, 23 October 2024
Line 23:		Line 23:

	[[File:AreasPage-ConfigEmail.png\|border\|700px\|alt=Image showing where to edit the config change contacts list]]		[[File:AreasPage-ConfigEmail.png\|border\|700px\|alt=Image showing where to edit the config change contacts list]]

			*After adding or editing the "persons to notify list", select "Save" in the lower portion of the box

	If the desired contact is not found, then add a new contact by going to the Contacts tab under Callout Scheduling, as shown here [[Portal Callout Scheduling]]. You can also use the contact list to make sure that the contact to be used has an email address specified. Note that on the contact page the email address can be entered even though the email checkbox is left off, if this is the case the contact will not receive email callouts but can still receive the config change emails.		If the desired contact is not found, then add a new contact by going to the Contacts tab under Callout Scheduling, as shown here [[Portal Callout Scheduling]]. You can also use the contact list to make sure that the contact to be used has an email address specified. Note that on the contact page the email address can be entered even though the email checkbox is left off, if this is the case the contact will not receive email callouts but can still receive the config change emails.

	A contact can be used to sign up for emails across multiple areas.		A contact can be used to sign up for emails across multiple areas.

Thomas Peterson: /* Sign up for Emails */

2024-10-23T20:44:18Z

← Older revision		Revision as of 20:44, 23 October 2024
Line 15:		Line 15:
	==Sign up for Emails==		==Sign up for Emails==

	Go to the Areas page.		*Go to the Areas page.

	[[File:UnitsPage.png\|border\|700px\|alt=Image showing where to edit the config change contacts list]]		[[File:UnitsPage.png\|border\|700px\|alt=Image showing where to edit the config change contacts list]]

	Select the contacts you would like to have subscribed.		*Select "Edit" next to an area
			*Select the contacts you would like to have subscribed.

	[[File:AreasPage-ConfigEmail.png\|border\|700px\|alt=Image showing where to edit the config change contacts list]]		[[File:AreasPage-ConfigEmail.png\|border\|700px\|alt=Image showing where to edit the config change contacts list]]

Thomas Peterson at 20:43, 23 October 2024

2024-10-23T20:43:42Z

← Older revision		Revision as of 20:43, 23 October 2024
Line 5:		Line 5:
	DCTs send the Brain config to the server typically once a day. The time of sending is not fixed. If changes were made in the last 24h to the panel, the email will include those changes to the unit.		DCTs send the Brain config to the server typically once a day. The time of sending is not fixed. If changes were made in the last 24h to the panel, the email will include those changes to the unit.

	Staring with DCT v1.67.276, the panel will also send config changes shortly after those changes are made. The email will specify if the change was sometime in the last 24h or is known to have been recent.		Staring with DCT v1.67.276, the panel will also send config changes shortly after those changes are made. The email will specify if the change was sometime in the last 24h (for old panel software), or is known to have been recent.

	'''Example Email'''		'''Example Email'''

Thomas Peterson at 20:42, 23 October 2024

2024-10-23T20:42:54Z

← Older revision		Revision as of 20:42, 23 October 2024
Line 3:		Line 3:
	Users can receive config change notifications by subscribing to receive emails for changes to configuration on any DCT panel in that area.		Users can receive config change notifications by subscribing to receive emails for changes to configuration on any DCT panel in that area.

	DCTs send the Brain config to the server typically once a day. The time of sending is not fixed. If changes were made in the last 24h to the panel, the email will include those changes to the unit. Staring with DCT v1.67.276 the panel will also send config changes shortly after those changes are made. The email will specify if the change was sometime in the last 24h or is known to have been recent.		DCTs send the Brain config to the server typically once a day. The time of sending is not fixed. If changes were made in the last 24h to the panel, the email will include those changes to the unit.

			Staring with DCT v1.67.276, the panel will also send config changes shortly after those changes are made. The email will specify if the change was sometime in the last 24h or is known to have been recent.

	'''Example Email'''		'''Example Email'''

Thomas Peterson at 20:42, 23 October 2024

2024-10-23T20:42:27Z

← Older revision		Revision as of 20:42, 23 October 2024
Line 1:		Line 1:
	==Overview==		==Overview==

	Users can receive config change notifications by subscribing to receive emails for changes to configuration on any DCT panel in that area.		Users can receive config change notifications by subscribing to receive emails for changes to configuration on any DCT panel in that area.

Thomas Peterson at 20:41, 23 October 2024

2024-10-23T20:41:32Z

← Older revision		Revision as of 20:41, 23 October 2024
Line 1:		Line 1:
	==Overview==		==Overview==

	Users can receive config change notifications by subscribing to receive ~~all config change notifications~~ for an area.		Users can receive config change notifications by subscribing to receive emails for changes to configuration on any DCT panel in that area.

	DCTs send the Brain config to the server typically once a day. The time of sending is not fixed. If changes were made in the last 24h to the panel, the email will include those changes to the unit. Staring with DCT v1.67.276 the panel will also send config changes shortly after those changes are made. The email will specify if the change was sometime in the last 24h or is known to have been recent.		DCTs send the Brain config to the server typically once a day. The time of sending is not fixed. If changes were made in the last 24h to the panel, the email will include those changes to the unit. Staring with DCT v1.67.276 the panel will also send config changes shortly after those changes are made. The email will specify if the change was sometime in the last 24h or is known to have been recent.

Thomas Peterson at 20:38, 23 October 2024

2024-10-23T20:38:33Z

← Older revision		Revision as of 20:38, 23 October 2024
Line 21:		Line 21:
	[[File:AreasPage-ConfigEmail.png\|border\|700px\|alt=Image showing where to edit the config change contacts list]]		[[File:AreasPage-ConfigEmail.png\|border\|700px\|alt=Image showing where to edit the config change contacts list]]

	If the desired contact is not found, then add a new contact by going to the Contacts tab under Callout Scheduling, as shown here [[Portal Callout Scheduling]].		If the desired contact is not found, then add a new contact by going to the Contacts tab under Callout Scheduling, as shown here [[Portal Callout Scheduling]]. You can also use the contact list to make sure that the contact to be used has an email address specified. Note that on the contact page the email address can be entered even though the email checkbox is left off, if this is the case the contact will not receive email callouts but can still receive the config change emails.

			A contact can be used to sign up for emails across multiple areas.

Thomas Peterson at 20:36, 23 October 2024

2024-10-23T20:36:30Z

@@ Line 1: / Line 1: @@
 ==Overview==
 Users can receive config change notifications by subscribing to receive all config change notifications for an area.
 ==Sign up for Emails==
@@ Line 14: / Line 22: @@
 If the desired contact is not found, then add a new contact by going to the Contacts tab under Callout Scheduling, as shown here [[Portal Callout Scheduling]].

Cvalentine at 19:25, 27 September 2024

2024-09-27T19:25:53Z

← Older revision		Revision as of 19:25, 27 September 2024
Line 3:		Line 3:
	Users can receive config change notifications by subscribing to receive all config change notifications for an area.		Users can receive config change notifications by subscribing to receive all config change notifications for an area.

	==Sign Up for ~~emails~~==		==Sign up for Emails==

	Go to the Areas page.		Go to the Areas page.