IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Developing business processes > Create business rules

Weak type support with business rules

Business object definitions can have XSD wildcards that can be used in business rules logic.

Such wildcards can represent a placeholder for any of the following:

• an arbitrary simple type (xs:anySimpleType)
• an arbitrary complexType (xs:anyComplexType)
• an arbitrary type (simple or complex, called 'xs:anyType')
• an arbitrary element (xs:any)

For more advanced mapping and expressions involving weak types or attributes use other components such as interfaces or business objects maps.

Restrictions

• No local variables in a rule set can be of weak type.

• You cannot use weak types in computations or comparisons.

Business rules support of weak types for basic mapping

Input type	Output type	Supported
any	any	Yes. All existing open elements are deleted from the source and the source open elements are added to the end of the closed elements.
	anyAttribute	No
	anyType	No
	anySimpleType	No
	Concrete complex type	No
	Concrete simple type	No
anyAttribute	any	No
	anyAttribute	Yes. All of the attributes are removed and replaced.
	anyType	No
	anySimpleType	No
	Concrete complex type	No
	Concrete simple type	No
anyType	anyType	Yes. Assignment allowed.
	any	No
	anyAttribute	No
	anySimpleType	Yes. Assignment allowed if data is a simple type, for example a string.
	Concrete complex type	Yes. Assignment allowed if data is of a compatible type.
	Concrete simple type	Yes. Assignment allowed if data is of a compatible type.
AnySimpleType	anySimpleType	Yes. Assignment allowed.
	any	No
	anyAttribute	No
	anyType	Yes. Assignment allowed.
	Concrete simple type	No
	Concrete complex type	Yes
Concrete simple type	any	No
	anyAttribute	No
	anyType	Yes. Assignment allowed.
	anySimpleType	Yes. Assignment allowed.
Concrete complex type	any	No
	anyAttribute	No
	anyType	Yes. Assignment allowed.
	anySimpleType	No

Create business rules