<Destination>

The Destination element specifies the document title, HotSync® destinations, and file destinations for the converted document.

Full element example

    <Destination>
      <Title>My Document</Title>
      <HotSync>
        <Path>John Doe</Path>
        <Path>Jane Doe:</Path>
      </HotSync>
      <ActiveSync>
        <Path>PocketPC</Path>
        <Path>PocketPC:</Path>
      </ActiveSync>
      <Files>
        <Path>c:\My Documents\My Document.pdb</Path>
        <Path>c:\Backup\My Document.pdb</Path>
      </Files>
    </Destination>

Sub-element summary

TagTypeDefaultDescription
<Title> string n/a Document title
<HotSync> multi-string n/a HotSync® destinations
<ActiveSync> multi-string n/a ActiveSync® destinations
<Files> multi-string n/a File destinations

Sub-element descriptions

<Title>

Description
The Title element is mandatory. Its content is a string up to 31 characters in length. The title is also used for constructing the default file name of the destination document.

As of version 4.15 of iSiloX and iSiloXC, in addition to static characters in the title, the title can also have dynamic components such as the date of conversion or the title of the first source file. Dynamic components always begin with the two-character sequence consisting of a backslash and an uppercase X, followed by the component name. If the component has additional parameters, a question mark follows the component name and the parameters follow the question mark. A semicolon marks the end of a component.

The following table lists the available title components:
Component Description
\Xdate; Text: The date the conversion starts.

Default format: A six character sequence in the format Y2M2D2, where Y2 is the last two digits of the year, M2 is the two digit month, and D2 is the two digit day.

Parameters: Any of the following parameters can be provided in any order. Additional characters may also be interspersed between the parameters as separators that are included in the resulting text.

  • Y: The year in natural format (e.g., 1999, 2004)
  • Y2: The year in two-digit format (e.g., 99, 04)
  • M: The month in natural format (e.g., 8, 12)
  • M2: The month in two-digit format (e.g., 08, 12)
  • D: The day of the month in natural format (e.g., 9, 31)
  • D2: The day of the month in two-digit format (e.g., 09, 31)
\Xtime; Text: The time the conversion starts.

Default format: A four character sequence in the format H2M2, where H2 is the two digit hour in 24-hour format and M2 is the two digit minute.

Parameters: Any of the following parameters can be provided in any order. Additional characters may also be interspersed between the parameters as separators that are included in the resulting text.

  • H: The hour in 24-hour natural format (e.g., 2, 23)
  • H2: The hour in 24-hour two-digit format (e.g., 02, 23)
  • M: The minute in natural format (e.g., 8, 51)
  • M2: The minute in two-digit format (e.g., 08, 51)
  • S: The second in natural format (e.g., 9, 38)
  • S2: The second in two-digit format (e.g., 09, 38)
\Xtitle; Text: The title of the first source file.

Parameters: This component has no parameters.



Examples
This example specifies the title for the document to be "Short Stories of Yore".

  <Title>Short Stories of Yore</Title>

If the date of conversion is December 25, 2004, the following sets the title to "041225 Short Stories of Yore". This title uses the default date format.

  <Title>\Xdate; Short Stories of Yore</Title>
If the date of conversion is December 25, 2004, the following sets the title to "12-25-2004 Short Stories of Yore". Notice the inclusion of hyphens between the month, day, and year parameters, which result in the insertion of hyphens between those parts in the same places in the resulting title.
  <Title>\Xdate?M-D-Y; Short Stories of Yore</Title>
If the date of conversion is March 1, 2005, the following sets the title to "Short Stories of 1-3-05 Yore".
  <Title>Short Stories of \Xdate?D-M-Y2; Yore</Title>
If the date of conversion is March 1, 2005, the following sets the title to "Short Stories of 01-03-05 Yore".
  <Title>Short Stories of \Xdate?D2-M2-Y2; Yore</Title>

<HotSync>

Description
Use the HotSync element to specify one or more HotSync® destinations. A HotSync® destination results in queuing of the converted document for installation to a HotSync® user's handheld the next time the user performs a HotSync®. If you do not want the converted document queued for HotSync®, then do not specify the HotSync element.

Within the <HotSync> start tag and the </HotSync> end tag, specify one or more Path elements. Each Path element consists of the destination HotSync® user name string enclosed within the <Path> start tag and the </Path> end tag.

To have the document written to the external memory card, append a colon to the end of the user name. The document goes to the /Palm/Programs/iSilo folder of the first memory card found with enough space for the document.

To have the document written to a specific external memory card and to a specific folder on the card, append a colon and the destination path. The path specifies the memory card and location on the card to which to install the document and must be a full path with slashes as path component separators. Either forward slashes or backslashes may be used as path component separators.

The first component of the path must be the volume name or label of the memory card. If the volume name is empty or not that of a mounted memory card at the time of HotSync®, the document installs to the first memory card with available space.

Following the volume name component is the path of the folder to which to install the document. If the full path ends in a slash, the filename is based on the document title as described above. Otherwise, the last component of the path is the file name the document takes on the memory card.

If any of the folders in the path do not exist at the time of installation, the iSilo™ Install conduit creates them.

Note: The HotSync element only works for the following versions of iSiloX and iSiloXC:

Note: Destination path support is available as of version 4.05 and later of the above versions of iSiloX and iSiloXC.

Examples
This example queues the converted document for installation to the internal memory of John Doe's handheld.

  <HotSync>
    <Path>John Doe</Path>
  </HotSync>
This example queues the converted document for installation to the external memory card of Pam's handheld. Note the colon following the user name.
  <HotSync>
    <Path>Pam:</Path>
  </HotSync>
This example queues the converted document for installation to the /Documents/iSilo folder of the external memory card with the volume label Johns Card of John's handheld under the file name Diary for September.pdb. Note the colon and path following the user name.
  <HotSync>
    <Path>John:/Johns Card/Documents/iSilo/Diary for September.pdb</Path>
  </HotSync>

<ActiveSync>

Description
Use the ActiveSync element to specify one or more ActiveSync® destinations. An ActiveSync® destination results in queuing of the converted document for installation to the "\My Documents\iSilo" directory of either the internal storage memory or to inserted memory cards of a handheld device connected via ActiveSync®. If you do not want the converted document queued for installation via ActiveSync® then do not specify the ActiveSync element.

Within the <ActiveSync> start tag and the </ActiveSync> end tag, specify one or more Path elements. Each Path element consists of the destination ActiveSync® device name string enclosed within the <Path> start tag and the </Path> end tag.

To have the document written to the external memory card, append a colon to the end of the device name. This installs the document to the iSilo subfolder of the default folder for documents on the first memory card with enough free space for the document. Note that some devices may have built-in memory cards and that the order in which the operating system on the device presents the memory cards to the iSilo™ ActiveSync® service provider may differ from one ActiveSync® connection to the next. For specific control over exactly which memory card the document installs to, use the Path destination option described next. The exact destination path depends on the device, but for English language devices, the full path of the destination folder is usually \Storage Card\My Documents\iSilo\.

To have the document written to a specific path on the device's file system, append a colon and the destination path. The path must be a full path with slashes as path component separators. Either forward slashes or backslashes may be used as path component separators.

If any of the folders in the path do not exist at the time of installation, the iSilo™ ActiveSync® service provider creates them.

If the full path ends in a slash, the filename is based on the document title as described above. Otherwise, the last component of the path is the file name the document takes.

Note: The ActiveSync element only works for the following versions of iSiloX and iSiloXC:

Note: Destination path support is available as of version 4.05 and later of the above versions of iSiloX and iSiloXC.

Examples
This example queues the converted document for installation to the internal memory of the ActiveSync® handheld with the device name PocketPC.

  <ActiveSync>
    <Path>PocketPC</Path>
  </ActiveSync>
This example queues the converted document for installation to the external memory card of the ActiveSync® handheld with the device name Jornada728. Note the colon following the device name.
  <ActiveSync>
    <Path>Jornada728:</Path>
  </ActiveSync>
This example queues the converted document for installation to the \Documents\iSilo\ folder of the ActiveSync® handheld with the device name Jornada728 under the file name Diary for September.pdb. Note the colon and path following the device name.
  <ActiveSync>
    <Path>Jornada728:\Documents\iSilo\Diary for September.pdb</Path>
  </ActiveSync>

<Files>

Description
Use the Files element to specify one or more file destinations. A file destination results in the converted document being written to a file. If you do not want the converted document written to a file then do not specify the Files element.

Within the <Files> start tag and the </Files> end tag, specify one or more Path elements. Each Path element consists of the path to a destination file or directory/folder enclosed within the <Path> start tag and the </Path> end tag.

To specify a destination directory or folder, end the path string with the path separation character. The file name will be composed of the title as given by the <Title> tag and the extension .pdb.

Examples
This example results in the converted document being written to the c:\Docs folder under the file name news.pdb.

  <Files>
    <Path>c:\Docs\news.pdb</Path>
  </Files>
This example results in the converted document being written to the c:\Stories folder. Notice that the path to the folder below ends with a backslash, which is the path separation character in Windows®. If the title was specified as Horror, then the resulting file name would be Horror.pdb.
  <Files>
    <Path>c:\Stories\</Path>
  </Files>

©1999-2017 DC & Co. All rights reserved.