Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
emailstaffnotification [2019/07/24 12:51] – Justin Willey | emailstaffnotification [2019/08/01 17:33] (current) – List of topics Michael Scott | ||
---|---|---|---|
Line 3: | Line 3: | ||
Email Group Notifications provide a mechanism for maintaining single or groups of email addresses for use by Jobs and iqxWEB when distributing messages reports etc. Individual email addresses etc can then be changed in IQX without having to edit the jobs each time. | Email Group Notifications provide a mechanism for maintaining single or groups of email addresses for use by Jobs and iqxWEB when distributing messages reports etc. Individual email addresses etc can then be changed in IQX without having to edit the jobs each time. | ||
- | * Topic - a pre-agreed token e.g. RegisterCandidate or CompleteTimesheet | + | * Topic - a pre-agreed token, often shared with the IQXWeb Settings - Query Recipients. Examples in use are SUBMITCANDIDATE, |
* Email Address - can be one or more recipient addresses, separated by commas or semicolons | * Email Address - can be one or more recipient addresses, separated by commas or semicolons | ||
- | * Message Text - the text of the email. May contain tokens such as < | + | * Message Text - the text of the email - if invoked by RequestLinkedEmailStaffNotification (see below). May contain tokens such as < |
* Supported tokens are: | * Supported tokens are: | ||
* {personid} | * {personid} | ||
* {companyid} | * {companyid} | ||
* {vacancyid} | * {vacancyid} | ||
- | * {loadform} | + | * {loadform} |
* Division and Department can be used to narrow down the recipients for a particular notification. If they are left blank this recipient will receive all notifications for the topic | * Division and Department can be used to narrow down the recipients for a particular notification. If they are left blank this recipient will receive all notifications for the topic | ||
Line 18: | Line 18: | ||
A Scheduled Job, EmailStaffNotifier.xml or equivalent, must be running to do the actual sending. ++++Sample Job|<sxh xml><? | A Scheduled Job, EmailStaffNotifier.xml or equivalent, must be running to do the actual sending. ++++Sample Job|<sxh xml><? | ||
<Job title=" | <Job title=" | ||
- | < | + | |
- | < | + | < |
- | < | + | < |
- | select id, topic, body, hyperlink, departmentid, | + | select id, topic, body, hyperlink, departmentid, |
- | from EmailStaffNotification | + | from EmailStaffNotification |
- | where Dispatched is null and Requested > current date - 3 | + | where Dispatched is null and Requested > current date - 3 |
- | ]]> | + | ]]> |
- | </ | + | </ |
- | < | + | < |
- | < | + | < |
- | <If x1=" | + | <If x1=" |
- | < | + | < |
- | < | + | < |
- | <If x1=" | + | <If x1=" |
- | < | + | < |
- | < | + | < |
- | < | + | < |
- | </ | + | </ |
- | </ | + | </ |
- | < | + | < |
- | < | + | < |
- | < | + | < |
- | </ | + | </ |
- | </ | + | </ |
- | < | + | < |
- | < | + | < |
- | </ | + | </ |
- | </ | + | </ |
- | </ | + | </ |
</ | </ | ||
</ | </ | ||
Line 52: | Line 52: | ||
There are two alternative functions which can be invoked from a web net procedure or anywhere else:< | There are two alternative functions which can be invoked from a web net procedure or anywhere else:< | ||
- | pTopic links to the Topic in Agency Setup - Email Group Notifications. pHyperLink is the woodpecker form to load with parameters e.g. person/ | + | This is used to directly specify |
- | Alternatively | + | pTopic links to the Topic in Maintenance | Agency Setup | Email Group Notifications. pBody is the body text. pHyperLink is an optional woodpecker form to load, with parameters e.g. person/xxxx where xxxx is a personid. The generated hyperlink will be appended to the body text. pDepartmentID and pDivisionID will be used to narrow down who receives the emails from the recipients specified in Maintenance | Agency Setup | Email Group Notifications. |
+ | |||
+ | Alternatively | ||
& {personid} (see above) and the alternative call used:< | & {personid} (see above) and the alternative call used:< | ||
in pTopic char(50),in pPersonID char(20) default null,in pCompanyID char(20) default null,in pVacancyID char(20) default null,in pDepartmentID char(2) default null,in pDivisionID char(20) default null )</ | in pTopic char(50),in pPersonID char(20) default null,in pCompanyID char(20) default null,in pVacancyID char(20) default null,in pDepartmentID char(2) default null,in pDivisionID char(20) default null )</ |