Adding or modifying web service elements and attributes

You can use Developer Studioto change the format of the XML code so that it is compatible with your web service. You can:

  • Add, delete, or rename the XML elements.
  • Create XML elements to enable the grouping of existing XML elements. This grouping is only cosmetic.
  • Use attributes instead of elements.
  • Set nillable, MinOccurs, and MaxOccurs attributes of elements.

Related topics

Editing-the-web-service-XML

Handling-null-empty-and-missing-values

You can edit the XML when you publish a web service from AR System. When you consume an external web service, the external web service decides the XML format, and you must conform to it. Developer Studiodisables all editing features in that case. You can select only which fields to map to which XML elements.

XML documents can specify the data type in the document itself instead of in the XML schema. If you want the output document to contain XSI Type information so that the consumers of the web service can process the document correctly, select Support XSI Type above the mapping table.

To add a new element or attribute

  1. Open the web service in Developer Studio.
  2. View the mapping table under WSDL Ports > Port > WSDL Operations > Operation.
  3. Right-click an element in the XML Data Type column to display a list of actions.
  4. Select New > Element or New > Attribute.
    The new element or attribute appears one level below the selected item. You can add form elements, field elements, or field attributes.
  5. Rename the new element or attribute.

To change element ordering

  1. Open the web service in Developer Studio.
  2. View the mapping table under WSDL Ports > Port > WSDL Operations >Operation.
  3. Right-click an element in the XML Data Type column to display a list of actions.
  4. Click Move Up, Move Down, Move Left, or Move Right.

To set XML object properties

  1. Open the web service in Developer Studio.
  2. View the mapping table under WSDL Ports > Port > WSDL Operations > Operation.
  3. Select the element in the XML Data Type column, and click the ellipsis button (...) to open the XML Properties dialog box.
    web_services_xml_properties.gif

The properties of an object indicate the information that the object provides. You can set various property values for the XML Schema objects:

  • DefaultValue—The default value of an element unless it is overridden by the value in the actual document (incoming or outgoing).
  • Element—Whether the object is an element or an attribute.  If the value for Element is true, the object is an element. If the value is false, the object is an attribute. The ROOT element cannot be edited.
  • MaxOccurs—The maximum number of instances of the element. The default value is 1. A value of "unbounded" indicates that the element might be repeated any number of times. For example, a purchase order document might contain any number of line items.
  • MinOccurs—The number of instances of the element. The default value is 1. If the value is 0, the element might or might not be present.
  • Nillable—Whether a node is nillable.  Any leaf node (elements only) can be made nillable. You can set the Nillable attribute to True or False only in the mapping dialog boxes. The document is interpreted according to the rules described in Handling-null-empty-and-missing-values.
  • Type—The XML data type of the element.
  • XML Type—Whether the node is an XML type. Any leaf node (element or attribute) can be identified as XML Type. If XML Type is True, the data can be treated as XML string data. In this case, AR System does not treat it like a regular string, that is, the data is not encoded or decoded.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*