No matter your business or position, you have decisions to make for your business
processes. Oracle Integration Service supports Decision Model and Notation (DMN),
the industry standard for modeling and executing decisions. A Friendly Enough
Expression Language, FEEL, makes development intuitive. And decision
models are reusable. So, for simpler decision making, use DMN instead of
Oracle Business Rules. Let's explore decision modeling by
automating a simple decision like: Do I need an umbrella, a raincoat, or an
overcoat for today's weather? The business process starts with a form,
where you enter the forecast values for the current temperature and the chance
of rain. The decision model analyzes the data; the human task displays the results.
How can you make the decision quickly and effectively with decision modeling?
First, create the model. It's the container for the decisions, input data,
and decision services. Let's look at the five main steps in designing a decision
model. Begin by adding the result decision "What To Bring" for today's
weather. Then, add the supporting decisions that feed into the result
decision. You'll use two additional decisions---temperature and weather rain
is expected---to decide what to bring. The Decisions pane shows the decision list. A
decision can reference several of the decisions that occur below it in the
list, which is why the final result decision is listed first followed by the
supporting decisions. After your decision framework is in place, define the inputs
needed to make the decision. Add a data type for the forecast, define
temperature and precipitation as its attributes, then add forecast as input
data. Continue by defining the logic behind the decision-making process. If
the chance of precipitation is greater than 80, then the condition is true and
rain is likely. If the temperature is greater than 65,
then it's warm. Else, it's cold. The "What To Bring" result decision uses a table to
process the supporting decision results--- temperature and rain---and provide an
answer. Use a decision table anytime you have
multiple conditions that interact to determine different outcomes. Each row in
the table is one rule. These columns are for the input data. You can add more
columns as needed. The last column is for the output data. Easily select values
based on the input data you already defined to enter the four possible
outcomes of the final decision. If it's warm and rainy, bring an umbrella. Cold
and rainy, better wear a raincoat. Cold and dry, bundle up in an overcoat. Warm
and dry, you're all set. No need to bring anything. It's a good idea to test the
decision model. For example, if it's 85 degrees and there's an 85 percent chance
of rain, then it's warm and rain is expected, so
carry that umbrella. To use your decision model in your process applications, add a
new decision service. Define "What To Bring" as the final decision to output,
and define forecast as the input data to use. You created a decision model, but how
do you use it in an application? First, activate a snapshot of the decision
model to the DMN server, add the decision model and service to the process, map the
data coming into the decision and exiting from the decision, and then try
it in runtime. Just start the Forecast application, enter the temperature and
chance of rain, and submit the form. Now view the results and be prepared for
whatever the weather may be. For more information, check out
cloud.oracle.com/integration.