1. Using Integration Insight in Oracle Integration Generation 2
  2. Associate a Model to a Business Process Implementation
  3. Associate a Model to an Integration
  4. Supported Integrations Actions

Supported Integrations Actions

You can map milestones to only orchestration integrations. Other styles are not supported.

You can map milestones to the following actions in an integration (business process implementation):

  • Assign: When mapped to an Assign action, a milestone is considered passed and identifier/indicator values are extracted on entry or on exit of the Assign. You can define extraction criteria using message parts that exist on entry or on exit of the Assign, depending on the option you select.

  • Callback: When mapped to a Callback action, a milestone is considered passed and identifier/indicator values are extracted on entry of the Callback. You can define extraction criteria using only message parts that exist on entry of the Callback.

  • Fault Return: When mapped to a Fault Return action, a milestone is considered passed and identifier/indicator values are extracted on entry of the Fault Return. You can define extraction criteria using only message parts that exist on entry of the Fault Return.

  • Invoke: When mapped to an Invoke action, a milestone is considered passed and identifier/indicator values are extracted on entry or on exit of the Invoke. You can define extraction criteria using message parts that exist on entry or on exit of the Invoke, depending on the option you select.

  • Foot 1Log (new in 20.4.2): When mapped to a Log action, a milestone is considered passed and identifier/indicator values are extracted on entry of the Log. You can define extraction criteria using only message parts that exist on entry of the Log.

  • Foot 1Notification (new in 20.4.2): When mapped to a Notification action, a milestone is considered passed and identifier/indicator values are extracted on entry of the Notification. You can define extraction criteria using only message parts that exist on entry of the Notification.

    For the indicators that are associated with the milestones mapped to a Notification action, the following additional options must be set while defining the indicator xpath in the Insight Designer:


    Notification action options
    • Use Notification To: the <To> mail ID associated with the notification
    • Use Notification From: the <From> mail ID associated with the notification
    • Use Notification Subject: the subject of the notification mail

    These options are in addition to the generic xpath support (Launch Expression Builder) supported for all other actions.

  • Re-throw Fault: When mapped to a Re-throw Fault action, a milestone is considered passed and identifier/indicator values are extracted on entry of the Re-throw Fault. You can define extraction criteria using only message parts that exist on entry of the Re-throw Fault.

  • Return: When mapped to a Return action, a milestone is considered passed and identifier/indicator values are extracted on entry of the Return. You can define extraction criteria using only message parts that exist on entry of the Return.

  • Schedule: When mapped to a Schedule action, a milestone is considered passed and identifier/indicator values are extracted on exit of the Schedule. You can define extraction criteria using message parts that exist on exit of the Schedule.

  • Stop: When mapped to a Stop action, a milestone is considered passed and identifier/indicator values are extracted on entry of the Stop. You can define extraction criteria using only message parts that exist on entry of the Stop.

  • Foot 1Switch (new in 20.4.2): When mapped to a Switch action, a milestone is considered passed and identifier/indicator values are extracted on entry of the Switch. You can define extraction criteria using only message parts that exist on entry of the Switch.

    Note:

    The Switch action contains two branches by default: IF and Otherwise (default). The milestone must be mapped to either of these two branches. Be sure that you don't map the milestone to the Switch action itself.
    Switch action branches

  • Foot 1Throw New Fault (new in 20.4.2) : When mapped to a Throw New Fault action, a milestone is considered passed and identifier/indicator values are extracted on entry of the Throw New Fault. You can define extraction criteria using only message parts that exist on entry of the Throw New Fault.

  • Trigger: When mapped to a Trigger action, a milestone is considered passed and identifier/indicator values are extracted on exit of the Trigger. You can define extraction criteria using message parts that exist on exit of the Trigger.

Mapping milestones to other actions is not supported.


Footnote Legend

Footnote 1:

If you want to map model milestones to any of the actions added in 20.4.2 (released in November 2020) in integrations activated prior to 20.4.2, you must reactivate those integrations to use the new actions in Insight.