April 3, 2015

EAI - Defining Field Dependencies in Integration Objects

Define dependency between fields by using the user properties of the integration component field. The names of these user properties must start with FieldDependency, and it is recommended that the value of each property contain the name of the field on which the associated field is dependent. The EAI Siebel Adapter processes fields in the order defined by these dependencies, and generates an error if cyclic dependencies exist. 

The EAI Siebel Adapter automatically takes into account the dependencies of the fields set by a PickList on the fields used as constraints in that PickList. For example, if a PickList on field A also sets field B, and is constrained by field C, then this implies dependencies of both A and B on C. As a consequence, the EAI Siebel Adapter sets field C before fields A and B. 

User Property Name: FieldDependency<field_name>
Value: Any active integration component field name within the same integration component 

For the complete list Of Integration Object User Properties, refer to bookshelf.

No comments:

Post a Comment