(I did a poor job asking my question so I'm editing my post)
In 3.1, we used file VVVSQ100 to store global variables. I used this file to softcode the IFS locations of the html/js files for different environments (dev, qat, prod). It seems the new file for this is VVSETTINGS. When I input my settings into VVSETTINGS, and try to add a new app to the portal, it seems that Valence now puts /portal/[fpapps_path] at the front of my custom URL. How do I get around this as our current IFS structure is not under that folder?
Here is what it looked like:
/portal/[fpapps_path]/myapp.html
What is the proper way to softcode custom application paths in Valence 4.1 (how do you set up VVSETTINGS and how do you reference the custom application path)?
In 3.1, we used file VVVSQ100 to store global variables. I used this file to softcode the IFS locations of the html/js files for different environments (dev, qat, prod). It seems the new file for this is VVSETTINGS. When I input my settings into VVSETTINGS, and try to add a new app to the portal, it seems that Valence now puts /portal/[fpapps_path] at the front of my custom URL. How do I get around this as our current IFS structure is not under that folder?
Here is what it looked like:
/portal/[fpapps_path]/myapp.html
What is the proper way to softcode custom application paths in Valence 4.1 (how do you set up VVSETTINGS and how do you reference the custom application path)?
Comment