Multiple Licenses, multiple flavors of help
Hickling, Lisa (TOR)
lhickling at Express-Scripts.com
Wed Jul 5 13:42:03 MDT 2006
You could take any of the following approaches:
High Maintenance Approach:
Create separate help projects for each license (be sure to single-source
topics and apply conditional tags where possible). Ask developers to
code each help launch function so that it tests for the user's license.
Display help topic from the project associated with the license
detected.
Low Maintenance Approach:
Clearly state the intended audience of each topic using some sort of
topic header. Allow users to sieve through to the information that is
most applicable to them.
HTH,
Lisa
******* Confidentiality Notice *******
ESI Canada -- Optimizing the value of drug and dental benefits
This email, its electronic document attachments, and the contents of its website linkages may contain confidential health information. This information is intended solely for use by the individual or entity to whom it is addressed. If you have received this information in error, please notify the sender immediately and arrange for the prompt destruction of the material and any accompanying attachments.
******* Avis de confidentialite *******
ESI Canada -- Optimiser la valeur des regimes d'assurance medicaments et dentaires
Ce courriel ainsi que tout document y etant joint de meme que le contenu des liens vers des sites Web peuvent reunir des renseignements confidentiels sur la sante. Cette information s'adresse uniquement a l'usager ou a l'organisation auxquels elle est destinee. Si vous avez recu ce message par erreur, veuillez en aviser l'expediteur immediatement et proceder a la suppression du document et des fichiers joints sans tarder.
More information about the TECHWR-L
mailing list