X

PaaS Partner Community

Replace Trigger in Orchestration by Vijay Kendai

Juergen Kress
PaaS Partner Adoption

 

imageThis blog is for a new feature coming out in Oracle Integration Cloud (OIC) February 2021 release.

Currently in Orchestration, after a trigger has been added, the user does not have the ability to replace it with another trigger. The user essentially has to re-create the integration to achieve this. With this feature, users will be provided with the ability to replace a trigger with minimal impact and without having the need to re-construct various actions in the canvas. After conversion, users will be provided with appropriate warnings and errors to take any corrective action needed, to bring the integration to a configured state.

What is covered ?

In the first phase, only scheduled orchestrations will be addressed.

  • Schedule trigger will be allowed for replacement only with a REST trigger.

What is not covered ?

  • Replacing schedule in Scheduled orchestrations with REST trigger having multiple verbs
  • Replacing trigger in App driven orchestrations

Details

The following section describes in detail how a schedule can be converted to a REST trigger. On clicking the schedule node, user will be provided with a menu option under more actions to convert to a REST based trigger as shown below. Read the complete article here.

PaaS Partner Community

For regular information on Oracle PaaS become a member in the PaaS (Integration & Process) Partner Community please register here.

clip_image003 Blog clip_image005 Twitter clip_image004 LinkedIn image[7][2][2][2] Facebook clip_image002[8][4][2][2][2] Wiki

Technorati Tags: SOA Community,Oracle SOA,Oracle BPM,OPN,Jürgen Kress

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.