How Substitution Works

GI/Substitution is a three-phase job.

Phase one involves initialization.  As GI/Substitution starts, it loads the XML file containing the user's "permanent" settings.  This is application dependant, and may not exist in all products.  See product help for more information on how GI/Substitute is implemented.

Phase two involves parsing of any INPUT/VISTA file comments, searching for substitution text/values.  These can be 'standard' or 'pseudo-html' statements coded as comments.

Phase three involves actually performing the substitution on the input before sending to the host.

Upon termination of the application, GI/Substitution will save any items marked as "permanent" back to the user's XML file.  Again, this is only if the application supports permanent settings.