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.
Please help me understand the various parts of an HTML page created with the Composer tool. This is how I understand it...
Inside the BODY tag is a SELECT item which represents a listbox. This SELECT element is assigned a persistentuniqueid="compUid_1". I assume this is required to render the listbox in the browser.
Also inside the BODY tag is an INPUT item which represents a submit button. This INPUT element has an attribute - requests_list="0". I assume this causes requestid="0" to be executed when the button is pressed.
Inside the XML section is a REQUEST which represents a call to a fex. This REQUEST element is assigned a requestid="0".
Also inside the XML section is a VARIABLE which is given the same NAME as the SELECT element. This VARIABLE has an attribute - from="compUid_1". I assume this ties the VARIABLE to the SELECT element. This VARIABLE also has an attribute - requestid="0". I assume this ties the VARIABLE to a specific REQUEST.
Lastly, inside the XML section is an INPUT_CONTROL which is also given the same name as the VARIABLE and SELECT elements. This INPUT_CONTROL has an attribute - bindcontrolid="compUid_1". I assume this ties the INPUT_CONTROL to one or both of the other elements but i don't know which.
Here are my questions... Are the VARIABLE and INPUT_CONTROL redundant? Is the VARIABLE left over from an earlier version? I don't see a requestid attribute for the INPUT_CONTROL so I am guessing they are both needed.
The INPUT_CONTROL appears to have everything it needs to populate the listbox so why does the VARIABLE have attributes like file="masterfile.mas" or datafield="fieldname" or datasource="masterfile.mas"? If I edit the HTML page and change the procedure code for one of the INPUT_CONTROLs to point to a different data source the INPUT_CONTROL value changes but the VARIABLE still has file="OLDmasterfile.mas" and datasource="OLDmasterfile.mas". I'm not exactly certain which datasource is being used but it doen not appear to be affecting performance.
Thanks for your help!
DanThis message has been edited. Last edited by: Dan Pinault,
7.7.05M/7.7.03 HF6 on Windows Server 2003 SP2 output to whatever is required.
Posts: 393 | Location: St. Paul, MN | Registered: November 06, 2007