Skip to main content
Testing my integration on Oracle Integration Cloud Service (ICS)

Ramping Up

The Jenkins Role-Based Authorization Strategy plugin is an excellent approach to normalize the Jenkins users into roles that can then be notified via pipeline input and emails to perform action in the release management workflow.  

This blog focuses on the pipeline script that can be implemented once the plugin is configured for use which consists of the following steps.

1. The "Role-based Authorization Strategy" plugin must first be installed in the "Managed Jenkins...Manage Plugins" dialog. 

Batch Scope

The batch scope within a MuleSoft application enables the ability to process a message as a batch, splitting the incoming payload into individual records to be processed. While the default values within this scope can be used, considerations around what these default values provide along with implications of these chosen values are explained within this article.


The batch scope configurations to be discussed are limited to just the General configurations. For reference, the default values for this configuration are shown below:

There is an issue adding link fields to PCS 17.2.3 forms using the new web form design tool. At runtime, the value stored in the link's data element is lost once the form is submitted. This describes the problem and provides a fairly simple workaround.

A tenet of any integration toolset is the ability to interact with databases. With standards in place, this for the most part is fairly easy. But sometimes, the particulars of a database can create some unexpected complexity. One example of this is an integration solution developed within Mulesoft that invokes Oracle PL/SQL stored procedures and functions. In this scenario, knowing about some of the complexity beforehand will ensure less frustration by a developer during the development phase.

Others may disagree, but I am a fan of creating the first cut of ADF forms for Oracle BPM using the human task's auto-generation feature.  While this worked well in previous releases, in, and small manual edits are now needed to eliminate the errors on the generated form.

There are now two types of errors caused by 12.2.1.x auto-generation - edAttTy errors and duplicate ID errors. 


While this blog describes the manual edits you can make to the auto-generated .jspx files to correct the issues:

Behavior-driven development (BDD) can prove an excellent augmentation when added to an existing, healthy development framework and testing practice.

Now more than ever, organizations are having to transition to new ways of working as a result of the on going digital transformation. The rise in demand for mobile applications, cloud-based services, ability for citizen developers to create new applications, and access to real-time data that is meaningful and actionable is driving a tremendous need for organizations to be nimble and responsive. The key underlying component of this disruption is the ability to easily and quickly assemble data, services, and events from disparate systems into something meaningful and beneficial.

Moving BPM operations to the cloud frees up resources and money. One of the biggest benefits is the speed at which companies can get started. Getting the Oracle Process Cloud Service setup in the cloud, of course, is blazingly fast compared to an on-premise install. It also is more flexible from a cost and commitment perspective as there’s no need to install and implement complex initiatives on premise. Here are a few simple tips for ensuring cloud-based BPM success:

A few years back when I was leading development teams in a large IT shop, I recall a Senior Operations leader asking me this:

"How can I do BPM with smaller teams and workgroups?  I just can’t justify the expense for a team of 6 or 8."

Subscribe to Blog Lead Image - Cloud on blue