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.
I have created a lanuch page and a fex to populate the dropdown in the launch page.
I am trying to clarify...wbat is the rule of thumb or 'best practice' for creating launch page in composer....do you include the fex for dropdown as an embedded proc or as an external proc?
Thanks!This message has been edited. Last edited by: Kerry,
Mostly user preference. I prefer NOT to comingle my fex code with my HTML functionality and in many cases I re-use the "dropdown" fex for several different launch pages. So I always keep them as external procedures. If you don't have this need or preference, then embedding it allows you to keep all related code/processes and functionality in one single place.
Regards,
Darin
In FOCUS since 1991 WF Server: 7.7.04 on Linux and Z/OS, ReportCaster, Self-Service, MRE, Java, Flex Data: DB2/UDB, Adabas, SQL Server Output: HTML,PDF,EXL2K/07, PS, AHTML, Flex WF Client: 77 on Linux w/Tomcat
Posts: 2298 | Location: Salt Lake City, Utah | Registered: February 02, 2007
I agree with Darin... Preference... Reusable code is highly beneficial in that it can be maintained separatly and is available for use with several launch pages. But, Keeping it all together has its merits as well. If you do decide to keep them separate (my preference) it would be wise to include a comment, or two, to identify the associated procedures which use it...
In FOCUS Since 1983 ~ from FOCUS to WebFOCUS. Current: WebFOCUS Administrator at FIS Worldpay | 8204, 8206
Posts: 3132 | Location: Tennessee, Nashville area | Registered: February 23, 2005