If Samantha had previously selected a plain text or an HTML/image file, wewill import it for her into a new rich text field. There will now only beone field for a signature, which will be rich, and it will roam. Sinceit's a 'low cost' solution, Samantha will only have a 'lite' rich text field,but that will allow her to add attachments, such as a vCard, and also herpicture or company logo.
- If you used the Plain Text and HTML/image file as a way to manage 'two different' signatures, you will no longer have this option. You'll have to change the one signature in preferences or manually enter the 2nd signature (through More > Insert Signature... command). How big an issue is this?
- If you go to an 8.5 client (and 8.5 template) and then switch back to a previous client, while keeping the 8.5 template, you will no longer have automatic signature support. Unfortunately, the Preferences page will make it seem like there is automatic signature support, so this is a concern. Does anyone have this scenario? If so, why and how often?
- If you have different signatures on different machines, we will only retain the signature from the first machine you use with 8.5. How often do people have different signatures on different machines?
- You will be able to insert images, attachments, and doclinks. The actual rich 'text' support available in this dialog is very limited (i.e. only red or blue text, only one font, etc.), so Samantha will probably want to create her 'rich text' somewhere else and paste it in. We know this isn't ideal. How big a deal is this?
- Any other issues you're concerned about?
Again, we're trying toascertain whether this ‘low cost’ solution to roaming signatures is stillbetter than what we have today, given the issues I’ve listed above. Please give us any feedback on the questionsabove, and at the end a simple Yes or No would be great too!
Margo and the Notes Template & Core teams