The object editing and creation forms configured using objectUIs can have three different associated XSL transformations: init, validate and compute.

These transformations act on XML generated by the data navigator.

You can configure the XML using three optional attributes of the init, validate and compute objectUI element:

•dataMaxSize: maximum size in bytes of the binary data to be inserted directly in the XML. Larger data is rendered as URLs. If 0 or less then zero all the data is exported as URL. The default value is 0.

•outputNulls: if ‘true’ attributes that have the special 'null' value - i.e. that are not present in the object - are still rendered, either as ‘xsi:nil’ elements or as empty attributes. If ‘false’ or omitted null attributes are not rendered (the default behavior).

•navOptions: comma-separated list of data navigator options to use. The default value is ‘Default’.

So for example:

    . . .

    <objectUI name="newStory" useAttributesOrder="true" iconName="ui_story" iconSize="68">

      <default mode="Normal" />

      . . .

      <init dataMaxSize="5000" outputNulls="true" navOptions="Referencing, Sources, Dests">

        <gn4:story>

          <xsl:element name="authors">

            <xsl:value-of select="$context/lc:LoginContext/@UserFullName"/>

          </xsl:element>

        </gn4:story>

      </init>

      .  .  .

    </objectUI>

  . . .

defines a ‘newStory’ form with an initialization XSLT that acts on data navigator XML that has all the binary data attributes smaller than 5000 bytes rendered directly as data in the XML (dataMaxSize="5000"), contains the null attributes (outputNulls="true") and includes the referencing, sources and destinations extra information (navOptions="Referencing, Sources, Dests").

If the options URL parameter is omitted the system uses default – i.e. outputs referencing objects and creation / last modified details.