...
Option | Description | ||||||
---|---|---|---|---|---|---|---|
Notice | The action triggers the notification.
| ||||||
Post URL/Email | The URL to post to, or the email address to email, when the notice is triggered | ||||||
HTTP Code | The HTTP Response Code returned by the URL that signifies a successful transmission. | ||||||
Response Contains | Some portion of the output returned by the URL that signifies a successful transmission. This can be used separately, or in conjunction with the HTTP Code for more refined control over successful responses. | ||||||
From Email | The address to send email notifications from. | ||||||
Subject | The subject of the email notification. | ||||||
HTML/Text | The HTML and Text body content for the email notification. |
...
Package Option
...
Notification Tags
Service option notifications are executed when an action is performed on the service.
...
The action triggers the notification.
Option | Description |
---|---|
Add | Executed when a service is created. |
Edit | Executed when a service is updated. |
Suspend | Executed when a service is suspended. |
Unsuspend | Executed when a service is unsuspended. |
Cancel | Executed when a service is canceled. |
Renew | Executed when a service is renewed. That is, the invoice generated for the service renewal is paid. |
Package Change | Executed when the package is changed for the service. |
...
The service option notification emails allow for the following tags:
Tags | Description | Notes |
---|---|---|
{*} | The value submitted for this custom field | Every custom service field or package field has a tag associated with it, this tag is labeled by the fields name represented here by * |
{*_name} | This is the label associated with the submitted value for fields of type select or radio | This tag is only available for radio and select fields |
{*_values} | This is a list of checked boxes for this field each containing the box's label and value | This tag is only available for checkbox fields |
{_action} | The code of the action for which this notification is being sent | |
{_package.id} | The system-level service ID | The _package tag is not available for the package addition notification |
{_package.description} | The package's description | |
{_package.module_row} | The ID of the module row the package is associated with | |
{_package.status} | The status of the package |
Info | ||
---|---|---|
| ||
The {*_values} contains data in the following format. For a guide on using email tags in Blesta see the 'Customizing Emails' page.
custom_1_values = array ( array ( 'value' => ' 1' , 'name' => ' Option 1' ), array ( 'value' => ' 2' , 'name' => ' Option 2' ) ); |
Expand | |||||||
---|---|---|---|---|---|---|---|
| |||||||
Due to the nature of tag objects containing several fields, many of which are likely irrelevant for use in email templates, but may be useful to you in certain circumstances, a dump of the tags are shown below.
|
Service Option Notifications
Service option notifications are executed when an action is performed on the service.
Option | Description | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Notice | The action triggers the notification.
| ||||||||||||||||
Post URL/Email | The URL to post to, or the email address to email, when the notice is triggered | ||||||||||||||||
HTTP Code | The HTTP Response Code returned by the URL that signifies a successful transmission. | ||||||||||||||||
Response Contains | Some portion of the output returned by the URL that signifies a successful transmission. This can be used separately, or in conjunction with the HTTP Code for more refined control over successful responses. | ||||||||||||||||
From Email | The address to send email notifications from. | ||||||||||||||||
Subject | The subject of the email notification. | ||||||||||||||||
HTML/Text | The HTML and Text body content for the email notification. |
Service Option Notification Tags
The service option notification emails allow for the following tags:
Tags | Description | Notes |
---|---|---|
{*} | The value submitted for this custom field | Every custom service field or package field has a tag associated with it, this tag is labeled by the fields name represented here by * |
{*_name} | This is the label associated with the submitted value for fields of type select or radio | This tag is only available for radio and select fields |
{*_values} | This is a list of checked boxes for this field each containing the box's label and value | This tag is only available for checkbox fields |
{_action} | The code of the action for which this notification is being sent | |
{_service.id} | The system-level service ID | The _service tag is not available for the service addition notification |
{_service.status} | The service status | |
{_service.date_added} | The UTC datetime stamp of the date the service was added | Formatted as "YYYY-MM-DD HH:MM:SS" |
{_service.date_renews} | The UTC datetime stamp of the service renew date | Formatted as "YYYY-MM-DD HH:MM:SS" |
{_service.date_last_renewed} | The UTC datetime stamp of the service's last renew date | Formatted as "YYYY-MM-DD HH:MM:SS" |
{_service.date_suspended} | The UTC datetime stamp of the date the service was suspended | Formatted as "YYYY-MM-DD HH:MM:SS" |
{_service.date_canceled} | The UTC datetime stamp of the date the service was canceled | Formatted as "YYYY-MM-DD HH:MM:SS" |
{_package.id} | The system-level service ID | |
{_package.description} | The package's description | |
{_package.module_row} | The ID of the module row the package is associated with | |
{_package.status} | The status of the package | |
{_other.*} | The _other tag contains additional information, most of which is received through user input | Here * is the name of the field to access from the other tag (e.g. pricing_id) |
Info | ||
---|---|---|
| ||
The {*_values} contains data in the following format. For a guide on using email tags in Blesta see the 'Customizing Emails' page.
custom_1_values = array ( array ( 'value' => ' 1' , 'name' => ' Option 1' ), array ( 'value' => ' 2' , 'name' => ' Option 2' ) ); |
Expand | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
Due to the nature of tag objects containing several fields, many of which are likely irrelevant for use in email templates, but may be useful to you in certain circumstances, a dump of the tags are shown below.
|
...
Creating Packages
Info | ||
---|---|---|
| ||
Universal Module product service field names are used for the email tag. For example, a service field with the name "hostname" would result in a tag available to the welcome email of {service.hostname}. Universal module products are unique in this regard because each product may have different tags, defined by the staff member who created them. |