<< Previous in series
In this post we are going to go through the Integration Component field properties in detail because these are the properties that you will modifying frequently.
Type: This property can have one of the three values
- Data : This is the default type for the business component fields vanilla and custom fields.
- System: This is the default type for the business component system fields (Id, Created, Updated).
- Custom: This is new type that has been introduced in Siebel 8.0. I haven’t had a chance to play with property thoroughly but whatever I have seen so far this property can used to introduce tags with constant values.
Name, External Name and XML Tag: These three properties are related. They are just three different representation of the same field and are used at different time. Let’s go through them one by one
- External Name: This is the name of the business component field. Let’s say you added a new field “SR Number” in your business component that you need to sent to external application as part of your XML. So, you will create a new Integration Component field and mention “SR Number” in the External Name property.
- Name: For most of the scenarios this value will be same as External name. There are very few cases where you will need to change this value and we will go through one such scenario later in the series.
- XML Tag: The external application expects new XML Tag to be “ServiceRequestNumber” then in the XML Tag property you will mention “ServiceRequestNumber” as value.
XML Style: This is very important property and can have one of the three values:
- Attribute: If you define XML Style of your field as an “Attribute” then once your Siebel Message is converted into XML Hierarchy it will appear inside a XML Tag
- Element: Your field will appear as an XML Tag inside XML Hierarchy
- ComponentElementValue: You can define one field as ComponentElementValue and it will appear value of the the IC to which this IC fields belong. I haven’t been able to exact practical use of this property, so my understanding might not be accurate. Please feel free to correct or enhance it if you can.
Below image will show what effect these properties have on fields when they appear in XML
Attribute is property of element used to describe more about element. So, how is it decided that, to which element this attribute will belong?? This is where the next property comes into play.
XML Parent Field: Usually this field does not have any value but when you define a field as an attribute then you need to specify to which element this attribute belongs. In the above example I wanted to make App an attribute of the Folder element. So, as shown in the screen shot below I defined Folder as parent of App.
Rest of the properties are self explanatory but if you have any questions about them, do let me know. Before I end this post I have a question for you
What if I define an Integration Component field as Attribute but leave its XML Parent Field blank???
<< Previous in series