Meta Data
Meta Data allows you to create slots to store hidden data within messages. Data stored as a meta data value is sent along with a message. Meta Data is also copied when a message is replied to or resent. You can also use meta data as a source for visibility rules and conditional link commands.
To add a meta data item to a template click on the "Add Meta Data" button. Then enter a value for the key. A meta data item's key is like the external label of a field and allows you to refer to that item in other parts of the template and is also the name of the XML tag used when exporting or importing messages from other systems.
Call and Set Value Commands use meta data for their source values. The phone number for a Call Command must be stored as a meta data value. Similarly a Set Value Command can update a meta data value, a technique that is useful when creating workflows within a message. For example a meta data key could hold the status or state of a job with different fields or commands visible depending on that value.
When combined with Default Data, meta data items allow you to capture extra information about the sender of a message. For example adding a meta data key for an employee code and then setting that value per mobile account will allow you to capture the employee information for that mobile user without them having to enter it on the phone each time they send a message.
Meta Data can only contain string values.
Default Data
Allows you to set automatic defaults for data items. This includes Text Fields, Text Box Fields, String Fields and Meta Data items. When set at the template level values are global and applied the same for each user of the template. Typically Default Data is used at the mobile account level to customise a templates values for that user. If a value is set in the template default data and the mobile account default data then the mobile account value will be used.
Default Data can only contain string values.
