Structure of the xml-file with the list of Tasks for the application
(Tasks.xml in directory TEXT.en)

This structure individualizes the Codes (shortcuts) of the (Sub-)Tasks of an application depending on the selected language.
And - of course – the description of the (Sub-)Task.

The usage is within a 'CommandCenter' frame where all available Tasks are shown depending on the content of this file.

Another main purpose of the XML-structure within this file is to map the displayed (and entered) Code from the language dependant version to an internal code where the processing within the application depends on.
Further this XML-structure contains information how many parameters have to be supplied when chosing a Code for a Task and language dependant label-text for this parameters

By individualizing the Code depending on the language the user can see a more remindable Code which is really a shortcut of the description of the (Sub-)Task.
Example:
The Englisch 'Order Entry' can have the Code 'OE' attached while the German 'Bestellung Erfassen' can habe the Code 'BE' attached.
Internal there might be 'A8' used for further processing.

Prerequisites:

• None;
  this document accompanies the development of a fat-client with Java (Develop a Fat-Client in Java) and explains the structure of the xml-file with the list of Codes for Tasks.

Example:

• This example is an excerpt from a not yet published project.
  That means, the listed example has nothing to do with the Tutorial to Develop a Fat-Client in Java.

• The sample - an excerpt from the file 'DisplayStrings.xml':
  <!-- Root-Element (Tasks); has to be there otherwise the parser reports an error -->
<Tasks>
<!--            ********************************************* -->
<!-- ********** Marker if entered codes are converted to UpperCase *********** -->
  <UpperCase></UpperCase>
<!--            ********************************************* -->
<!-- ********** List of selectable Codes; displayed as ordered here *********** -->
  <Task>
    <DisplayedCode>P</DisplayedCode>
    <Description>Product</Description>
  </Task>
  <Task>
    <DisplayedCode>PM</DisplayedCode>
    <InternalCode>P1</InternalCode>
    <Description>Maintain Product Data</Description>
    <Parameter1Label>Brand-Code</Parameter1Label>
    <Parameter1MinimumLength>2</Parameter1MinimumLength>
    <Parameter2Label>Product-Code (of the vendor)</Parameter2Label>
    <Parameter2MinimumLength>0</Parameter2MinimumLength>
  </Task>
  <Task>
    <DisplayedCode>PO</DisplayedCode>
    <InternalCode>P2</InternalCode>
    <Description>Order Product Manually</Description>
    <Parameter1Label>Brand-Code</Parameter1Label>
    <Parameter1MinimumLength>2</Parameter1MinimumLength>
    <Parameter2Label>Product-Code (of the vendor)</Parameter2Label>
    <Parameter2MinimumLength>0</Parameter2MinimumLength>
  </Task>
  <Task>
    <DisplayedCode>PL</DisplayedCode>
    <Description>Product-Listings</Description>
  </Task>
  <Task>
    <DisplayedCode>PLO</DisplayedCode>
    <InternalCode>P2A</InternalCode>
    <Description>List Products suggested for automatic order</Description>
    <Parameter1Label>Brand-Code</Parameter1Label>
    <Parameter1MinimumLength>0</Parameter1MinimumLength>
  </Task>
  <Task>
    <DisplayedCode>PLI</DisplayedCode>
    <InternalCode>P3</InternalCode>
    <Description>Generate inventory list of Products (print-option)</Description>
    <Parameter1Label>Brand-Code</Parameter1Label>
    <Parameter1MinimumLength>0</Parameter1MinimumLength>
  </Task>
  <Task>
    <DisplayedCode>PLT</DisplayedCode>
    <InternalCode>P4</InternalCode>
    <Description>Generate turnover list of Products (print-option)</Description>
    <Parameter1Label>Brand-Code</Parameter1Label>
    <Parameter1MinimumLength>0</Parameter1MinimumLength>
  </Task>
  <Task>
    <DisplayedCode>C</DisplayedCode>
    <Description>Client</Description>
  </Task>
  <Task>
    <DisplayedCode>CI</DisplayedCode>
    <InternalCode>C1</InternalCode>
    <Description>Maintain Clients Invoice data</Description>
    <Parameter1Label>Search text</Parameter1Label>
    <Parameter1MinimumLength>0</Parameter1MinimumLength>
    <Parameter2Label>Accounting number</Parameter2Label>
    <Parameter2MinimumLength>0</Parameter2MinimumLength>
  </Task>
  <Task>
    <DisplayedCode>CD</DisplayedCode>
    <InternalCode>C2</InternalCode>
    <Description>Maintain Clients Delivery Adresses</Description>
    <Parameter1Label>Search text</Parameter1Label>
    <Parameter1MinimumLength>0</Parameter1MinimumLength>
    <Parameter2Label>Accounting number</Parameter2Label>
    <Parameter2MinimumLength>0</Parameter2MinimumLength>
  </Task>
</Tasks>

top.

Detailed description of attributes:

• <Tasks> is enclosing the whole xml-structure.
  An attribute name for the whole xml-structure is requiered, as the parser (to read the file and build a structure within a Java-application) is not capable to read more than one xml-structures within in one file.

• <UpperCase> is a marker that the entered code (at the graphic user interface) is converted to upper-case letters before it is compared with the <DisplayedCode> in this xml-structure.
  If is marked, then <DisplayedCode> is converted to upper-case letters before it is displayed in the tree-structure.
  The absence of the <UpperCase> -element means, that the comparison is done case-sensitive.

• <Task> is enclosing the elements for one selectable Code.

• <DisplayedCode> is the code the user can select.

• <InternalCode> is the code used within the application to open the selected (Sub-)Task.
  If this element is missing, then entering the <DisplayedCode> expands the displayed tree-structure to show further selection.
  (This is dependant on your individual implementation of the Application-Start-Frame !).

• <Description> is the explanatory text displayed on the tree-structure of the Task-List.

• <Parameter1Label> is the explanatory text of the additional parameter that can be entered at the Application-Start-Frame.
  If this element is missing, the Label is filled with spaces and the Text-Entry-Field for the parameter is blanked and entering text into it is disabled.

• <Parameter1MinimumLength> is the minimum number of characters that have to be entered before the button to call a (Sub-)Task is enabled.
  If this element is missing, the entered text can be omitted.

• <Parameter2Label> similar to <Parameter1Label>.

• <Parameter2MinimumLength> similar to <Parameter1MinimumLength>.

• <Parameter3Label> similar to <Parameter1Label>.

• <Parameter3MinimumLength> similar to <Parameter1MinimumLength>.

top.

Related Documents:

• Directory Architecture shows the structure of sub-directories with parameter-files.