The Detailed Editing Panel

 

Detail editing panel shows the detailed properties of the selected node in the XTT tree. The general rule for text fields in the editing panel is that when an object outside the text field or area is selected the value is set. For example, the name field will be set after the next field is selected or the XTT tree selection is changed. The change can be seen on the XTT tree.

xtt:template

image\ebx_1235454623.gif

Figure: The language encoding menu of the detailed editing panel

Encoding – The Encoding menu specifies the text encoding for any output XML file. The choices are database local (the text encoding specified in the database), UTF-8, UTF-16LE and UTF-16BE. The default is database local. If database local is Big5 and the encoding setting is database local, then the output XML will be encoded in Big5.

Header – The header box it is where you add information like a schema file or applicable XSL in the output XML file. The XTT engine will print the content in this block to the output XML file after <?xml version=”1.0”…?> . Be sure to type valid XML content in this header block.

image\ebx_-1980216310.gif

Parameters – you may add as many parameters as you want. The parameter name must be unique. Press the 'delete' key to remove a selected row. The last empty row cannot be removed. The parameter default can be empty.

image\ebx_-216262095.gif

There are a few display settings available for the output XML file. The default value for each setting is 'system default'. The display settings will apply to all XTT objects unless specified otherwise.

Empty abbreviation –

0 – always show start and end tags for an element, even if its content is empty.

1 – to use the abbreviated form of the end tag if no sub element is produced. For example, <Department id=”1001” />.

2 – hide the start and end tags if the element content is empty; no text, no attribute, no child element. If the element only has attributes, it will use type 1 abbreviation.

Indent – the number of indent spaces in the source document for each sub level as displayed in a text editor. For example, if the number is 2, then the start tag of the root will be indented 2 spaces, and a sub node of the root will be indented 4 spaces.

Line break –

0 – do not add any line break.

1 – add a line break after an end tag.

2 – add a line break after every start and end tag.

Line break char – the character(s) to be added as line break.

0 – {CR}

1– {LF}

2 – {CR}{LF}.

Display mode – the way to display text data. Generally, the text character '<' will be replaced with '&lt;' in the text content. But '<' can be used if it is enclosed in the CDATA section, or the text content itself is already an XML fragment and can be added into the output XML as a part of the XML content. There are 3 different ways to display text data.

0 – display XML text content with the escape character.

1 – use a CDATA section to enclose the text value.

2 – make the content native XML text.

Null handling – specify how to handle null data.

0 – skip null data. If it's an attribute, then do nothing.

1 – show empty content. For example, <NAME></NAME>.

2 – display 'NULL'. For example, <NAME>NULL</NAME>.

LO mode – specify how to handle large objects.

0 – dump large object data directly into the XML file. Print a string if it is CLOB type data or print in hexadecimal format if it is BLOB type data.

1 – to store large object data in external file.

user-defined element

The following represents the properties of a user-defined element in the XTT object tree.

image\ebx_-1343786248.gif

Figure: The detailed editing panel for a user-defined element

Name – the element name. It is case-sensitive and cannot be empty.

Value – the text value. This is a text expression, which can have both constant text and a variable reference. For example, you might want to add the country code to all phone number data, such as "886 - $SQL1.PHONE", where "886 –" is the constant text and "$SQL1.PHONE" is the variable reference. The XTT engine will concatenate both into the output XML file as the text value of the element.

Browse button – the browse button will list all the available parameters and variable references at the current level. You can choose the variable name(s) and insert them into the text expression field next to the browse button.

image\ebx_-430771040.gif

Figure: The query view for a user-defined element in the detailed editing panel

An element can have embedded query properties in it. A valid XTT element will have both fields (name and command) specified or both left as empty.

Name – the query name. It will be used as a variable reference in the sub nodes.

Command – SQL query statement. The statement must be able to generate a result set. For example, you cannot type a delete table statement here.

The display settings are similar to the ones in xtt:template, But the default is 'follow template setting'.

Null handling – there are only two choices instead of three. If 'follow template setting' is selected and the template has the null handling setting as '0 - skip null data', then it will be treated as '1 show empty content'.

1 – show empty content. For example, <NAME></NAME>.

2 – display 'NULL'. For example, <NAME>NULL</NAME>.

attribute Node

image\ebx_1841796433.gif

Figure: An attribute viewed in the detailed editing panel

Name – attribute name. The Name field cannot be empty. Multiple attributes must have names unique to the same parent element.

Value – the attribute value; a text expression field.

There are only two display settings for an attribute node; null handling and LO mode. The default for both is 'follow template setting'.