Events

Common Event Fields

Each incoming event passes an event payload to the listener depending on the event type. Below are example payloads for each event type.

All Event messages have the following top level fields:

Key

Description

Key

Description

eventType

The event type that triggered this Event. e.g. Workflow Completed, Task Created.

actor

The actor, generally a user, that triggered this event.

object

The object the event occurred on. This could be the Project name, Release name etc.

timestamp

The time the event occurred.

payload

The specific event payload (see examples below)

Events

Comment Added

The Comment Added event is triggered anytime there is a comment created throughout FlexDeploy. As and example use case, you could use this event to create a Jira Ticket anytime a comment was created and contained the words “Jira”.

{ "eventType": "Comment Added", "actor": "fdadmin", "object": "Comment - 1913", "timestamp": "2023-10-18 05:45:44 -0500", "payload": { "createdBy": "fdadmin", "createdOn": "2023-10-18 05:45:44 -0500", "updatedBy": "fdadmin", "updatedOn": "2023-10-18 05:45:44 -0500", "commentId": 1913, "oldCommentText": null, "commentText": "{\"type\":\"doc\",\"content\":[{\"type\":\"paragraph\",\"content\":[{\"type\":\"text\",\"text\":\"test4\"}]}]}", "objectId": 33313, "objectType": "WORK_ITEM" } }

Comment Updated

The Comment Updated event is triggered anytime a comment is edited throughout FlexDeploy.

{ "eventType": "Comment Updated", "actor": "fdadmin", "object": "Comment - 1913", "timestamp": "2023-10-18 05:45:44 -0500", "payload": { "createdBy": "fdadmin", "createdOn": "2023-10-18 05:45:44 -0500", "updatedBy": "fdadmin", "updatedOn": "2023-10-18 05:45:44 -0500", "commentId": 1913, "oldCommentText": "{\"type\":\"doc\",\"content\":[{\"type\":\"paragraph\",\"content\":[{\"type\":\"text\",\"text\":\"test3\"}]}]}", "commentText": "{\"type\":\"doc\",\"content\":[{\"type\":\"paragraph\",\"content\":[{\"type\":\"text\",\"text\":\"test4\"}]}]}", "objectId": 33313, "objectType": "WORK_ITEM" } }

Comment Deleted

The Comment Updated event is triggered anytime a comment is deleted throughout FlexDeploy.

{ "eventType": "Comment Updated", "actor": "fdadmin", "object": "Comment - 1913", "timestamp": "2023-10-18 05:45:44 -0500", "payload": { "createdBy": "fdadmin", "createdOn": "2023-10-18 05:45:44 -0500", "updatedBy": "fdadmin", "updatedOn": "2023-10-18 05:45:44 -0500", "commentId": 1913, "oldCommentText": "{\"type\":\"doc\",\"content\":[{\"type\":\"paragraph\",\"content\":[{\"type\":\"text\",\"text\":\"test3\"}]}]}", "commentText": null, "objectId": 33313, "objectType": "WORK_ITEM" } }

Package Created

The Package Created event is triggered anytime a package is created for a project throughout FlexDeploy. This could possibly be used as a event to execute a script to automatically add the package to a release whenever one is created for a specific project.

Package Status Updated

@Since 7.0.0.1 - The Package Status Updated event is triggered anytime a package’s status is changed (‘Active’, ‘Inactive’, ‘Completed’) for a project throughout FlexDeploy. This could possibly be used as a event to execute a script to automatically remove the package from a release whenever it is inactivated or completed for a specific project.

Pipeline Stage Completed

The Pipeline Stage Completed event is triggered whenever a stage succeeds or fails in a Release Pipeline Execution. Common use cases can include logic you want to perform after EVERY pipeline execution regardless of the Pipeline or Release being used. For example you may want to create a Service Now incident whenever the Production Stage fails in any pipeline. This could be easily accomplished by listening for this event but filtering for a status of FAILED and environment of PRODUCTION.

Release Started

The Release Started event is triggered whenever a release is started in FlexDeploy. Common use cases can include logic you want to perform after any release is started. For example you may want to start a sprint in Jira whenever the release is started.

Release Ended

The Release Ended event is triggered whenever a release is endedin FlexDeploy. Common use cases can include logic you want to perform after any release is ended. For example you may want to end a sprint in Jira whenever the release is ended.

Snapshot Completed

The Snapshot Completed event is triggered whenever a snapshot eventually completes successfully or fails to build.

Tag Assigned

The Tag Assigned event is triggered whenever a tag is assigned to an object like a project, environment, or target group.

Tag Unassigned

The Tag Unassigned event is triggered whenever a tag is unassigned from an object like a project, environment, or target group.

Task Created

The Task Created event is triggered whenever a human task is created. This can be triggered from either a standalone project or a release.

Task Approved

The Task Approved event is triggered whenever a human approval task is approved.

Task Rejected

The Task Rejected event is triggered whenever a human approval task is rejected.

User Created

The User Created event is triggered whenever a user is created inside FlexDeploy. This could be particularly useful when configuring users in an Single Sign-On (SSO) Realm setup.

Workflow Completed

The Workflow Completed event is triggered whenever a workflow execution succeeds or fails. Note that this event will trigger for ALL workflow types.

The testSuiteExec array in the payload will return all test suite executions from the workflow. This is most common in TEST workflows but tests can be run from any workflow type (Build, Deploy, Utility, etc..).

Workflow Completed (DEPLOY) Event Payload

Workflow Completed (TEST) Event Payload

Work Item Created

The Work Item Created event is triggered whenever a work item is created.

Work Item Updated

The Work Item Updated event is triggered whenever work item is updated.

 

The following macros are not currently supported in the footer:
  • style