Account Import XML Schema Guide › Example XML Data File › Schema Notes

Schema Notes

<accountimport> element

The <accountimport> element denotes which version of CA DataMinder the account import operation will synchronize with. If this tag includes preserveuniquegroups='true', then if a group with a unique name exists in the xml file and the same group name is also unique in the CA DataMinder database but in a different location, then a <movegroup> command is performed to move the group from the current CA DataMinder location to the new location specified in the xml file, leaving only one group with that name in the CA DataMinder database; if this tag includes add_db='true', then the current CA DataMinder group hierarchy is added to the <root> element (see below) when the XML file is imported. If the XML file does not contain a <root> element, then one will be added.

<root> element

The <root> element creates the entire hierarchy of groups and users. There can only be one <root> element per file. If your groups and users are contained in separate databases, you may want to create your hierarchy using the <hierarchy> and <user> elements - see below.

<hierarchy> element

The <hierarchy> element represents a subsection of the group structure. The relativeTo attribute value is the name of the group in the <root> section where you want to insert this subsection. Any group name specified as a relativeTo attribute value must already exist and be unique within the <root> section. In the following example, the <root> section must contain a unique group called Development; a QualityAssurance group is then created within it:

<hierarchy relativeTo='Development'>
  <group name='QualityAssurance'/>
<\hierarchy>

The relativeTo attribute is optional, but if it is not included, the hierarchy is inserted at the top of the <root> section, that is, it will be identical to the <root> section. If you think you need a <hierarchy> section without a relativeTo attribute, it may be better to add this directly into the <root> section, as the XML file can then be processed quicker.

<user> elements

<user> elements in the <users> section are added to the <root> section based on their <group> element. The <group> element can specify either the complete group name or a relative group name. For example, the following element adds Spencer Rimmel to the Unipraxis/Directors group, while the policyexempt attribute exempts him from policy.

<users>
  <user policyexempt='true'>
    <name>SpencerRimmel</name>
    <group>
      <element>Unipraxis</element>
      <element>Directors</element>
    </group>
  </user>
</users>

The next example adds Lynda Steel to the same Directors group. As with the <hierarchy> element's relativeTo attribute, if the isRelative attribute is set to true, the first <element> value must specify a group that already exists and is unique in the <root> section. In this example, no policyexempt attribute is specified, so the attribute defaults to 'false'. That is, Lynda Steel is not exempt from policy.

<users>
  <user>
    <name>Lynda_Steel</name>
    <group isRelative='true'>
      <element>Directors</element>
    </group>
  </user>
</users>