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.
In the first phase, only scheduled orchestrations will be addressed.
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.
For regular information on Oracle PaaS become a member in the PaaS (Integration & Process) Partner Community please register here.