Process Data Definition by Red Maveriks

Processes transform inputs (data) into outputs (data)

We have our BPMN process and if we only want to document our process, this is almost all the work we’ll need to do. However, Akino Fishing Co. wants to not only document, but also automate and execute the processes. For that, we need to define our process data.

A process governs data transformation

Process data refers to the entities that the process manipulates, or interacts with, during its life cycle. To put it simply, a process manipulates things. All these things must first be defined, so that the process does what it’s intended to do.

For our process, we’ll define the following data entities:

• Request
• Parking Space

Oracle BPM Composer allows you to define this in a fairly simple way. First, you create the data structure, that will specify what makes that “thing”. Let’s build an example to understand this better:

What makes a request? How is it defined? Think about it for 5 minutes…

5 Minutes

You should end up with something like this:

• Requester – who made the request
• Request date – when the request was made
• Employee? – is the requester an employee?
• Park date&time – when does the requester want to park
• Fulfilled? – was the request fulfilled?
• State – state of the request: open, closed, pending alternative

So, these set the characteristics, the structure, of our request.

Business Objects vs Data Objects

We define a request as being comprised of these 6 elements, by creating a Business Object. In the BPM process composer select the option Business Object, Read the complete article here.

SOA & BPM Partner Community

For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Facebook Wiki