Status actions - Revision history

Tvi at 10:13, 9 April 2024

2024-04-09T10:13:01Z

← Older revision		Revision as of 12:13, 9 April 2024
Line 38:		Line 38:
	=== Task create ===		=== Task create ===
	This will dynamically create new tasks for any '[[FieldTask\|Task list]]' fields found in the solution.		This will dynamically create new tasks for any '[[FieldTask\|Task list]]' fields found in the solution.


	=== Codeunit ===		=== Codeunit ===
Line 43:		Line 44:

	Except for timed actions you would implement this inside a [[Codeunit/Formevents]].		Except for timed actions you would implement this inside a [[Codeunit/Formevents]].


	=== Export ===		=== Export ===
Line 85:		Line 87:
	\|-		\|-
	\|}		\|}


	=== Shift status ===		=== Shift status ===
Line 90:		Line 93:

	This type of action only makes sense to use in timed actions.		This type of action only makes sense to use in timed actions.


	=== Webhook ===		=== Webhook ===

Tvi at 10:12, 9 April 2024

2024-04-09T10:12:30Z

← Older revision		Revision as of 12:12, 9 April 2024
Line 34:		Line 34:

	Read about special tags and formatting her [[Tutorial/Status_notifications]]		Read about special tags and formatting her [[Tutorial/Status_notifications]]


	=== Task create ===		=== Task create ===

Tvi: Formatting and info about webhooks

2024-04-09T10:12:15Z

Formatting and info about webhooks

← Older revision		Revision as of 12:12, 9 April 2024
Line 91:		Line 91:

	=== Webhook ===		=== Webhook ===
	~~!This functionality is not ready!~~

	This action performs an HTTP-request with parameters from the updated item and update the item based on the result.		This action performs an HTTP-request with parameters from the updated item and update the item based on the result.
	{\| class="wikitable"		{\| class="wikitable"
Line 135:		Line 133:
	\|Fields that should be updated based on the data returned.		\|Fields that should be updated based on the data returned.
	If type is "raw", only the first item in this list will be updated, and it will be set to the entire response.		If type is "raw", only the first item in this list will be updated, and it will be set to the entire response.

			If type is "json", attributes with keys formatted as <code>[FIELDNAME]</code> will be updated from the given key in the returned data.
	\|}		\|}
			In <code>params</code> and <code>body</code>, values formatted as <code>[FIELDNAME]</code>, will be filled with data from the record.

	==== Sample ====		==== Sample ====
Line 151:		Line 152:
	},		},
	"body": {		"body": {
	"id":1,		"id": 1,
	"name":"~~John Doe~~",		"name": "[NAME]",
	"email":"john.doe@example.com"		"email": "john.doe@example.com"
	},		},
	"update": {		"update": {

Nun: /* Sample */

2023-07-18T08:25:56Z

Sample

← Older revision		Revision as of 10:25, 18 July 2023
Line 140:		Line 140:
	<syntaxhighlight lang="json">		<syntaxhighlight lang="json">
	{		{
	"url": "http://localhost:3001/users/2",		"url": "http://localhost:3001/users/1",
	"method": "~~GET~~",		"method": "PUT",
	"type": "json",		"type": "json",
	"headers": {		"headers": {
	"~~Authorization~~": "Bearer XYZ"		"authorization": "Bearer XYZ",
			"Content-type": "application/json"
	},		},
	"params": {		"params": {
	"param": "DATA"		"param": "DATA"
	},		},
	"body": "",		"body": {
			"id":1,
			"name":"John Doe",
			"email":"john.doe@example.com"
			},
	"update": {		"update": {
	~~"[LINK]": "info.link",~~		"[NAME]": "name"
	"[NAME]": "~~info.~~name"
	}		}
	}		}
	</syntaxhighlight>		</syntaxhighlight>

Nun: /* Webhook */

2023-07-17T09:35:11Z

Webhook

← Older revision		Revision as of 11:35, 17 July 2023
Line 91:		Line 91:

	=== Webhook ===		=== Webhook ===
			!This functionality is not ready!

	This action performs an HTTP-request with parameters from the updated item and update the item based on the result.		This action performs an HTTP-request with parameters from the updated item and update the item based on the result.
	{\| class="wikitable"		{\| class="wikitable"

Nun: /* Action types */

2023-07-17T09:34:28Z

Action types

← Older revision		Revision as of 11:34, 17 July 2023
Line 89:		Line 89:

	This type of action only makes sense to use in timed actions.		This type of action only makes sense to use in timed actions.

			=== Webhook ===
			This action performs an HTTP-request with parameters from the updated item and update the item based on the result.
			{\| class="wikitable"
			!Datapoint
			!
			!Type
			!Notes
			\|-
			\|url
			\|Required
			\|String
			\|The url that is to be called. This supports input of parameters from the item.
			\|-
			\|method
			\|Optional
			\|String
			\|The HTTP-method of the call, one of: "POST", "GET", "PUT" or "DELETE". Default: "GET".
			\|-
			\|type
			\|Optional
			\|String
			\|The datatype of data returned, supported types: "json", "raw" or "XML". Default: "json".
			\|-
			\|headers
			\|Optional
			\|Map
			\|A map of extra headers that should be set
			\|-
			\|params
			\|Optional
			\|Map
			\|Path parameters that should be set and send.
			\|-
			\|body
			\|Optional
			\|String
			\|A string that will be set and send. Not available for "GET".
			\|-
			\|update
			\|Optional
			\|Map
			\|Fields that should be updated based on the data returned.
			If type is "raw", only the first item in this list will be updated, and it will be set to the entire response.
			\|}

			==== Sample ====
			<syntaxhighlight lang="json">
			{
			"url": "http://localhost:3001/users/2",
			"method": "GET",
			"type": "json",
			"headers": {
			"Authorization": "Bearer XYZ"
			},
			"params": {
			"param": "DATA"
			},
			"body": "",
			"update": {
			"[LINK]": "info.link",
			"[NAME]": "info.name"
			}
			}
			</syntaxhighlight>

Tvi: 38 revisions imported

2021-12-10T10:55:32Z

38 revisions imported

← Older revision

Revision as of 12:55, 10 December 2021

old>Admin: /* Notification */

2020-11-18T07:57:56Z

Notification

← Older revision		Revision as of 09:57, 18 November 2020
Line 33:		Line 33:
	* Interface tokens (external users)		* Interface tokens (external users)

	Read about special tags and formatting her [Tutorial/Status_notifications]		Read about special tags and formatting her [[Tutorial/Status_notifications]]

	=== Task create ===		=== Task create ===

old>Admin: /* Notification */

2020-11-18T07:57:39Z

Notification

← Older revision		Revision as of 09:57, 18 November 2020
Line 17:		Line 17:

	=== Notification ===		=== Notification ===
	This action sends an email for ~~one~~ or ~~more users~~.		This action sends an email for users or groups.

	Various options for the target email exists, including		Various options for the target email exists, including
	* Raw email: Static reference		* Raw email: Static reference
			* User: A specific user in the database
	* Field value: The contents of another field		* Field value: The contents of another field
	* ~~User: A specific user in the database~~		** Email
			** Phone (sent by SMS)
	~~The email body may contain dynamic values in the tag format {FIELD}, which will be populated with field values for the item in question.~~		** CPR nr (sent by eBoks)

	~~The record resume has a special {RESUME} tag~~

	~~Other tags exist to help out with values not in the item~~
	* ~~{LINK}~~
	* ~~{NOLINK}~~
	* ~~{RAWLINK}~~

	~~If neither {LINK}, {NOLINK} nor {RAWLINK} is found within the email body, the link for item will be appended to the bottom of the email.~~

	~~If no interface is chosen, a normal show link for~~ the ~~item will be~~ generated~~. Otherwise a token link will be generated, requiring~~ the ~~interface~~ to ~~be of~~ the ~~type UPDATE.~~		Different types of content can be includeded in the emails
			* Data from the record
			* Document generated using data of the record
			* Links to the record (internal users)
			* Interface tokens (external users)

	~~Finally URLs can be entered by using {APPURL} in front of a relative reference. Example: {APPURL}~~/~~login~~		Read about special tags and formatting her [Tutorial/Status_notifications]

	=== Task create ===		=== Task create ===

old>Admin: /* Notification */

2019-08-28T08:32:48Z

Notification

← Older revision		Revision as of 10:32, 28 August 2019
Line 30:		Line 30:
	Other tags exist to help out with values not in the item		Other tags exist to help out with values not in the item
	* {LINK}		* {LINK}
	* {NOLINK}		* {NOLINK}
			* {RAWLINK}

	If neither {LINK} nor {~~NOLINK~~} is found within the email body, the link for item will be appended to the bottom of the email.		If neither {LINK}, {NOLINK} nor {RAWLINK} is found within the email body, the link for item will be appended to the bottom of the email.

	If no interface is chosen, a normal show link for the item will be generated. Otherwise a token link will be generated, requiring the interface to be of the type UPDATE.		If no interface is chosen, a normal show link for the item will be generated. Otherwise a token link will be generated, requiring the interface to be of the type UPDATE.