The SRA engine is very similar to AppWrap, but it does offer a few additional strengths. The primary difference is that SRA is the engine that performs the HAT signing of URLs for every piece of content UAG goes through. It can do regular search and replace just like AppWrap, but its real power is in our ability to teach UAG to recognize and sign HTML code that it wasn't initially designed to.
The need for this sort of situation would arise if some application generates HTML code that UAG cannot recognize, leading to HAT signing failure. There are additional mechanisms that help UAG deal with that, but if all fails, you may need to address this manually. Dealing with missed links can be done by locating the missed links, and adding a custom AppWrap or SRA file that will perform the necessary search and sign of these rogue links A better way would be to configure UAG to correctly recognize the code for the link so that it can sign it automatically, rather than by us having to fix...