DevOps:Doc/FlexForm/2.0/email - Revision history

Fd4138e7-8b46-4c8f-99bf-d4b738ebc295: Text replacement - "|Subject version=2.0,2.1" to "|Subject version=2.0,2.1,2.5"

2025-08-21T09:08:01Z

Text replacement - "|Subject version=2.0,2.1" to "|Subject version=2.0,2.1,2.5"

ws-class-props
← Older revision		Revision as of 11:08, 21 August 2025
Line 1:		Line 1:
	{{Csp class properties		{{Csp class properties
	\|Subject version=2.0,2.1		\|Subject version=2.0,2.1,2.5
	\|Doc subject=DevOps:Doc/FlexForm		\|Doc subject=DevOps:Doc/FlexForm
	\|Doc sort order=220		\|Doc sort order=220

2025-07-15T08:33:34Z

Imported by PageSync

ws-class-props
← Older revision		Revision as of 10:33, 15 July 2025
Line 1:		Line 1:
	{{~~Doc~~ properties		{{Csp class properties
	\|Subject version=2.0,2.1		\|Subject version=2.0,2.1
	\|Doc subject=DevOps:Doc/FlexForm		\|Doc subject=DevOps:Doc/FlexForm

2024-12-16T09:58:57Z

← Older revision		Revision as of 11:58, 16 December 2024
Line 154:		Line 154:
	=== Note / Tip ===		=== Note / Tip ===
	Since the email template is parsed, you can fill the value for e.g. the '''_bcc''' email addresses with a Semantic Media Parse function. Effectively you could create a newsletter function with this feature. Additionally.. when u use the Api function [[DevOps:Doc/FlexForm/1.1/API/FlexFormBot\|FlexFormBot]] you can create a Python function or a Maintenance script that could be triggered using a Cron job to send newsletters automatically.		Since the email template is parsed, you can fill the value for e.g. the '''_bcc''' email addresses with a Semantic Media Parse function. Effectively you could create a newsletter function with this feature. Additionally.. when u use the Api function [[DevOps:Doc/FlexForm/1.1/API/FlexFormBot\|FlexFormBot]] you can create a Python function or a Maintenance script that could be triggered using a Cron job to send newsletters automatically.

			=== Links ===
			The above Tip, basically creating a newsletter, is explained in more detail in this Developer log : https://wikibase-solutions.com/developer-logs/create-a-newsletter-with-flexform

2024-11-04T21:29:36Z

@@ Line 3: / Line 3: @@
 |Section=Documentation/FlexForm
 |Published time=2022-11-17
 }}

2024-11-04T21:28:08Z

ws-seo
← Older revision	Revision as of 23:28, 4 November 2024
Line 1:	Line 1:
		{{SEO
		\|Image=FlexForm logo.png
		\|Section=Documentation/FlexForm
		\|Published time=2022-11-17
		}}

2024-11-04T21:20:32Z

← Older revision		Revision as of 23:20, 4 November 2024
Line 151:		Line 151:
	=== Parsing ===		=== Parsing ===
	FlexForm will first parse the email template and then substitute form names in the email template with the form values. If you want to have this reversed, use the '''parselast''' argument on the _email function.		FlexForm will first parse the email template and then substitute form names in the email template with the form values. If you want to have this reversed, use the '''parselast''' argument on the _email function.

			=== Note / Tip ===
			Since the email template is parsed, you can fill the value for e.g. the '''_bcc''' email addresses with a Semantic Media Parse function. Effectively you could create a newsletter function with this feature. Additionally.. when u use the Api function [[DevOps:Doc/FlexForm/1.1/API/FlexFormBot\|FlexFormBot]] you can create a Python function or a Maintenance script that could be triggered using a Cron job to send newsletters automatically.

2023-06-05T12:13:36Z

← Older revision		Revision as of 14:13, 5 June 2023
Line 105:		Line 105:
	'''_bcc''' = email address that receives a copy of the email, but not visible to anyone else		'''_bcc''' = email address that receives a copy of the email, but not visible to anyone else

	'''~~_replyto~~''' = email address used when someone replies to the send email		'''_reply-to''' = email address used when someone replies to the send email

	'''_header''' = Title name of Wiki page with the email letterhead		'''_header''' = Title name of Wiki page with the email letterhead

2023-03-31T20:13:32Z

ws-class-props
← Older revision		Revision as of 22:13, 31 March 2023
Line 1:		Line 1:
	{{Doc properties		{{Doc properties
	\|Subject version=2.0		\|Subject version=2.0,2.1
	\|Doc subject=DevOps:Doc/FlexForm		\|Doc subject=DevOps:Doc/FlexForm
	\|Doc sort order=220		\|Doc sort order=220

2023-03-15T13:38:04Z

← Older revision		Revision as of 15:38, 15 March 2023
Line 80:		Line 80:
	\|no		\|no
	\|}		\|}

			Mail addresses can be also be formatted. It can be '''person@company.com''', but you can also use '''Mr. Person [person@company.com]'''. The email will then be addressed to Mr. Person.


	All the elements needed to send an email can be set inside the email template. You can create multiple email templates. You simply tell FlexForm what email template to use in the form. The elements that can be set at form level will override any defined elements in the template.		All the elements needed to send an email can be set inside the email template. You can create multiple email templates. You simply tell FlexForm what email template to use in the form. The elements that can be set at form level will override any defined elements in the template.

Line 144:		Line 148:
	<p>Best regards</p>		<p>Best regards</p>
	</syntaxhighlight>		</syntaxhighlight>

			=== Parsing ===
			FlexForm will first parse the email template and then substitute form names in the email template with the form values. If you want to have this reversed, use the '''parselast''' argument on the _email function.

2023-03-01T20:09:45Z

← Older revision		Revision as of 22:09, 1 March 2023
Line 82:		Line 82:
	All the elements needed to send an email can be set inside the email template. You can create multiple email templates. You simply tell FlexForm what email template to use in the form. The elements that can be set at form level will override any defined elements in the template.		All the elements needed to send an email can be set inside the email template. You can create multiple email templates. You simply tell FlexForm what email template to use in the form. The elements that can be set at form level will override any defined elements in the template.

	All form elements that should be send with the email, must be defined in the email template. If you have ~~a _field~~ element of type text and a name of "address" and you want to send this with the email, you have to put the name of the field inside the template with a "$"-sign in front of it( in this case $address). See examples.		All form elements that should be send with the email, must be defined in the email template. If you have an input element of type text and a name of "address" and you want to send this with the email, you have to put the name of the field inside the template with a "$"-sign in front of it( in this case $address). See examples.
	===Form Parameters===		===Form Parameters===
	'''to''' = recipients email address		'''to''' = recipients email address