mar_mac For scenarios where QA uses other tools for performance testing you have a few options. You will use a workflow driven scan (same functionality is available in FoD - https://www.microfocus.com/documentation/fortify-on-demand/241/Fortify_on_Demand_Guide_24.1_EN.pdf#page=130). To create the workflow macro:

•  FAST (Functional Application Security Testing) proxy to generate a workflow macro captured during the execution of scripts in UFT One. This allows you to ensure nothing gets missed with testing that uses all the functional tests IAST does. Here is a YouTube video https://www.youtube.com/watch?v=4uliU_Z-qF that shows the full process through SC DAST. As you are an FoD customer, or any WebInspect users reading this, the setup of the proxy and generation of the macro will be slightly different.
• WebInspect Proxy - If you have WebInspect installed you can start the WebInspect Proxy or Traffic Monitor to record traffic
• HAR file. If your current tooling allows you to recorder a HAR file, WebInspect can consume that file
• Burp Traffic - If any customers use Burp, WebInspect can consume traffic generated from Burp. We also have a connector for Burp.

After speaking with the FoD PM, they mentioned, "customers can use any proxy software and capture traffic and upload it to FOD for scanning." You might want to discuss with your FoD representative the options available in your specific use case.

For customers that have WebInspect standalone, you can open the UFT .usr file natively in a WebInspect Guided Scan - https://www.microfocus.com/documentation/fortify-webinspect/2420/WI_Guide_24.2.0.pdf#page=150 / www.microfocus.com/.../uft-one