Variables for changing terminology and utilising values stored in RefTracker

In addition to the variables for each field in the question tables of the Data dictionary, there are some other variables that can be used in QuickText and email templates and other places in RefTracker.

Surrounding a Data dictionary variable name with curly brackets will give you the current value of that variable e.g {Question_no} will give you the current question’s Question number e.g. RT1234.

Adding “Label_” before any Data dictionary variable name will give you the name of that variable rather than the current value of it e.g. {label_question_no} gives “Question” or perhaps “Request” if you have changed the Data dictionary label for the question_no field to “Request”.

If you want to change the way requests are referred to in your system, get your Altarama support representative to change the Data dictionary table name for the Question code table to your preferred terminology e.g Request to Offer.  (The change is made in Code tables>System>Database tables.)  Request is the default name.

{question} is used to refer to the question/request throughout RefTracker, and will be replaced by the new name of this table.  If this variable is the first thing in a sentence the first letter will be capitalised.
{questions} should be used if the Database table name needs to be pluralised e.g. where “Enquiry” needs to become “Enquiries”.
If you are going to make this change it is also important that you check, and correct if necessary, the labels that your system is using for the {question_no} and {question_text} variables in your Data dictionary Question table so they match the changes you made to your terminology for questions/requests.

If you want to change the way end users are referred to in your system, get your Altarama support representative to change the Data dictionary table name for the Client Code table to your preferred terminology e.g Requester to Patron.  (The change is made in Code tables>System>Database tables.)  Requester is the default name.

{client} is used to refer to the end user throughout RefTracker, and will be replaced by the new name of this table.  If this variable is the first thing in a sentence the first letter will be capitalised.

You can use any of the {Staff_*} variables defined in System>Data dictionary menu>System tables>Staff to show attributes of the staff member assigned this question. 

You can also use the {CurrentUser*} variables that provide the contact details for the currently signed on user (as opposed to the staff member allocated the question).

The CurrentUser variables are:

{CurrentUserName} = Currently signed on Staff member name                        
{CurrentUserEmai} = Currently signed on Staff member email address
{CurrentUserPhone} = Currently signed on Staff member phone number
{CurrentUserTitle} = Currently signed on Staff member title
{CurrentUserNumber} = Currently signed on Staff member staff number
{CurrentUserLocation} = Currently signed on Staff member staff location

Further there are some parameters that can be used as variables:

{Parm_Organisation} = the Organisation name provided in parameter 1.0
{Parm_Service_Name} = the Service name provided in parameter 1.1
{Parm_ContactPhone} = the Organisation Phone number provided in parameter 1.10
{Parm_ContactEmail} = the Organisation Email address provided in parameter 1.11
{Parm_ContactURL} = the Organisation URL provided in parameter 1.12