Database Design Report XML Output Grammar

50 FileMaker Pro Advanced Database Design Report XML Output Grammar
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.