SmartGuide Customizer for XML and SmartGuide Launcher for XML samples

These are some samples to illustrate how to use the SmartGuide Customizer for XML (Customizer is used to represent this term in the content of this document from now on) and SmartGuide Launcher for XML (Launcher is used to represent this term in the content of this document from now on) tools. The original template XML files used in the samples are exported from the Object Builder, but in reality they can be any XML files. The final target XML files generated by the Launcher for the samples can be imported back to Object Builder, but in reality they may not be able to be imported back to Object Builder. The detailed documentation of how to use the tools can be found in the help funtions within the tools. This document only serves as a read-me for the samples.

To invoke the Customizer tool, type xmlcustm from command line.

To invoke the Launcher tool, type xmllaunch from command line.

The first sample has one business object. If you import simple.xml into Object Builder as user defined business objects, you get a model with one file, one business object (BO) in that file, key and copy helper for the BO, BO implementation, data object (DO), DO implementation and managed object (MO). If you open simple-macro.xml in the Customizer, select the element in the tree view, the definition of the SmartGuide page for that element is displayed on the right pane.The SmartGuide page definition for all the elements are saved in a XML wizard script file (simple-macro.xml for this sample). To run the XML wizard script, you use the Launcher tool or press the "test" button in the Customizer tool. In the XML wizard, you follow the prompts to add elements and edit element values, finally save the target XML file. The target XML file (simple-new.xml for this sample) is the new XML document generated by the Launcher tool. Import it back into Object Builder, you get a diferent model with similar structures. You can rename the business object file and interface, rename the attribute, change the type, add new attributes. The names for the new key, copy helper, BO implementation, DO and MO etc. are derived from the new BO file and interface name.

The second sample is a foreign key sample. There are two BOs. The first BO has an one to many relationship with the second BO. You are prompted for the BO file name and interface name, attribtues for the first BO, then the object relationship name and the type of the second BO or the many side BO, then the information about the second BO including the foreign key attribute name and type. foreignkey.xml is the original template, foreignkey-macro.xml is the XML wizard script and foreignkey-new.xml is the target XML document.

The third sample is a specialized home sample. There are two BOs. The second BO is the specialized home BO for the first BO. You are only prompted for the information about the first BO. The information about the second BO is derived from that of the first BO.spechome.xml is the original template, spechome-macro.xml is the XML wizard script and spechome-new.xml is the target XML document.