Generally, the following JavaScript command can be embedded into a Template, in order to make the ported popup operate from that Template:

FreedombasePopUp('View All PopupName.htm',0,'System_Class','')

PopupName.htm is the name of the Popup template, eg EXAMPLES_STATES_POPUP.htm.

System_Class is the name of the System and Class (generally Application and Table without underscores) on the current Template, that the selected data should be placed into; for example, if a popup was being run to select a state, so the state could be set in the CUSTOMER STATE field in the Examples system, the System_Class would be EXAMPLES_CUSTOMER. As long as a relationship has been defined within Freedombase, linking the CUSTOMER STATE attribute to the STATE KEY attribute, Freedombase will provide appropriate JavaScript to update the selected data from the popup into the STATE field on the current page.

For example:

FreedombasePopUp('View All EXAMPLES_CUSTOMER_ID_POPUP.htm',0,'EXAMPLES_CUSTOMERS','')

Please note that System_Class must be the Freedombase System and Class names, not the OpenInsight Table name.

IMPORTANT – The Template must be rebuilt (re-integrated with Freedombase) after the relationship has been entered between the Classes in Freedombase. If it is not rebuilt after the relationship is set, then the popup will be unable to set the selected data into the page that called the popup. Beginning developers may find it easier to port the popup, then set the relationship, then port the popup again.

Similar code to the above, is used within the Freedombase Designer to manage popups. Please see the code within the Designer Templates, to see working examples of popups that have been linked into pages.