Friday, July 21, 2006 11:18 AM
Fig. 1 - BEFORE Original Textbox with value "Smith, John".
Fig. 2 - AFTER Textbox now invisible, dropdown loaded with validation list, "Smith, John" selected.
I'll continue now for those interested in the technical details. Technical Details It is easy to get the XML validation list for a field from WebPublisher. For example, here is the validation list for the Product field from the Inmagic Support Knowledgebase: view xml. The query string parameters will tell you what you need for your own database: AC=validation_lists FN=[FieldName] TN=[TextbaseName] You use AJAX to fetch the XML, then write some script to walk the DOM and create an option object for each entry, which you then add to the select object in question. I use JSMX from www.lalabird.com to do the AJAX bit. That's the easy part. The hard part is suppressing the dynamically-generated textbox, which is given an ID/name on the fly by WebPublisher, depending upon where it appears in the form. In order to suppress the thing, the script must identify it. Fortunately edit inputs are generated in numerical order, so the textbox will be named EIx, where x is an integer and corresponds to the textbox's location among the other inputs. Rather than assume "it's the 3rd one down so it must be EI3", the script is able to locate it within a specially marked container tag and render it non-visible.
Fig. 3 - FORM DESIGN VIEW
[Author] is where WPP will insert HTML on the edit page. [Author] is wrapped by the div tag whose "DropdownOverride" class is a marker.
Fig. 4 - WPP EDIT VIEW [Author] has been replaced by WPP generated HTML. The script is able to find an input or textarea whose name is EIx within the container div tag marked "DropdownOverride".
The input EIx remains the "active" element, whose value WPP works with on submit. The dropdown itself will be ignored. Any selection change in the dropdown calls UpdateSelection() to update the EIx value even though EIx does not display, since the script set it to style="display:none;".
Monday, July 17, 2006 4:46 PM
Hot off the forge: a multi-textbase search alternative. Designed for maximum ease-of-use, so no field mapping or special form design. You can add a WebPublisher database to the search as quickly as you can create a canned query. No field mapping also means that the textbases being searched do not need to correlate in any way. One textbase could search Title, Author, and Subject while another searched Address, City, and State, for example. Also, due to the fact that you do not need access to the textbase itself or its WebPublisher support files, you can search *any* available WebPublisher database. Hmm. Better ask nicely first! Results come back with a hit count and a link to the individual results for each database. The result display is completely configurable, and returns five values for each database result: textbase description, result count, search text, canned query text, error text (if any). The demo simultaneously searches the Andornot WebPublisher Links database and the Inmagic Support Knowledgebase: http://andornot.com/products/addons/multisearch.aspx.