Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
sa_maintenance [2022/04/15 14:03] – Shelley Hunter | sa_maintenance [2023/04/19 08:56] (current) – Shelley Hunter | ||
---|---|---|---|
Line 22: | Line 22: | ||
* Booking Shifts | * Booking Shifts | ||
* Confirming Shifts | * Confirming Shifts | ||
- | * Timesheets view on Temp Desk | + | * Timesheets view on Temp Desk (to either vacancy or site contact) |
+ | * Favourites | ||
\\ | \\ | ||
Line 65: | Line 66: | ||
**Recipient Type** – Candidate, Client or Agency (Person Selector and Record can only use Candidate type as no links to others) | **Recipient Type** – Candidate, Client or Agency (Person Selector and Record can only use Candidate type as no links to others) | ||
- | **Template** – The body of text for the notification. This will be HTML for emails and plain text for SMS. | + | **Template** – The body of text for the notification. This will be HTML for emails and plain text for SMS. It is possible to include in the template a bcc that the notification will always be sent to, note this cannot be added at the point of sending only on the template. |
**Sort order** - The first template (lowest sort order) of any given type will be used as the default. If more than one template shares the lowest sort order, all with that sort order will be displayed in separate forms. This allows for both SMS and Email notifications to be sent at the same time. | **Sort order** - The first template (lowest sort order) of any given type will be used as the default. If more than one template shares the lowest sort order, all with that sort order will be displayed in separate forms. This allows for both SMS and Email notifications to be sent at the same time. | ||
Line 73: | Line 74: | ||
**Division** – Can be used to limit the templates to a particular division. | **Division** – Can be used to limit the templates to a particular division. | ||
- | **Defunct** – If ticked the template will not appear for selection. Useful for old or partly written templates. | + | **Defunct** – If ticked the template will not appear for selection. Useful for old or partly written templates. 2.21.11+ defunct templates will be hidden by default and can be seen by pressing the Show Defunct button, defunct templates will show in red to highlight them as different. |
=== How to set up === | === How to set up === | ||
Line 99: | Line 100: | ||
It allows specification of a comma-separated list of attachments, | It allows specification of a comma-separated list of attachments, | ||
- | **For report directories and attachments, | + | **For report directories and attachments, |
+ | 2.22.2+ there is a simplified method of adding attachments. | ||
==== Example of a set up notification ==== | ==== Example of a set up notification ==== | ||
Line 107: | Line 109: | ||
{{: | {{: | ||
- | {{: | + | {{: |
+ | |||
+ | === Notifications and Jobs === | ||
+ | 2.21.8+ added the ability to invoke the powerful notification engine from jobs, so that, among other things, it can be launched from a candidate or company selector for the selected people and with notification text generated in the job. For assistance with setting this up please contact IQX Support. \\ \\ | ||
+ | |||
+ | === Progress Notifications Changing State === | ||
+ | Notifications can be set up to change the Person Progress States when sent - this function is available on Desk Top ‘Progress due for Action’ and Vacancy ‘Progress/ | ||
+ | |||
+ | Admin set up required- Maintenance > Database functions > Notifications > Notification Complete > change the ‘ptemplateid’ to the notification ID and set the current Person State and the required Person State after sending (see example below, highlighted in Green) | ||
+ | |||
+ | if " | ||
+ | update " | ||
+ | end if \\ \\ | ||
+ | === Reports === | ||
+ | A notification template can run a specified report at the point of creation, the fields will be populated according to the record it is being run from and the completed report will be emailed as an attachment to the notification. | ||
+ | |||
+ | Reports that are produced and sent with a notification can now be saved into the database. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | Users will then see the document has Auto save prefixed to it when they are sending the notification | ||
+ | |||
+ | {{: | ||
+ | |||
+ | And the item will be saved to the documents view of the record | ||
+ | |||
+ | {{: | ||
+ | |||
+ | === Deep Links === | ||
+ | |||
+ | Agencies can include deep links in notification emails that candidates can click on and details will be sent back to the database. | ||
+ | For more information on how to set this up click [[Notifications_DeepLink|here]]. |