Altering content is critical for the HAT process that we discussed in the Chapter 1, Customization Building Blocks, and for a lot of applications, it is equally important to maintain basic functionality alone. For example, when UAG publishes Citrix, altering some of the page content is necessary because Citrix was never designed to be published in this scenario. Without the specific alterations, the user would not even be able to launch the Citrix web page, and instead, the browser would go into an error loop.
In other circumstances, the content alteration makes the user experience more savory. For example, when OWA is published through UAG, the Sign out button that OWA usually displays is removed by UAG, with the intention that the user would instead be forced to use the portal frame's Log Off button, located on the UAG toolbar as shown in the following screenshot:
UAG has two mechanisms for manipulating content. One is called The Application Wrapper...