Business rule actions and properties
When you define a business rule in System Manager, with
a combination of detection type, effective time, event, and any
associated properties, you will also define the condition that triggers
the business rule. Additionally, you also select and configure the
actions that activate when executing the business rule. At run time,
rule actions execute when the rule engine detects and triggers the
business rule.
The available actions are:
- Collaboration Invocation
- Collaboration Property Modification
- Logging
- Email
- Failed Event
Collaboration invocation
The collaboration to be invoked must be bound to an external
interface just like the collaboration for external clients. The
following information is required to invoke a collaboration:
- Collaboration object name
- Port name
- Business object key attribute name
- Key attribute in business object probe
- Business object type
- Business object verb
To enter the key attribute value, do one of the following:
- Select a business object probe attribute from the combo box.
If you do this, the value of the selected business object probe
attribute is used as the key attribute value for the business object.
- Directly type in a key value.
Collaboration property modification
The following information is required to modify collaboration
properties:
- Collaboration object name
- Property name
- Property value
Logging
The following information is required to write a message
to the InterChange Server Express log file:
- Log level, that is, Info, Warning, Error or Fatal
- Log message
Email
The following information is required to send notifications
and confirmations to the user or administrators:
- Recipient address
- Message body
The following information is not required to send notifications
and confirmations, but is recommended for inclusion:
- Mail server address
- Return address
- Message subject
Note:
If the mail server address is set, messages are
sent using JavaMail. If this property is not set, messages are sent
either using JavaMail or the Email connector. You must configure
the server for sending mail, or the send will fail and log an error
message in the server log.
Failed Event
A set of failed event APIs is included with the business
rule functionality. When the rule is set to Synchronous, a failed
event action also exists for the rule engine.
Note:
When the business rule involves the detection of
a business object probe event, you can elect to fail the collaboration
flow that spawns the business object probe event by using the "Failed
event" action. When this action is used in a business rule,
the collaboration flow that spawns the business object probe pauses
and waits for the business rule trigger result before continuing.
When the probe triggers a business rule that contains a "Failed
event" action, a collaboration exception is shown and the collaboration
flow fails.
No user-specified properties need to be set for this action.
