after recording login transaction, it will be used in many scripts. So I thought we could store the login transaction to external JS as a function and other scripts could load it.
but the cons are that if we need to update the transaction, we cannot open it to Vugen to check the header/response/etc.
We could add the file to the script via Extra Files but that means it will be added to the script folder not in the original path and for any changes we make, we have to update it manually to the file in the original path.
Could there be another way to maximize the transaction reusability?
Support
Documentation
Learning Services
Partner Programs
