IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > Siebel Business Applications > Overview of WebSphere Adapter for Siebel Business Applications > Technical overview > Outbound processing > Outbound operations
Create operation
The Create operation creates the corresponding Siebel business component hierarchy in the Siebel application.
During the Create operation, the following occurs:
- Each of the child object is created first, and then the parent object is created. After all the child objects are created, the parent object is saved. By saving the parent object after creating all the child object, you can roll back all the child objects that were created, if the top-level Create operation fails.
- Field values are set for the simple attributes.
- Each of the business component records is saved.
- In case of a failure, the adapter generates a SiebelCreateFailedException error.
- If the Siebel application generates a duplicate record error, the adapter generates a DuplicateRecordException error.
- The output business object is populated with values for the key attributes.
Each of the child container attributes is processed as follows:
- The key attributes are not set on the parent business component. The Siebel application generates the key attributes when a record is created. If the key attributes are set, Siebel returns an exception and sets the read-only fields populated with values.
- If the child container is a business component of a PickList, and you want to select an existing child instance, do not create a child business object. Instead, set the value on the parent container.
For example, if you pick an existing Business Address instance under the Account object, set the PrimaryAddressId instead of creating a Business Address instance. However, to create a child instance, you must populate the non-key attributes in the child business component so that the adapter tries to create the corresponding child instance in the Siebel application.
- If there are static Picklists, then the corresponding simple attribute in the business object is required. If a value is not listed in the Picklists list of values, the adapter tries to populate a value. If the list is unbounded and Insert is enabled, the operation is successful.
If the adapter is unable to populate the value by itself, the operation fails.
- With multi value links, the child record is created. If the child Create operation fails, the child record is rolled back. If the parent Create operation fails, all the child and the parent records are rolled back.
- The adapter attempts to select an existing child business component instance (for example, Association) based on the value of all the attributes in the corresponding child business object. If a matching child business component instance is found, it is associated with the parent. If a matching child business component instance is not found, a new child business component is created and associated with the parent business component.
- If the child Create operation fails, the child component is rolled back. If the parent Create operation fails, only the parent component is rolled back. Because association components can also be individual components, as well as child component of other components, a child component, or parent component cannot be rolled back after an associated child component has been created.