Using Calendars in LifeGuide - Revision history

152.78.223.80 at 11:53, 23 November 2010

2010-11-23T11:53:09Z

← Older revision		Revision as of 11:53, 23 November 2010
Line 63:		Line 63:


	This logic sends the email. So here we can see that the string has been appended with the date that the person enters to ensure that this is a unique name for the email. The email address is taken from the interaction called '''email''' on page1. ~~the~~ subject of the email is <code>"The email you queued"</code>, the variable message has been entered for the message content and the variable for the delay is included to give a time for when the email will be sent out.		This logic sends the email. So here we can see that the string has been appended with the date that the person enters to ensure that this is a unique name for the email. The email address is taken from the interaction called '''email''' on page1. The subject of the email is <code>"The email you queued"</code>, the variable message has been entered for the message content and the variable for the delay is included to give a time for when the email will be sent out.

152.78.223.80 at 11:50, 23 November 2010

2010-11-23T11:50:29Z

← Older revision		Revision as of 11:50, 23 November 2010
Line 12:		Line 12:

	A [http://www.lifeguideonline.org/manager/intervention/show/566 demo] of this example can be downloaded from the LifeGuide Community Website.		A [http://www.lifeguideonline.org/manager/intervention/show/566 demo] of this example can be downloaded from the LifeGuide Community Website.


	In order to use the date entered within a calendar to then do something on that specific date (e.g. to send an e-mail), logic needs to be used with the calendar interaction.		In order to use the date entered within a calendar to then do something on that specific date (e.g. to send an e-mail), logic needs to be used with the calendar interaction.

152.78.223.80 at 11:49, 23 November 2010

2010-11-23T11:49:58Z

← Older revision		Revision as of 11:49, 23 November 2010
Line 12:		Line 12:

	A [http://www.lifeguideonline.org/manager/intervention/show/566 demo] of this example can be downloaded from the LifeGuide Community Website.		A [http://www.lifeguideonline.org/manager/intervention/show/566 demo] of this example can be downloaded from the LifeGuide Community Website.


	In order to use the date entered within a calendar to then do something on that specific date (e.g. to send an e-mail), logic needs to be used with the calendar interaction.		In order to use the date entered within a calendar to then do something on that specific date (e.g. to send an e-mail), logic needs to be used with the calendar interaction.


	Please see the help-file related to sending [[Sending_Emails\|emails]] for full details of this function.		Please see the help-file related to sending [[Sending_Emails\|emails]] for full details of this function.


	NB: The e-mail will automatically be sent out at midnight on the date specified unless you also ask your end-user to select a specific time.		NB: The e-mail will automatically be sent out at midnight on the date specified unless you also ask your end-user to select a specific time.

152.78.223.80 at 11:48, 23 November 2010

2010-11-23T11:48:30Z

← Older revision		Revision as of 11:48, 23 November 2010
Line 55:		Line 55:

	<code>set delay to +(page1.emaildate, (3600 * page1.hours), (60 * mins), (-1 * currenttime()))</code>		<code>set delay to +(page1.emaildate, (3600 * page1.hours), (60 * mins), (-1 * currenttime()))</code>


	The last part of the logic for sending an email includes the delay for when the message will be sent out. In this example we need to set the delay based on the date and time that they have selected from the interaction.		The last part of the logic for sending an email includes the delay for when the message will be sent out. In this example we need to set the delay based on the date and time that they have selected from the interaction.

152.78.223.80 at 11:47, 23 November 2010

2010-11-23T11:47:40Z

← Older revision		Revision as of 11:47, 23 November 2010
Line 38:		Line 38:

	Hours are pretty straight forward as this unit of time would always be used. However, as it could be likely that if an end-user wants to receive an e-mail on the hour they may not select the minutes unit of time then we first need to set minutes to 0. If the end-user then selects the 15 minute option the minutes will then be set to 15.		Hours are pretty straight forward as this unit of time would always be used. However, as it could be likely that if an end-user wants to receive an e-mail on the hour they may not select the minutes unit of time then we first need to set minutes to 0. If the end-user then selects the 15 minute option the minutes will then be set to 15.


	<code>set datetext to printtime(page1.emaildate, "EEE, dd MMM yyyy")</code>		<code>set datetext to printtime(page1.emaildate, "EEE, dd MMM yyyy")</code>


	On page2 of the intervention end-users will be shown the date that they selected. This uses the command printtime to display the date which has been taken from the intervention.		On page2 of the intervention end-users will be shown the date that they selected. This uses the command printtime to display the date which has been taken from the intervention.

	A more specific breakdown of this line of logic sees that the variable '''datetext''' has been set to include the date from the interaction called '''emaildate''' from '''page1''' and this will display the date as the day of the week, date, month and year where EEE corresponds with the day and so on.		A more specific breakdown of this line of logic sees that the variable '''datetext''' has been set to include the date from the interaction called '''emaildate''' from '''page1''' and this will display the date as the day of the week, date, month and year where EEE corresponds with the day and so on.


	<code>set message to append ("This is the email that you queued to be sent at ", page1.hours, ":", mins, " on ", datetext, " on the LifeGuide calendar demo.")</code>		<code>set message to append ("This is the email that you queued to be sent at ", page1.hours, ":", mins, " on ", datetext, " on the LifeGuide calendar demo.")</code>


	In this example, the content of the email has been set to the word '''message''' to be used within the e-mail logic		In this example, the content of the email has been set to the word '''message''' to be used within the e-mail logic


	<code>set delay to +(page1.emaildate, (3600 * page1.hours), (60 * mins), (-1 * currenttime()))</code>		<code>set delay to +(page1.emaildate, (3600 * page1.hours), (60 * mins), (-1 * currenttime()))</code>
Line 54:		Line 59:

	Here we can see that the variable '''delay''' has been set as the date entered in the calendar on page 1 (this interaction was called '''emaildate''') plus 3600 x the number selected on the interaction called '''hours''' on page1. (This is because time within the LifeGuide logic works in seconds and there are 3600 seconds in an hour. So if a person chooses to receive their message at 3 o clock it would need to calculate 3 x 3600 to send it at this time). The same needs to be done with the minutes that they chose. (So here the logic is calculating 60 x the variable that was set earlier in the logic). Finally the command <code>currenttime</code> has been used to determine the time that the person used the page (which has be multiplied by -1) so that we can calculate a delay from the time that they entered the details.		Here we can see that the variable '''delay''' has been set as the date entered in the calendar on page 1 (this interaction was called '''emaildate''') plus 3600 x the number selected on the interaction called '''hours''' on page1. (This is because time within the LifeGuide logic works in seconds and there are 3600 seconds in an hour. So if a person chooses to receive their message at 3 o clock it would need to calculate 3 x 3600 to send it at this time). The same needs to be done with the minutes that they chose. (So here the logic is calculating 60 x the variable that was set earlier in the logic). Finally the command <code>currenttime</code> has been used to determine the time that the person used the page (which has be multiplied by -1) so that we can calculate a delay from the time that they entered the details.


	<code>after page1 if (sendemail(append("calendaremail", page1.emaildate) , page1.email, "The email you queued", message, delay)) goto page2</code>		<code>after page1 if (sendemail(append("calendaremail", page1.emaildate) , page1.email, "The email you queued", message, delay)) goto page2</code>


	This logic sends the email. So here we can see that the string has been appended with the date that the person enters to ensure that this is a unique name for the email. The email address is taken from the interaction called '''email''' on page1. the subject of the email is <code>"The email you queued"</code>, the variable message has been entered for the message content and the variable for the delay is included to give a time for when the email will be sent out.		This logic sends the email. So here we can see that the string has been appended with the date that the person enters to ensure that this is a unique name for the email. The email address is taken from the interaction called '''email''' on page1. the subject of the email is <code>"The email you queued"</code>, the variable message has been entered for the message content and the variable for the delay is included to give a time for when the email will be sent out.


	<code>show page2</code>		<code>show page2</code>

152.78.223.80 at 11:45, 23 November 2010

2010-11-23T11:45:36Z

← Older revision		Revision as of 11:45, 23 November 2010
Line 60:		Line 60:

	<code>show page2</code>		<code>show page2</code>

	<code>set page2.hours to page1.hours</code>		<code>set page2.hours to page1.hours</code>

	<code>set page2.minutes to mins</code>		<code>set page2.minutes to mins</code>

	<code>set page2.date to datetext</code>		<code>set page2.date to datetext</code>


	This logic uses the '''set''' command to show end-users the information the date and time that they should expect to get their email.		This logic uses the '''set''' command to show end-users the information the date and time that they should expect to get their email.

152.78.223.80 at 11:44, 23 November 2010

2010-11-23T11:44:52Z

152.78.223.80 at 11:37, 23 November 2010

2010-11-23T11:37:58Z

← Older revision		Revision as of 11:37, 23 November 2010
Line 28:		Line 28:


	<code>set mins to 0		<code>set mins to 0</code>
	~~if (page1.minutes = "fifteen") set mins to 15~~

	if (page1.minutes = "~~thirty~~") set mins to 30		<code>if (page1.minutes = "fifteen") set mins to 15</code>

	if (page1.minutes = "fortyfive") set mins to 45</code>		<code>if (page1.minutes = "thirty") set mins to 30</code>

			<code>if (page1.minutes = "fortyfive") set mins to 45</code>

	Hours are pretty straight forward as this unit of time would always be used. However, as it could be likely that if an end-user wants to receive an e-mail on the hour they may not select the minutes unit of time then we first need to set minutes to 0. If the end-user then selects the 15 minute option the minutes will then be set to 15.		Hours are pretty straight forward as this unit of time would always be used. However, as it could be likely that if an end-user wants to receive an e-mail on the hour they may not select the minutes unit of time then we first need to set minutes to 0. If the end-user then selects the 15 minute option the minutes will then be set to 15.

152.78.223.80 at 11:36, 23 November 2010

2010-11-23T11:36:41Z

← Older revision		Revision as of 11:36, 23 November 2010
Line 29:		Line 29:

	<code>set mins to 0		<code>set mins to 0
			if (page1.minutes = "fifteen") set mins to 15

	~~if (page1.minutes = "fifteen") set mins to 15~~
	if (page1.minutes = "thirty") set mins to 30		if (page1.minutes = "thirty") set mins to 30

	if (page1.minutes = "fortyfive") set mins to 45</code>		if (page1.minutes = "fortyfive") set mins to 45</code>

152.78.223.80 at 11:35, 23 November 2010

2010-11-23T11:35:23Z

← Older revision		Revision as of 11:35, 23 November 2010
Line 29:		Line 29:

	<code>set mins to 0		<code>set mins to 0

	if (page1.minutes = "fifteen") set mins to 15		if (page1.minutes = "fifteen") set mins to 15
	if (page1.minutes = "thirty") set mins to 30		if (page1.minutes = "thirty") set mins to 30

← Older revision		Revision as of 11:44, 23 November 2010
Line 35:		Line 35:

	<code>if (page1.minutes = "fortyfive") set mins to 45</code>		<code>if (page1.minutes = "fortyfive") set mins to 45</code>


	Hours are pretty straight forward as this unit of time would always be used. However, as it could be likely that if an end-user wants to receive an e-mail on the hour they may not select the minutes unit of time then we first need to set minutes to 0. If the end-user then selects the 15 minute option the minutes will then be set to 15.		Hours are pretty straight forward as this unit of time would always be used. However, as it could be likely that if an end-user wants to receive an e-mail on the hour they may not select the minutes unit of time then we first need to set minutes to 0. If the end-user then selects the 15 minute option the minutes will then be set to 15.

	set datetext to printtime(page1.emaildate, "EEE, dd MMM yyyy")		<code>set datetext to printtime(page1.emaildate, "EEE, dd MMM yyyy")</code>

	On page2 of the intervention end-users will be shown the date that they selected. This uses the command printtime to display the date which has been taken from the intervention		On page2 of the intervention end-users will be shown the date that they selected. This uses the command printtime to display the date which has been taken from the intervention.

	A more specific breakdown of this line of logic sees that the variable datetext has been set to include the date from the interaction called emaildate from page1 and this will display the date as the day of the week, date, month and year where EEE corresponds with the day and so on.		A more specific breakdown of this line of logic sees that the variable '''datetext''' has been set to include the date from the interaction called '''emaildate''' from '''page1''' and this will display the date as the day of the week, date, month and year where EEE corresponds with the day and so on.

	set message to append ("This is the email that you queued to be sent at ", page1.hours, ":", mins, " on ", datetext, " on the LifeGuide calendar demo.")		<code>set message to append ("This is the email that you queued to be sent at ", page1.hours, ":", mins, " on ", datetext, " on the LifeGuide calendar demo.")</code>

	In this example, the content of the email has been set to the word message to be used within the e-mail logic		In this example, the content of the email has been set to the word '''message''' to be used within the e-mail logic

	set delay to +(page1.emaildate, (3600 * page1.hours), (60 * mins), (-1 * currenttime()))		<code>set delay to +(page1.emaildate, (3600 * page1.hours), (60 * mins), (-1 * currenttime()))</code>

	The last part of the logic for sending an email includes the delay for when the message will be sent out. In this example we need to set the delay based on the date and time that they have selected from the interaction.		The last part of the logic for sending an email includes the delay for when the message will be sent out. In this example we need to set the delay based on the date and time that they have selected from the interaction.

	Here we can see that the variable delay has been set as the date entered in the calendar on page 1 (this interaction was called emaildate) plus 3600 x the number selected on the interaction called hours on page1. (This is because time within the LifeGuide logic works in seconds and there are 3600 seconds in an hour. So if a person chooses to receive their message at 3 o clock it would need to calculate 3 x 3600 to send it at this time). The same needs to be done with the minutes that they chose. (So here the logic is calculating 60 x the variable that was set earlier in the logic). Finally the command currenttime has been used to determine the time that the person used the page (which has be multiplied by -1) so that we can calculate a delay from the time that they entered the details.		Here we can see that the variable '''delay''' has been set as the date entered in the calendar on page 1 (this interaction was called '''emaildate''') plus 3600 x the number selected on the interaction called '''hours''' on page1. (This is because time within the LifeGuide logic works in seconds and there are 3600 seconds in an hour. So if a person chooses to receive their message at 3 o clock it would need to calculate 3 x 3600 to send it at this time). The same needs to be done with the minutes that they chose. (So here the logic is calculating 60 x the variable that was set earlier in the logic). Finally the command <code>currenttime</code> has been used to determine the time that the person used the page (which has be multiplied by -1) so that we can calculate a delay from the time that they entered the details.

	after page1 if (sendemail(append("calendaremail", page1.emaildate) , page1.email, "The email you queued", message, delay)) goto page2		<code>after page1 if (sendemail(append("calendaremail", page1.emaildate) , page1.email, "The email you queued", message, delay)) goto page2</code>

	This logic sends the email. So here we can see that the string has been appended with the date that the person enters to ensure that this is a unique name for the email. The email address is taken from the interaction called email on page1. the subject of the email is "The email you queued", the variable message has been entered for the message content and the variable for the delay is included to give a time for when the email will be sent out.		This logic sends the email. So here we can see that the string has been appended with the date that the person enters to ensure that this is a unique name for the email. The email address is taken from the interaction called '''email''' on page1. the subject of the email is <code>"The email you queued"</code>, the variable message has been entered for the message content and the variable for the delay is included to give a time for when the email will be sent out.

	show page2		<code>show page2</code>
	set page2.hours to page1.hours		<code>set page2.hours to page1.hours</code>
	set page2.minutes to mins		<code>set page2.minutes to mins</code>
	set page2.date to datetext		<code>set page2.date to datetext</code>

	This logic uses the set command to show end-users the information the date and time that they should expect to get their email.		This logic uses the '''set''' command to show end-users the information the date and time that they should expect to get their email.