Integration Schemas
84
Integration Guide
Object query content You can use query elements only within the context of a service level schema.
The following content format is in the object query element:
T Element MXPERSONQuery is type MXPERSONQueryType.
T Complex type MXPERSONQueryType has elements for all the configured
attributes of the top object (PERSON) of the object structure.
The following differences exist between the content of the query and the object
set:
T The query element includes only the top object of the object structure.
T The query element does not include nonpersistent columns.
T The query element allows two occurrences of the elements to support a query
on a range, such as a date range.
Since the query includes only the top object of the structure, you cannot have, for
example, a query for a person by phone number. The phone number exists in the
child PHONE object.
Object delete content You can use delete elements only within the context of service level schemas.
The following content format is in the object delete element:
T Element MXPERSONDelete is type MXPERSONDeleteType.
T Complex type MXPERSONDeleteType has elements for all the configured
attributes of the PERSON object.
The following differences exist between the content of the delete and the object
set:
T The delete element includes only the top object of the object structure.
T The delete element does not include nonpersistent columns.
Object Schemas
Object schemas define the content of objects. These schemas are not used directly
as input and output for any system service. They are used by system services
while defining input and output types.
Each object has a distinct schema, which includes all the persistent fields for a
persistent object and all nonpersistent fields defined for a nonpersistent object.
Schema Name
The naming convention for object schemas is the object name, for example,
PERSON.xsd.
To Next Page
Loading...