Related information
Parse XML rules
|
|
Records can be created in various ways. You can add a new record to your application or copy an existing one. You can specialize existing rules by creating a copy in a specific ruleset, against a different class or (in some cases) with a set of circumstance definitions. You may copy data instances but they do not support specialization as they are not versioned.
Based on your use case, the Create, Save As or Specialization form is used to create the record. The number of fields and available options vary by record type. Start by familiarizing yourself with the generic layout of these forms and their common fields:
This
Create a Parse XML rule by selecting Parse XML in the Integration-Mapping category.
A Parse XML rule has three key parts:
Field |
Completing the Field |
|
Apply to |
Select a class for this rule. The class is typically derived from the Data- base class or Work- base class. The list of available class names depends on the ruleset you select. Each class can restrict applying rules to an explicit set of rulesets as specified on the Advanced tab of the class form. |
| Namespace Qualifier |
Enter a name to group logically related XML documents. This value is arbitrary and is used only to differentiate identical element names that are used in different contexts. (You can include special characters such as @, % & * in this key part.) Although conceptually similar to a XML namespace, the Namespace key part is not used for matching namespace-qualified element names as defined by a Document Type Description (DTD) or XML Schema (XSDL) definition. If this Parse XML rule was created by the Import XSD/DTD wizard from a XML Schema Definition (XSD) file, the namespace in the XSD is used. If the XSD file doesn't identify a namespace, the value |
| Root Element Name |
Enter the name of the root element of the XML documents to be parsed by this rule; this must be a valid Java identifier. See How to enter a Java identifier. |