How to correctly insert dynamic fields into signatures
This article is obsolete and may relate only to older versions of our software.
Problem:
You use one of the older versions of the CodeTwo software. You noticed that dynamic fields typed in or copied and pasted into a signature are not populated with Active Directory data when the signature is added to a message. For example, the recipient sees the {First name} and {Last name} placeholders instead of the sender’s first and last name pulled from AD.
Solution:
Tip
You may want to consider upgrading your CodeTwo software to the latest version. We solved this problem in:
The latest versions include numerous improvements that will make your work with the software easier and quicker.
For dynamic fields to work properly, they need to be inserted from the program’s ribbon:
- In the signature editor, click on the dynamic field icon on the top menu bar and choose an AD attribute (Fig. 1.). This will automatically insert a placeholder into a signature.
Fig. 1. Choosing a dynamic field from the menu list.
- To make sure that the dynamic field was inserted correctly, double-click on a placeholder and check the Properties pane on the left:
- if a placeholder was entered correctly, it will be identified as an Active Directory field (Fig. 2.).
Fig. 2. Checking if the dynamic field was inserted properly.
- if a placeholder's name was typed in or pasted, the Properties records will show no reference to Active Directory.
Fig. 3. The properties pane showing that the dynamic field was inserted incorrectly.
The difference between the right and wrong use of dynamic fields will be visible when the email passes through the Exchange Server (Fig. 4.).
Fig. 4. Dynamic field recognized correctly (left) and incorrectly (right).
Related products: | CodeTwo Exchange Rules 2007 2.x, 3.x, CodeTwo Exchange Rules 2010 1.x, 2.x, CodeTwo Exchange Rules 2013 1.x, CodeTwo Exchange Rules 3.x, CodeTwo Exchange Rules Pro 1.x |
Categories: | How-To |
Last modified: | September 15, 2023 |
Created: | August 6, 2012 |
ID: | 254 |