Previous Next

Imports one or more sets of literal appdata or metadata into a USoft repository. To build the data to be imported from executing USoft Blend directives, instead of supplying them as literal data, use pc:XmlImportApply instead.

Returns an XML document. See the "Return document" section below.


commit-mode  :=  { commit | rollback }

The required alias identifies the connection to the Rules Engine that you want to use. For aliases, see pc:RunRulesService.

The optional commit determines whether or not the operation is committed after import. Choose the "rollback" option for debugging purposes, in particular to find out if the external data violate any rules. In terms of data change, the net effect of running the operation with "rollback" is null.

To import successfully, you must specify either the source attribute or the data-to-be-imported XML content. If you use source, its value must point to an existing file on the file system that contains the data. Otherwise, the <pc:XmlImport> element must have exactly 1 child element.



This example resets a "Allow_Disable_Constraint" configuration parameter in USoft Authorizer so that, in a next step, data may be imported against a disabled Rules Engine.

<pc:XmlImport connection="{$authconn}"  commit="commit">
  <Additional_Parameters documentName="Additional Parameters">
    <T_AUTH_OC_PARAMS OC_ID="LAN" SET_TYPE="URE" PARAM_NAME="Allow_Disable_Constraint" PARAM_VALUE="True"/>



collapseImport format
collapseReturn document
collapseProcessing the return document



See Also