Table 16. Integration Object Hierarchy to XML Document Method Input Arguments
|
|
|
|
Siebel Message |
SiebelMessage |
Hierarchy |
The Integration Object Hierarchy to be converted to XML. |
XML Character Encoding |
XMLCharEncoding |
String |
The character encoding to use in the XML document. The default is UTF-16 for the Unicode version of Siebel applications. |
Use Siebel Message Envelope |
UseSiebelMessageEnvelope |
String |
Inserts the Siebel Message Envelope into the XML document. The default is True. |
Ignore Character Set Conversion Errors |
IgnoreCharSetConv Errors |
String |
If some characters cannot be represented in the destination character set (like the local code page), the errors can be ignored. The errors are not ignored by default. For both situations, a warning error entry is created. |
Tags on Separate Lines |
Tags on Separate Lines |
String |
Default is False. When True, a line feed is placed at the end of each tag. |
XML Header Text |
XMLHeaderText |
String |
Text to prepend to the beginning of the XML document data. |
n/a |
GenerateNamespaceDecl |
String |
Default is False. If True, the namespace declaration will be generated. You must manually create and name this input argument if it is required for your business needs. |
n/a |
GenerateProcessingInstructions |
String |
Default is True. If set to False the Siebel processing instructions are not written. You must manually create and name this input argument if it is required by your business needs. |
n/a |
GenerateSchemaTypes |
String |
Default is False. If set to True, then XSD schema types will be generated if set on the integration objects user properties. You must manually create and name this input argument if it is required by your business needs. |
n/a |
Namespace |
String |
If a namespace is defined here, it will override any namespace defined in the user properties of an integration object. You must manually create and name this input argument if it is required by your business needs. |