Differences

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

--- hat_25 [2020/09/04 09:37] – code block Viola Scott
+++ hat_25 [2021/04/20 14:31] (current) – Michael Scott
@@ Line 5: / Line 5: @@
   * **Signature**  Double click on the signature field to edit
-The following data fields may be inserted inside curly brackets {{}
+The following data fields may be inserted inside curly brackets {}
 |{U_name}|User Name|
@@ Line 16: / Line 16: @@
 |{B_1}|Contents of Branch Address Etc 1|
 |{B_2} etc.|Contents of Branch Address Etc 2, etc.|
-|{H_x}|x is text that will appear only in HTML signatures - use for formatting markup e.g.{{H_<B>}Bold face text{{H_</B>}|
+|{B_QuestionID}|Gets data from the Agency Questionnaire with specified Question ID|
+|{H_x}|x is text that will appear only in HTML signatures - use for formatting markup e.g.{H_<B>}Bold face text{H_</B>}|
 |{I_SID}|To include the contents of another Signature with ID 'SID'|
 | |The included ID may contain substitutable tokens: |
-| |#U=the user's login name|
+| |e.g. {I_DIVSIG_#B} will include signature DIVSIG_LONDON or DIVSIG_BRISTOL according to the user's branch name|
-| |#S=user's Department ID|
+| |#B=user's Branch name  e.g. signature called BRN_LEICESTER will be called with {I_BRN_#B} for Users of Leicester Branch|
-| |#D=user's Division name|
+| |#S=user's Department ID    e.g. signature called DEPT_IN will be called with {I_DEPT_#S} for Industrial Department|
-| |#B=user's Branch name|
+| |#D=user's Division name    e.g. signature called DIV_THE PREFERRED AG will be called with {I_DIV_#D}  (From 2.19.6 Divisions can have long names which will not fit in a 20 character SignatureID - just use as much of the name as possible and it will be matched - in this example the User's division is named The Preferred Agency Ltd.)|
+| |#U=the user's login name   e.g. signature called USER_VHS will be called with {I_USER_#U} for User VHS|
 | |#H=HTML if creating signature for HTML, otherwise = TEXT|
 | |e.g. {I_DIVSIG_#B} will include signature DIVSIG_LONDON or DIVSIG_BRISTOL according to the user's branch name|
 |{P_FN}|FN is a picture filename which is used to put an image into an HTML signature.|
 |  |Obeys same # tokens as above. The file should be in the Reports folder. If the file does not exist, it is ignored.|
-|  |If you need detailed control of the HTML then use {{F_FN} e.g. <img width=293 height=146 src="{F_#B.jpg}">.|
+|  |If you need detailed control of the HTML then use {F_FN} e.g. <img width=293 height=146 src="{F_#B.jpg}">.|
+Example of using Branch defined signatures.\\
+{{:iqx_email_sig_branch_example.jpg?500}}\\
 Plain text is also used for static text.
@@ Line 101: / Line 105: @@
 <a href="http://www.iqx.co.uk">{H_<FONT COLOR= "#FF8000">}www.iqx.co.uk{H_</FONT COLOR="#FF8000">}</a> \\
-<a href="http://www.iqx.co.uk"><img width=235 src="{F_IQXSignatureLogo.jpg}"/></a> \\
+<a href="http://www.iqx.co.uk"><img width=235 src="{F_IQXSignatureLogo.jpg}"/></a> \\ \\
+Images for Email Signatures must NOT have spaces in the name but use an _ instead.  They can be named to connect to a division, department or User. \\ \\
+Any pictures/images that are to be used MUST exist in the reports directory in order to be picked up. From 2.20.9 onwards Images can be stored in the database and accessed from Agency Setup, Email and Report Images. This is required for IQX AnyWhere clients.\\
-Any pictures/images that are to be used MUST exist in the reports directory in order to be picked up. \\
-Images must NOT have spaces in the name.  They can be named to connect to a division, department or User. \\