Message Builder
- Ben Clark
- 1 Overview
- 2 Plugin Configuration
- 2.1 Step
Overview
Our users want to create a field with a “message” (Creative) that can have placeholders where other Fields in the flow can be automatically merged in.
The message itself could be straight text for a Twitter or SMS message or it could contain JSON or other code.
User can choose a “Template” for the Message from a field
User can choose the Field Delimiter
User can request line breaks are removed for the final message
User can automatically create and name the message field
Example:
An SMS rule is being built. The Rule needs a SMS message header created to ensure the SMS integration knows the correct details for each recipient. The User needs to pull into the SMS message header fields or Parameters.
Plugin Configuration
Step
Within the Step tab:
The following settings can be configured:
Setting | Description |
|---|---|
Step Name | Allows the Step to be given a unique descriptive name. |
Message Template | Contains the Message itself. This could be text or code as shown above. User will define the Field Placeholders using a Field Delimiter. The Field Delimiters can be selected by the user. (See below). |
Message Tempate From Field | This allows the User to select a Message Template from a field (See below). The Templates may be created using other Message Builder steps and a switch case or other step can switch from one Template to another to provide the ability to service multiple offers in the same Rule. Selecting this causes the Message Template box to become inactive. |
Message Template Field | Allows the User to select the Message Template field. |
Remove Line-Breaks | Will remove line breaks from the final Message. |
Field Delimiters | User can select the Field Delimiters used in the Message Template. |
Output Field | Allows the user to create and name the Outout Field for the Message Template. |