Home| Printable Version

Due to the native XML architecture of Hyfinity's technology, the binding information for each page simply consists of a number of XPaths used within the generated XSL. The following screen shot shows an example of how the binding page may appear upon first entry. The left section of the page contains a representation of the structure of the current page. The right hand section contains a representation of the binding files chosen for this page or associated actions as required. Each page contains a content-specific set of helpful guidelines, and can be shown or hidden as needed. Clicking on the XPath Guidelines will display the relevant help notes; clicking it again will hide them. Depending on how the page has been configured, XPath bindings may be required for the Groups, Repeats or Fields within it. Therefore, the remainder of this page is specific to the currently selected page component and actions. The name of this component is provided, and is highlighted in the page structure representation. No matter what element is selected, the required XPaths can be typed directly into the appropriate text area. Alternatively we can make use of the instance data files to create our XPaths. Once the required part of the XML instance has been found, if we click and drag it to the appropriate XPath text area, the XPath will be automatically created for us. Regardless of how the XPath has been created, FormMaker will try to 'match' it against the instance document. Any matching elements will be highlighted on the document treeview. You can click on the text showing the number of matches to automatically display the document with the matches highlighted. The red bars on the treeview on the left hand side highlight the page components for which binding information is currently invalid, or still needs to be provided. Once all the required XPaths have been entered for a component, the red bar will disappear from the appropriate entry in the treeview. You will notice that most of the XPaths have already been populated. When you add components to the page on the Page Structure screen, the appropriate bindings will be generated based on whether or not the field came from a data source. You can however adjust these default bindings if required. The main bindings that will not have been pre populated are those for additional features that have been enabled, such as conditional styling or dynamic hiding. In these cases, a message saying 'enter_xpath_here' will be displayed, alerting users to fill in XPath values appropriately. The following pages provide a description of what each required XPath is used for.