notify_01

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
notify_01 [2023/04/17 10:17] Shelley Hunternotify_01 [2024/03/26 09:18] (current) Shelley Hunter
Line 9: Line 9:
   * **ID** - visible unique id   * **ID** - visible unique id
   * **Description**   * **Description**
-  * **Transmission Type** - **Email** or **SMS**+  * **Transmission Type** - **Email****SMS** or **Push**
   * **Notification Type**   * **Notification Type**
 +    * **App_Favourites** - used on the Favourites form to send to applicants
 +    * **App_ProgressContact** - used on the progress view of the Person record
 +    * **App_SearchContact** - used when searching for vacancies from the candidate record
 +    * **Availability** - used for the Availability view of the Temp Desk
     * **ClientContact** - used on Client form (notify button, top panel)     * **ClientContact** - used on Client form (notify button, top panel)
 +    * **Com_Favourites** - used on the Favourites form to send to client contacts
 +    * **Compliance** - used on the Temp Desk Compliance view
     * **DiaryReminder** - used  on Diary->Reminder form     * **DiaryReminder** - used  on Diary->Reminder form
 +    * **Expiry Dates** - used in the Expiry Dates view of the Temp Desk
     * **FillShiftPack** - used on Shift Matching Forms to Send Docs     * **FillShiftPack** - used on Shift Matching Forms to Send Docs
 +    * **Job** - used when a job calls a notification template
     * **NotifyCancel**  - used on Shift Confirmation form re cancelling shifts     * **NotifyCancel**  - used on Shift Confirmation form re cancelling shifts
     * **NotifyConfirm** - used on Shift Confirmation form     * **NotifyConfirm** - used on Shift Confirmation form
Line 21: Line 29:
     * **PersonShiftPack** used on Person/Vacancy Shift Views to Send Docs     * **PersonShiftPack** used on Person/Vacancy Shift Views to Send Docs
     * **PlacementConfirm** - used on Placement form (notify button, top panel)     * **PlacementConfirm** - used on Placement form (notify button, top panel)
 +    * **PlacementContact** - used on the Placement selector
 +    * **Placements** - used on Temp Desk Placement view
 +    * **PLC_Link** - used on the Placement Link view of a placement record (2.23.30+)
     * **ProgressCode<StatusCode>** - used on Vacancy Shortlist view and Progress Forms(notify button) use individual codes eg ProgressCodeA     * **ProgressCode<StatusCode>** - used on Vacancy Shortlist view and Progress Forms(notify button) use individual codes eg ProgressCodeA
     * **QueryBook** - used by the query mechanism on the Shift Match/Book forms     * **QueryBook** - used by the query mechanism on the Shift Match/Book forms
 +    * **QueryCancel** - used by the query mechanism on Shift Conformation form
     * **QueryConfirm**  - used by query mechanism on Shift Confirmation form     * **QueryConfirm**  - used by query mechanism on Shift Confirmation form
 +    * **SHF_FillConfirm** - used to confirm after booking a shift on the shift fill wizard
 +    * **Temps** - used on Temp Desk Temps view
     * **TimesheetContact**- used by notification mechanism on Tempdesk (timesheet) form     * **TimesheetContact**- used by notification mechanism on Tempdesk (timesheet) form
 +    * **Vacancies** -used on Vacancies view of a Shift Desk
 +    * **Vac_Contact** - used on the Vacancy selector 
 +    * **VacancyShifts** - used on the Vacancy Shifts view of the Temp Desk
     * **VacShortListPack**- used on Vacancy/Shortlist to Send Docs     * **VacShortListPack**- used on Vacancy/Shortlist to Send Docs
 +    * **Vac_SearchContact** - used on vacancy search final page (2.23.30+)
   * **Recipient Type** - **Candidate**, **Client**, **Agency** or **Owner**   * **Recipient Type** - **Candidate**, **Client**, **Agency** or **Owner**
   * **Template** - the text of the template. This will be HTML for emails and plain text for SMS. For the substitutable fields see below. Note that for Emails the resulting text will be inserted into an HTML wrapper - see below for details.   * **Template** - the text of the template. This will be HTML for emails and plain text for SMS. For the substitutable fields see below. Note that for Emails the resulting text will be inserted into an HTML wrapper - see below for details.
Line 215: Line 233:
 </table> </table>
 </sxh> </sxh>
 +\\ \\ 2.23.1+ Save&Open button has been added allowing you to extract your template.  If you save as an HTML file it will also open in a browser where you can right click to inspect source and edit.  If you then save the file you can load back into the notification template using the Load button.
 ===== HTML wrapper mechanism ===== ===== HTML wrapper mechanism =====
 When generating an email notification, the expanded template will be inserted into an HTML_WRAP email signature construct, replacing the {bodytext} token. By default the wrapper with ID 'HTML_WRAP' will be used, but you can over-ride this in the 'HTML Wrap ID' Notification function. Into the wrapper will also be inserted a generated email signature, replacing {signature}. The 'DEFAULT' signature will be used unless the 'Signature ID' Notification function is used to over-ride. Any {origmessage} token in the wrapper will be blanked. When generating an email notification, the expanded template will be inserted into an HTML_WRAP email signature construct, replacing the {bodytext} token. By default the wrapper with ID 'HTML_WRAP' will be used, but you can over-ride this in the 'HTML Wrap ID' Notification function. Into the wrapper will also be inserted a generated email signature, replacing {signature}. The 'DEFAULT' signature will be used unless the 'Signature ID' Notification function is used to over-ride. Any {origmessage} token in the wrapper will be blanked.
Line 235: Line 253:
 ===== Adding a Thumbnail Photo ===== ===== Adding a Thumbnail Photo =====
 It is possible to include the thumbnail from a candidate record in a notification, this is useful if you are using notifications to send assignment confirmations.  General Setting number 3040 ‘Display Thumbnail Photo on Person’ needs to be set to Y then in your notification template insert the code {APP_THUMBNAIL} where you want the photo to appear. \\ \\ It is possible to include the thumbnail from a candidate record in a notification, this is useful if you are using notifications to send assignment confirmations.  General Setting number 3040 ‘Display Thumbnail Photo on Person’ needs to be set to Y then in your notification template insert the code {APP_THUMBNAIL} where you want the photo to appear. \\ \\
 +
 +===== Adding an Image =====
 +Images can be included in the notification template by including something like <img width=300 class="center" src="file:///C:\IQX\Reports\logo.jpg"/> where you can set the file location and the name of the image.  If you are an IQXAnywhere client then you need to include something like <img width= "739" height= "623" style= "width:7.7in;height:6.4916in" src="https://pizza.iqxanywhere.net/assets/logo.jpg"> instead of the file path you use the web location.  You will also need to upload the file to Email, Web Report Images and rebuild Web once it has been uploaded.
 +
 +From 2.23.1+ it is also possible to send an ad hoc image to all recipients in your selection, this can be useful for sending marketing information that has been created as an image rather than a word document.  If set up by your system administrator a new button will appear in the notification allowing you to browse your computer for an image to include in all notifications. \\ \\
 +In the relevant template add the following :- <img src="{GETIMAGE}" alt="test" width="500" height="600"> to switch on the new image button in the notification. \\ \\ 
  
 ===== Custom Merge Fields ===== ===== Custom Merge Fields =====
 Some custom merge fields should ONLY be used in notifications (for example some HTML coding), there is now a Notifications Only tick box in Maintenance – Database Set Up – Custom Word Merge Fields.  If ticked the fields will not be available for adding to a document template, they will be accessible under the [Special] header in Notifications. \\ \\ Some custom merge fields should ONLY be used in notifications (for example some HTML coding), there is now a Notifications Only tick box in Maintenance – Database Set Up – Custom Word Merge Fields.  If ticked the fields will not be available for adding to a document template, they will be accessible under the [Special] header in Notifications. \\ \\
 +If using a custom merge fields that requires the information to be over multiple lines e.g. address in a block then the merge field will need to be amended to replace the carriage returns with HTML breaks.  This needs to be in the custom merge field and the _literal_ needs to be the first part:
 + string('_literal_',
 +replace( Item to be Replaced)  endif, string(char(13), char(10)), '<br/>'))
  
 ===== Adding a URL ===== ===== Adding a URL =====
  • notify_01.1681726628.txt.gz
  • Last modified: 2023/04/17 10:17
  • by Shelley Hunter