Hello all
I'd like to know if it's possible to change 'on fly' the path for External Request WEbFocus Procedures (FEX files) under the Request & Data Sources for a HTML file in App Studio.
I will try to explain myself:
I have 2 equals portals (PRODUCTION and TEST) with the same files (HTML, FEX and SYNONYMS files) but they are pointing to two different environments (Production & Test) and inside those environments we have different databases for different Regions and users who belong to those Regions. So, we have different App folders in both enviroments for each Region.
I am using FEX files for filling in the pick-list in the HTML depending the user. This is, when the FEX file stat to run, at the very begginig, depending the user's belonging, the FEX file will choose one path or another for the SYNONYMS.
But, what happen when I improve, develop or update one or more HTML files in the test portal and need to copy-paste those files from test to production portal.... in this case I MUST edit those HTML and change all the FEX files in External Request WEbFocus Procedure to select the correct CONTENT PATH where the FEX files are. It is possible to see the path when you put the mouse over the FEX file. A pop up shows you the entire path of the FEX file in the 'Request & Data Sources' utility window.
My question is how to avoid this step or how to define and use a variable to fix that 'on fly'.
Sorry if I couldn' explain myself and thank you.

This message has been edited. Last edited by: FP Mod Chuck,

Hi osantamaria,

This subject have already been discussed a few weeks/months ago.

WF8 doesn't give you that ability "on the fly" as for Content HTML/Fex.

What you normally should have is two different servers (prod and dev) where each are configured (have path/folders) the same. So when you pass from one environment to another you don't need to change the path.

Hi MartinY
I used your proposal, but now I don't have this DEV server.
Anyway, thank you very much for your quick answer

The goal is to have different servers no matter if it's prod/dev/test.

You need to have same content and folders structure on each servers.

You can't have a folder called TST in you test server then promote your code from TST folder to PRD folder in your prod server; it won't work without re-selecting the proper path/folders.