The Notification template allows users to create an alternate language template to fire notifications. In other words, it is a user customized form of the existing "Fire Notification" action template.
An example of using the finished Notification template in a language rule might be as follows:
Here is how this template would be defined:
Here are the possible settings on this screen:
Name
Specifies the name of the vocabulary template. The name is used for irSDK access.
Display Name
Name of the template to be displayed in the business language template list.
Menu Group
Menu group under which the template will be listed. The user can choose to add his template to an existing menu group or can create his own menu group.
Scope
The scope of the template availability can be limited to only the context of the previously selected entity by checking "Available in rules and calculations for this entity." The availability can also be extended to those rule elements which have a reference to the previously selected entity by checking "Available in rules and calculations for entities referencing this entity."
Placeholders
The placeholders created in business language are configured here. For a detailed description of placeholders refer to "Configuring Placeholders".
Business Language
Business language to be displayed in the business language editor. Placeholders can be added to the template by enclosing them within $ symbols.
Notification
Type
Type of notification, it can either be Informational, Warning or Error.
Mode
When checked multiple notifications will be allowed to deploy. Mode When checked multiple notifications will be allowed to deploy.
Correlate Field
Associates this message with a particular field from the schema structure.
Message Expression
Specifies the actual message text. This text may contain embedded fields or rule expressions to provide context sensitive information in the message. For example, to refer to the "ItemQuantity" field, specify <%ItemQuantity%>.
Use a similar notation to refer to any placeholders, such as <%$placeholder1$%>.
Comments
0 comments
Please sign in to leave a comment.