Database Design Report XML Output Grammar

40 FileMaker Pro Advanced Database Design Report XML Output Grammar
Not es:
1. Many script steps below have options/attributes which are only applicable if certain other options/attributes are
enabled or set to a certain value. Examples of this are:
1 find requests for the 'Perform Find' script step (only applicable if 'Specify find requests' checkbox is checked)
1 file, calculation, or text for the 'Send Event' script step (only applicable if radio button is set to file, calculation
or text respectively)
For the sake of discussion, let us call the former 'conditional' options/attributes and the latter
'enabling/determining' options/attributes. Though only applicable when the corresponding 'enabling/determining'
option/attribute is appropriately set, once specified, 'conditional' options/attributes may very well be retained
even after the 'enabling/determining' option/attribute is changed in such a way that the 'conditional'
option/attributes are no longer applicable. This is done for the sake of convenience so that if/when the user ever
changes their mind and switches the 'enabling/determining' option/attribute back, so that the 'conditional'
options/attributes are once again applicable, the last entered/chosen values for these 'conditional'
options/attributes will still be present.
For example, in the case of a 'Perform Find' script step, previously specified find requests will be retained, even
though the user may uncheck the 'Specify find requests' checkbox, so that, in case they decide to re-enable it, the
last entered find will still be present, for the sake of convenience. Similarly, in the case of the 'Send Event' script
step, a previously specified calculation will be retained, even though the user may switch to specifying a file, so
that, in case they decide to switch back to a calculation, the last entered calculation will still be present, again for
the sake of convenience.
As the last entered/chosen values of such currently inapplicable 'conditional' options/attributes are actually stored
in the script step itself, corresponding XML for them is therefore generated when a DDR is performed. The fact
that such options/attributes are reported should not therefore be construed as somehow implying they are
applicable. Their applicability can/should be determined by checking the XML setting reported by the DDR for
the corresponding 'enabling/determining' option/attribute.
2. All script steps below contain the element <StepText> and many contain instances of the element
<DisplayCalculation>. Both of these elements contain redundant information that only serves to make DDR reports
(in particular, HTML ones) more readable.