Tutorial/Status notifications - Revision history

Tvi at 15:26, 15 February 2022

2022-02-15T15:26:42Z

← Older revision		Revision as of 17:26, 15 February 2022
Line 28:		Line 28:
	Tip: It is perfectly OK to use templates with any tags in it, but in that case you might consider using the link approach below.		Tip: It is perfectly OK to use templates with any tags in it, but in that case you might consider using the link approach below.

			Files from the record can be attatched using the following tag, where 123456 is the ID of the field.

			[FILES:123456]

	=== Dynamic links ===		=== Dynamic links ===

2021-12-10T10:55:46Z

18 revisions imported

← Older revision	Revision as of 12:55, 10 December 2021
(No difference)

2020-12-22T11:28:22Z

← Older revision		Revision as of 13:28, 22 December 2020
Line 21:		Line 21:

	This will render the the template, and attatch the resulting file as an attatchment to the email.		This will render the the template, and attatch the resulting file as an attatchment to the email.

			Default name of the file is "attatchment". In case you want a custom name add this in the tag (ex. "Foobar" )

			[REPORT:123456-Foobar]

	Tip: It is perfectly OK to use templates with any tags in it, but in that case you might consider using the link approach below.		Tip: It is perfectly OK to use templates with any tags in it, but in that case you might consider using the link approach below.


	=== Dynamic links ===		=== Dynamic links ===

2020-11-18T07:51:25Z

Special tags for notification

← Older revision		Revision as of 09:51, 18 November 2020
Line 23:		Line 23:

	Tip: It is perfectly OK to use templates with any tags in it, but in that case you might consider using the link approach below.		Tip: It is perfectly OK to use templates with any tags in it, but in that case you might consider using the link approach below.

			=== Dynamic links ===
			URLs can be entered by using {APPURL} in front of a relative reference.
			Example:
			{APPURL}/login

	=== Static file links ===		=== Static file links ===

2020-11-18T07:44:11Z

Data in emails

← Older revision		Revision as of 09:44, 18 November 2020
Line 11:		Line 11:
	* {RAWLINK}: Link without any HTML markup		* {RAWLINK}: Link without any HTML markup

	Note that a libnk to record will be included at the bottom of the message, unless a LINK or a NOLINK placeholder can be found.		Note that a libnk to record will be included at the bottom of the message, unless a LINK, RAWLINK or a NOLINK placeholder can be found.

	=== Create attatchments ===		=== Create attatchments ===

2020-11-18T07:42:48Z

Data in emails

← Older revision		Revision as of 09:42, 18 November 2020
Line 9:		Line 9:
	* {LINK}: Clickable link to the record (se below)		* {LINK}: Clickable link to the record (se below)
	* {NOLINK}: Do not include any record links		* {NOLINK}: Do not include any record links
			* {RAWLINK}: Link without any HTML markup

	Note that a libnk to record will be included at the bottom of the message, unless a LINK or a NOLINK placeholder can be found.		Note that a libnk to record will be included at the bottom of the message, unless a LINK or a NOLINK placeholder can be found.

2020-09-23T13:37:44Z

← Older revision		Revision as of 15:37, 23 September 2020
Line 17:		Line 17:
	[REPORT:123456]		[REPORT:123456]

	The number refers to the ID og the template to render.		The number refers to the ID of the template to render.

	This will render the the template, and attatch the resulting file as an attatchment to the email.		This will render the the template, and attatch the resulting file as an attatchment to the email.

2019-10-31T15:40:34Z

Create attatchments

← Older revision		Revision as of 17:40, 31 October 2019
Line 20:		Line 20:

	This will render the the template, and attatch the resulting file as an attatchment to the email.		This will render the the template, and attatch the resulting file as an attatchment to the email.

			Tip: It is perfectly OK to use templates with any tags in it, but in that case you might consider using the link approach below.

	=== Static file links ===		=== Static file links ===

2019-10-31T15:37:31Z

Special tags for notification

← Older revision		Revision as of 17:37, 31 October 2019
Line 1:		Line 1:
	== Special tags for notification ==		== Special tags for notification ==

			=== Data in emails ===
	Dynamic field content can be inserted using {FIELD_SYSTEM_NAME} syntax.		Dynamic field content can be inserted using {FIELD_SYSTEM_NAME} syntax.

	For status notification content the following tags will also be populated		For status notification content the following tags will also be populated
	* {USER}		* {USER}: Name of the user
	* {~~LINK~~}		* {RESUME} Name of the record
	* {~~NOLINK~~}		* {LINK}: Clickable link to the record (se below)
	* {~~RESUME~~}		* {NOLINK}: Do not include any record links

			Note that a libnk to record will be included at the bottom of the message, unless a LINK or a NOLINK placeholder can be found.

			=== Create attatchments ===
	Additionally rendered files can be attatched using the following syntax		Additionally rendered files can be attatched using the following syntax

2019-10-31T15:34:17Z

Special tags for notification

← Older revision		Revision as of 17:34, 31 October 2019
Line 13:		Line 13:
	[REPORT:123456]		[REPORT:123456]

	The number refers to the ID og the template to render.		The number refers to the ID og the template to render.

	=== Static ~~files~~ ===		This will render the the template, and attatch the resulting file as an attatchment to the email.

			=== Static file links ===
	If you only need static files, just upload them to the media libarry and put a link in the mail		If you only need static files, just upload them to the media libarry and put a link in the mail
	# Upload to media library: Ressources > Media files > Add		# Upload to media library: Ressources > Media files > Add