Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| hat_12 [2016/05/31 11:46] – ivan | hat_12 [2019/07/23 15:59] (current) – [Boilerplate menu list size] Shelley Hunter | ||
|---|---|---|---|
| Line 4: | Line 4: | ||
| Boiler Plate Text, (BPT), allows the setting up of blocks of standard text which may be easily dropped into the current cursor position of the various free text notes fields. | Boiler Plate Text, (BPT), allows the setting up of blocks of standard text which may be easily dropped into the current cursor position of the various free text notes fields. | ||
| - | The below fields are available | ||
| - | |||
| - | This allows the setting up of blocks of standard text which may be easily dropped into the current cursor position of the various free text notes fields. | ||
| Useful for such things as meeting note headings, job description outlines or standard blocks of text for sending emails. | Useful for such things as meeting note headings, job description outlines or standard blocks of text for sending emails. | ||
| Line 21: | Line 18: | ||
| * Text Message | * Text Message | ||
| - | The Type given to the Boiler Plate Text will determine where in IQX it can be used. For example, Progress type is available from the Insert Text on a Progress Record | + | The Type given to the Boiler Plate Text will determine where in IQX it can be used. For example, Progress type is available from the Insert Text on a progress record |
| Text Message Type is used for sending SMS/Email from Shift Booking or Shift Confirmation. | Text Message Type is used for sending SMS/Email from Shift Booking or Shift Confirmation. | ||
| Line 141: | Line 138: | ||
| Accessible from Shift Confirmation buttons and can also be passed through to contact events via the shift confirmation and tempdesk – shifts screen. | Accessible from Shift Confirmation buttons and can also be passed through to contact events via the shift confirmation and tempdesk – shifts screen. | ||
| - | Can use either Shift Details or {SHF} fields but not both, if SHIFTDETAILS is used then none of the {SHF} fields will be available. | + | Can use **either** Shift Details |
| Boiler Plate Field Example | Boiler Plate Field Example | ||
| Line 164: | Line 161: | ||
| SHF_STATEDESC Provisional | SHF_STATEDESC Provisional | ||
| SHF_SERIALNUMBER 12345 | SHF_SERIALNUMBER 12345 | ||
| - | + | ||
| + | It is possible to list all shifts applicable (up to 365 days in advance) to an applicant. The shifts do not have to be referenced in the Shift Confirmation Screen. | ||
| + | |||
| + | {SHR_BEGIN}{SHR_DATE dd/mm/yyyy} {SHR_FROM} – {SHR_TO}{SHR_END} | ||
| + | |||
| + | Would output something like: | ||
| + | |||
| + | 01/07/2016 08:00 – 17-00 | ||
| + | 02/07/2016 08:00 – 17-00 | ||
| + | 03/07/2016 08:00 – 17-00 | ||
| + | 04/07/2016 08:00 – 17-00 | ||
| + | |||
| + | SHR_BEGIN, can be replaced with {SHR_BEGIN_n}, | ||
| + | |||
| + | **Note** It is the current date that the Shift Range starts from and not the date of the shift you a confirming. This means that if you a confirming a shift in the future the SHR command might not list all of the shifts from the date you are confirming on. | ||
| + | |||
| + | **These fields cannot be used with {SHIFTDETAILS}.** | ||
| ==== Shift Matching Fields ==== | ==== Shift Matching Fields ==== | ||
| Line 173: | Line 187: | ||
| SHF_TO 10: | SHF_TO 10: | ||
| SHF_THEIRREF A/ | SHF_THEIRREF A/ | ||
| + | |||
| + | If you wish to contact a candidate about their availability for more than one shift you can use {SHF_BEGIN} and {SHF_END} to list the shifts. | ||
| + | |||
| + | {SHF_BEGIN}{SHF_DATE dd/mm/yyyy} {SHF_FROM} {SHF_TO}{SHF_END} {COM_COMPANYNAME} | ||
| + | |||
| + | Would output something like: | ||
| + | |||
| + | 01/07/2016 08:00 – 17-00 | ||
| + | 02/07/2016 08:00 – 17-00 | ||
| + | 03/07/2016 08:00 – 17-00 | ||
| + | IQX Limited | ||
| + | |||
| + | **These fields cannot be used with {SHIFTDETAILS}.** | ||
| ==== Colleague Fields ==== | ==== Colleague Fields ==== | ||
| Line 279: | Line 306: | ||
| The resulting name must be unique, i.e. if it is already a predefined boiler plate name, it will not be accessible. E.g. APP_NAME.\\ | The resulting name must be unique, i.e. if it is already a predefined boiler plate name, it will not be accessible. E.g. APP_NAME.\\ | ||
| + | |||
| + | ==== Questions ==== | ||
| + | |||
| + | Allows access to both the question answer and the description | ||
| + | |||
| + | QTN_< | ||
| + | |||
| + | eg | ||
| + | QTN_A_P_CUR | ||
| + | QTN_D_P_CUR | ||
| + | |||
| + | Sub menu selection not currently supported. | ||
| + | Multiple / Graded and Scored Selection are output in a comma separated list. | ||
| + | |||
| + | A question answer will only be evaluated if the question is applicable to the rest of the substitutions. | ||
| + | |||
| + | |||
| + | ==== Letter / Consultant Fields ==== | ||
| + | |||
| + | All fields staff with ‘LET_’ | ||
| + | |||
| + | Boiler Plate Field Example | ||
| + | LET_TODAY 1st January 2015 | ||
| + | LET_TODAY_dd/ | ||
| + | LET_ADDRESSLONG Wester Newhouse, Lilliesleaf, | ||
| + | LET_ADDRESS Wester Newhouse | ||
| + | Lilliesleaf | ||
| + | Melrose | ||
| + | TD6 9JT | ||
| + | LET_CONSULTANT Fred Smith | ||
| + | LET_CONSULTANTTITLE Administrator | ||
| + | LET_CONSULTANTEMAIL [email protected] | ||
| + | |||
| + | |||
| + | ==== Boilerplate menu list size==== | ||
| + | |||
| + | If you have large numbers of Boilerplate Text these will appear in one large list and some may disappear off the screen. | ||
| + | |||
| + | Switch off: {{: | ||
| + | |||
| + | This requires system administrator set up in General Settings group of Settings number 1850, the value entered will be the number of templates in each column. | ||
| + | |||
| + | \\ \\ \\ | ||
| Go back to [[hints_and_tips|Hints, | Go back to [[hints_and_tips|Hints, | ||
| Go back to [[ug1-22|References]] | Go back to [[ug1-22|References]] | ||