Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
maxLevel2
minLevel2
absoluteUrltrue
excludeRelated Pages
typeflat
separatorpipe

Overview

You can use one or more JSON triggers in a Comalatech 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)
pageJSON Triggers

o

Each trigger looks for a different change of state event.

  • on a change of state to QM - In Review  an email is sent to the users who have been added as a value to the workflow parameter @QT@, also an informative message dialog is shown
  • on a change of state to QM - In Approval  an email is sent to the users who have been added as a value for the workflow parameter @QT@ and the users who are members of the Confluence user groups added as a value for the workflow parameter @QM@, also an informative message dialog is shown
  • on a change of state to QM - Published  an email is sent to the user who created the page using the value reference @Creator@, also an informative message dialog is shown

Here's the JSON notation in full for these three 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": will be required in the JSON code if added to a workflow using the JSON editor. In workflow builder you do not have to add the "triggers": JSON element.You can add the JSON to the workflow in workflow builder.

Image Removed

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

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

Image Added


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

Related Pages

User Guide

Reviewing Content

Add a JSON trigger using workflow builder

Child pages (Children Display)
pageAdd a JSON trigger using workflow builder
first1

Notifications