Not sure whether this lives in the forum WebPublisherPro or WishList

Anyway, you 'entice' us within the "What's New in Version 7.0?" section by introducing sort order using XML tags (SortFields). Please add it to the documentation, as I had to go to the Input Schema to work it all out.... Your support web site was down/very slow.

In fact, here it is:

<xs:element name="SortFields" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The parent of the SortField elements. 
                      Specifies the type of sort the program will use to sort.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="SortField" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>Specifies the fields the program will use to sort.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:simpleContent>
            <xs:extension base="xs:string">
              <xs:attribute name="type" use="optional">
                <xs:annotation>
                  <xs:documentation>Specifies the SortField type: sort (default) or alternate.</xs:documentation>
                </xs:annotation>
                <xs:simpleType>
                  <xs:restriction base="xs:string">
                  <xs:enumeration value="sort" />
                  <xs:enumeration value="alternate" />
                  </xs:restriction>
                </xs:simpleType>
              </xs:attribute>
              <xs:attribute name="reverse" use="optional">
                <xs:annotation>
                  <xs:documentation>Specifies whether SortField is sorted reverse: Y or N (default).</xs:documentation>
                </xs:annotation>
                <xs:simpleType>
                  <xs:restriction base="xs:string">
                    <xs:pattern value="((Y|y)|(N|n))" />
                  </xs:restriction>
                </xs:simpleType>
              </xs:attribute>
            </xs:extension>
          </xs:simpleContent>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
    <xs:attribute name="sort" use="optional">
      <xs:annotation>
        <xs:documentation>Specifies sort method to use: 
                          specify, relevance, unsorted or textbase (default).</xs:documentation>
      </xs:annotation>
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:enumeration value="textbase" />
          <xs:enumeration value="specify" />
          <xs:enumeration value="relevance" />
          <xs:enumeration value="unsorted" />
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
  </xs:complexType>
</xs:element>

...and an example for those of you searching for it in the forums.

<SortFields sort='specify'>
  <SortField type='sort' reverse='Y'>DATE_PUB_WEB</SortField>
  <SortField type='sort' reverse='Y'>DATE_CADUCIDAD</SortField>
</SortFields>

The question is: What happens if the field is empty (null).

If the sort field is empty in a particular record, that record will sort before records where the field is non-empty. In other words, it behaves as if you chose "Option if primary sort field is empty: Sort Those Records First."

The "omit empties" sorting feature (Omit Those Records) is not available for Web sorts.