Requirement and Complaint Management Parameters

Article Summary

Share feedback

Thanks for sharing your feedback!

Some parameters and explanations that can be used in Requirement and Complaint Management e-mail templates are as follows.

header	header
{CONTACT_CONTID}	Contact’s unique Id
{CONTACT_FIRSTNAME}	Contact’s name
{CONTACT_LASTNAME}	Contact’s surname
{CONTACT_NAME}	Contact’s name and surname
{CONTACT_EMAIL}	Contact’s active email address
{CONTACT_EMAIL1}	Contact’s 1. email address
{CONTACT_EMAIL2}	Contact’s 2. email address
{CONTACT_EMAIL3}	Contact’s 3. email address
{CONTACT_EMAIL4}	Contact’s 4. email address

header	header
{ASSIGNED_CONTID}	Person’s unique Id
{ASSIGNED_FIRSTNAME}	Person’s name
{ASSIGNED_LASTNAME}	Person’s surname
{ASSIGNED_NAME}	Person’s name and surname
{ASSIGNED_EMAIL}	Person’s active email address
{ASSIGNED_EMAIL1}	Person’s 1. email address
{ASSIGNED_EMAIL2}	Person’s 2. email address
{ASSIGNED_EMAIL3}	Person’s 3. email address
{ASSIGNED_EMAIL4}	Person’s 4. email address

header	header
{ASSIGNER_CONTID}	Person’s unique Id
{ASSIGNER_FIRSTNAME}	Person’s name
{ASSIGNER_LASTNAME}	Person’s surname
{ASSIGNER_NAME}	Person’s name and surname
{ASSIGNER_EMAIL}	Person’s active email address
{ASSIGNER_EMAIL1}	Person’s 1. email address
{ASSIGNER_EMAIL2}	Person’s 2. email address
{ASSIGNER_EMAIL3}	Person’s 3. email address
{ASSIGNER_EMAIL4}	Person’s 4. email address

Informations Of Department That Assigned To Requirements/Complaints (Assigned Department)To Top

header	header
{ASSIGNEDDEP_DEPARTMENTID}	Department Unique Id
{ASSIGNEDDEP_DEPARTMENT}	Department name(Returns null if the name is empty)
{ASSIGNEDDEP_NAME}	Department name(Returns null if the name is empty)
{ASSIGNEDDEP_EMAIL}	Department email address

header	header
{ASSIGNERDEP_DEPARTMENTID}	Department Unique Id
{ASSIGNERDEP_DEPARTMENT}	Department name(Returns null if the name is empty)
{ASSIGNERDEP_NAME}	Department name(Returns null if the name is empty)
{ASSIGNERDEP_EMAIL}	Department email address

header	header
{REQUIREMENT}	Content of the introduction text of the Request / Complaint created
{LASTPOST}	Content of the last post of the Request / Complaint created
{RM_TYPE}	Requirement/Complaint Type
{RM_CATEGORY}	Requirement/Complaint Category
{RM_REQFILE}	It contains information about files added in first creation of requirement and during process. They are file name, date added and added by who
{RMLOG_POST}	Introduction text of Request/Complaint and content of all text written during process

header	header
{REQID}	Requirement/Complaint Unique Id
{TYPEID}	Requirement/Complaint Type Id
{CATEGORYID}	Requirement/Complaint Category Id
{REQSRC}	Requirement/Complaint Resource
{SENDER}	Requirement/Complaint sender data
{TARGET}	Requirement/Complaint target data
{REQDATE}	Requirement/Complaint date
{CONTID}	Requirement/Complaint Contact Id
{SUBJECT}	Requirement/Complaint Subject
{CONTENT}	Requirement/Complaint Content
{STATUS}	Requirement/Complaint Last Status
{SMVOLUME}	Requirement/Complaint Number of followers on twitter
{DEPARTMENTID}	Requirement/Complaint Department Unique Id
{ASSIGNED}	Requirement/Complaint Assigned Person Unique Id
{EXTERNALID}	Requirement/Complaint External Department Unique Id
{ORDERID}	Requirement/Complaint Order Id
{PLNDATE}	Requirement/Complaint Planned End Date
{ENDDATE}	Requirement/Complaint End Date
{MODULE}	Module used (COMP,REQ)
{RMVAR1-20}	Parameter contents used between 1-20. Example: {RMVAR1}

Was this article helpful?

Table of contents