Deploy dialog sets using the XML configuration interface

Use xmlaccess.sh (xmlaccess) to work with dialog sets.

We can import dialog sets by specifying the value create for the action attribute. See code sample 25.

Code sample 25:

01 <request type="update" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="PCM_1.0.xsd">
 02   03  <portal action="create">
 04     <dialog-set>
 05         <dialog name="dialog1">
 06             ...
 07         </dialog>
 08         ...
 09      </dialog-set>
 10  </portal>
 11 </request>

We can export dialog sets by specifying the value export for the action attribute. For example, use this option for staging or migration purposes. Code sample 26 shows how we can export a single dialog definition dialog1.

Code sample 26:

01 <request type="update" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="PCM_1.0.xsd">
 02   03  <portal action="export">
 04     <dialog-set>
 05         <dialog name="dialog1">
 06     </dialog-set>
 07  </portal>
 08 </request>

When we export dialog sets or definitions, use wildcards. Code sample 27 shows how we export all available dialog definitions.

Code sample 27:

01 <request type="update" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="PCM_1.0.xsd">
 02   03  <portal action="export">
 04      <dialog-set>
 05          <dialog name="*">
 06      </dialog-set>
 07  </portal>
 08 </request>

Code sample 28 shows how we export all dialog definitions the name of which starts with the string toBeExported.

Code sample 28:

01<request type="update" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="PCM_1.0.xsd">
 02   03    <portal action="export">
 04        <dialog-set>
 05            <dialog name="toBeExported*">
 06        </dialog-set>
 07  </portal>
 08 </request>

Code sample 29 shows how we export all dialog definitions the name of which ends with the string toBeExported.

Code sample 29:

01 <request type="update" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="PCM_1.0.xsd">
 02   03  <portal action="export">
 04      <dialog-set>
 05          <dialog name="*toBeExported">
 06      </dialog-set>
 07  </portal>
 08 </request>
 

Code sample 30 shows how we export all dialog definitions the name of which contains the string toBeExported.

Code sample 30:

01 <request type="update" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="PCM_1.0.xsd">
 02   03  <portal action="export">
 04      <dialog-set>
 05          <dialog name="*toBeExported*">
 06      </dialog-set>
 07  </portal>
 08 </request>

We can delete dialog sets by specifying the value delete for the action attribute. Code sample 31 shows how you delete a single dialog definition with the name dialog1. Use the same wildcards as for exporting.

Code sample 31:

01 <request type="update" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="PCM_1.0.xsd">
 02   03  <portal action="delete">
 04      <dialog-set>
 05          <dialog name="dialog1">
 06      </dialog-set>
 07  </portal>
 08 </request>

We cannot use xmlaccess.sh to merge an updated dialog definition with an existing one that you imported earlier. The xmlaccess request type update overwrites the specified existing portal resource with the new one. Therefore, to merge a previous dialog definition with a newer one, we need to manually merge the two XML scripts. To merge the two XML scripts, verify the new dialog definition contains both the new sections and the old sections to preserve.

Parent Transitions