As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
Piter, As far as I know, when you -INCLUDE as fex all labels are at first treated as local, meaning that WF will search the -INCLUDEd fex for labels. If a label is not found, then it will look in the calling fex. See the following example. The calling fex:
-SET &ECHO=ALL;
-* File piter01.fex
TABLE FILE CAR
PRINT COUNTRY
ON TABLE HOLD AS PITER FORMAT ALPHA
END
-RUN
-SET &R=&LINES;
-REPEAT #GETCOUNTRY FOR &I FROM 1 TO &R;
-READFILE PITER
-INCLUDE PITER00
-#GETCOUNTRY
-TYPE DONE
thanks, Daniel. Your case is clear. I was asking about dynamic labels and seems it is also clear - like Francis wrote - WF do not do "precompile" and will not understand 'future' dynamic labels