Versions Compared

Key

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

To create a new or edit a template, click Create or copy an existing out-of-box template or another custom template for an event. Image Removed

...

To edit an existing template, click the link under the Template column.

...

Edit Template

The Edit Template screen shows the Template Components from the copied template, The header some basic template information as well as the template components. The { } Custom header shown below indicates it's a custom template.Image Removed

...

Info

Code Editor

For more details on using the code editors on this page for Email Subject and Email Body, see Working with the Code Editor


Field

Description

Template Name

Name

The name of the

new

template.

Events

Associate an event for the template (

Ex

e.g. Workflow Request Completed). You can also assign more than one event to the same template.

Email Subject

The script to be used for email subject for the event(s).

Email Body

The script to be used for email body for the event(s).

Payload

The payload is used in the code editor to give suggestions of what variables and methods are available when accessing the $payload variable, as this will vary depending on the event. If more than one event is associated to this template, use this to switch between the selected events.

Template Components

The Email Subject and Email Body fields shows show the script needed to generate the content for the email message. FlexDeploy provides rich set of APIs to generate the HTML content. See the Java docs for more details on the functions which can be referenced with the $FLEXDEPLOY object. You can also use your custom styles as needed. For help with syntax of the Velocity Template Language (VTL) and examples, see the Apache Velocity User Guide. 

Payload

Both Subject and Body will be able to reference the payload object related to an event. Using the shorcuts shortcuts, you will be able to access all the data associated to an event using the variable $payload. Below The below table shows the Events events and associate payload objects.

Events

Payload Object Name

Workflow Request Scheduled
Workflow Request Rejected
Workflow Request Deploying
Workflow Request Completed
Workflow Request FailedNotifProjectWorkflowRequestFolder Request Scheduled
Folder Request Rejected
Folder Request Deploying
Folder Request Completed
Folder Request FailedNotifApplicationRequest

Api Token Expiration

TokenExpirationPayload

Pipeline Gate Approval Assigned

Pipeline Gate Approval Rejected

PipelineGateApprovalAssignedOrRejectedPayload

Pipeline Manual Step Assigned

PipelineManualStepAssignedPayload

Pipeline Step Execution Failed

PipelineStepExecFailedPayload

Workflow PreDeploy Review Assigned

Workflow PreDeploy Review Rejected

ProjectReviewTaskPayload

Workflow Approval Assigned

Workflow Request Pending Approval

Workflow Approval AssignedNotifProjectTask

ProjectApprovalTaskPayload

Workflow Request Failed

Workflow Request

Pending Approval

Ready

Workflow

Predeploy Pending Review Workflow Predeploy Review Folder Request Pending Approval
Folder Approval AssignedNotifApplicationTaskPipeline Gate Approval AssignedNotifPipelineGateTaskPipeline Manual Step AssignedNotifPipelineStepTaskPipeline Step Exec FailedNotifPipelineStepExectionRequest

Request Rejected

NotifProjectReviewTask

Workflow Request Scheduled

ProjectWorkflowRequestPayload


Info

Each payload object of an event holds a different set of data. Please use the link for each payload and go through the methods available to structure your HTML content for the template. You can always use the Preview and Send Test options to test and validate your script using the test data available.


Info

All out-of-box templates use custom styling. The style settings can be found inside the application folder configured as part of the FlexDeploy installation. The files are located at <flexdeploy install root>/application/templates/notifications.

Any changes to the styles have to be tested thoroughly to make sure they work with the mail clients used within your organization. Please save a copy of the files before making any changes. Check FlexDeploy server logs for any errors while testing your custom changes. Look for "org.apache.velocity.runtime" text for any exceptions.