Template scope

All templates within HelpMaster have an "operating scope" that they will work in. Each template type contains a number of attributes that are used to define the scope of its use throughout the HelpMaster product suite. For example, some Job templates may be specifically designed to be used via the web interface, or the Email Manager. In such cases, this Job template would be marked as "Web enabled" and "Email Manager" enabled. Such markings tell HelpMaster how this template should be used, and it also enforces a number of validation and usage rules of such a template throughout the system.

A fully qualified Job template can be marked as "Web enabled" and "Email Manager enabled"
A fully qualified Action template can be marked as "Web enabled", "Email Manager enabled" and "Priority Manager enabled"

Fully Qualified Templates

Throughout this help file and within several message boxes that are displayed within HelpMaster, the term "fully qualified template" appears. A fully qualified template basically means that a template has a value specified for all of it's mandatory fields. This mandatory settings will change depending on which template entity type you're working with. For example, before a job can be logged, it requires a Priority code. Therefore, in order for a Job Template to become "fully qualified", it must have a Priority code specified in the template.

When a template is fully qualified, it means that it can be used by one of the other HelpMaster modules (Web Interface, Email Manager, Priority Manager) without requiring human intervention to use the template. All of the required information is already specified in the template and it just needs to be applied. This is particularly relevant when you have an automated process such as the Email Manager that needs to apply an Action template for example to an incoming email.

Note: A template does not have to contain full details about a particular entity. It may contain partial or incomplete information. If such a template is created and then used, the incomplete data fields will need to be manually filled-in by the current user.