Page Comparison

Table of Contents

maxLevel	2
minLevel	2
absoluteUrl	true
exclude	Related Pages
type	flat
separator	pipe

Overview

You can use one or more JSON triggers in a Comala Document Management workflow.

Using JSON triggers to create a custom email notification for different state changes

In our custom workflow, we have added three triggers.

JSON Triggers

Child pages (Children Display)

page	JSON Triggers

Image Removed

Image Added

Each trigger looks for a different change of state event.

Trigger One

On a change of state to QM - In Review

Code Block
{"event": "on-change-state", "conditions": [ {"state": "QM - In Review"}

There are two "actions:"

an email is sent to the users who have been added as a value to the workflow parameter @QT@
an informative message dialog is shown

Trigger Two

On a change of state to QM - In Approval

Code Block
{"event": "on-change-state", "conditions": [ {"state": "QM - In Approval"}

There are two "actions:"

an email is sent to
- the users who have been added as a value for the workflow parameter @QT@
- the users who are members of the Confluence user groups added as a value for the workflow parameter @QM@
an informative message dialog is shown

Trigger Three

On a change of state to QM - Published

Code Block
{"event": "on-change-state", "conditions": [ {"state": "QM - Published"}

There are two "actions:"

an email is sent to the user who created the page using the value reference @Creator@
an informative message dialog is shown

Here's the JSON notation in full for these three workflow triggers.

Code Block

"triggers":
[
	{"event": "on-change-state",
	"conditions":
	[
		{"state": "QM - In Review"}
	],
	"actions":
	[
		{"action": "send-email",
			"recipients":
			[
				"@QT@"
			],
			"notification": {"subject": "${content.title} is QM - In Review State",
				"title": "${content.title} is QM - IN REVIEW State",
				"body": "Hello, ${content.link} in the ${content.space} space is in QM - In Review state and needs to be reviewed"}},
		{"action": "set-message",
            "type": "info",
            "title": "This is the title of the dialog shown on your page",
            "body": "This is the body of the dialog shown on your page"}
	]},
	{"event": "on-change-state",
	"conditions":
	[
		{"state": "QM - In Approval"}
	],
	"actions":
	[
		{"action": "send-email",
			"recipients":
			[
				"@QT@",
				"@QM@"
			],
			"notification": {"subject": "${content.title} is QM - In Approval State",
				"title": "${content.title} is QM - In Approval State",
				"body": "Hello, ${content.link} in the ${content.space} space QM - In Approval"}},
		{"action": "set-message",
            "type": "info",
            "title": "This is the title of the dialog shown on your page",
            "body": "This is the body of the dialog shown on your page"}
	]},
	{"event": "on-change-state",
	"conditions":
	[
		{"state": "QM - Published"}
	],
	"actions":
	[
		{"action": "send-email",
			"recipients":
			[
				"@Creator@"
			],
			"notification": {"subject": "${content.title} is QM - Published State",
				"title": "${content.title} is QM - Published State",
				"body":"Hello, ${content.link} in the ${content.space} space QM - Published"}},
		{"action": "set-message",
            "type": "info",
            "title": "This is the title of the dialog shown on your page",
            "body": "This is the body of the dialog shown on your page"}
	]}
]

Info
Only one overall "`triggers":` notation will be required in the JSON code if added to a workflow using the JSON editor.

In the JSON markup multiple trigger events are enclosed in a single pair of "[" and "]" brackets prefaced by a single "triggers": JSON element.

You can add the JSON to the workflow in workflow builder.

Image Removed

Image Added

There is no need to add the opening "triggertriggers": JSON when adding the JSON code to workflow builder. Workflow builder will automatically add this when you save the changes to the workflow.