...
Package Option Notification Tags
The service package 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 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 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} tag 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' )); |
...
| 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 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 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} tag 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' )); |
...