Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
jBPM6 Developer Guide

You're reading from   jBPM6 Developer Guide Learn about the components, tooling, and integration points that are part of the JBoss Business Process Management (BPM) framework

Arrow left icon
Product type Paperback
Published in Aug 2014
Publisher Packt
ISBN-13 9781783286614
Length 310 pages
Edition 3rd Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
 Salatino Salatino
Author Profile Icon Salatino
Salatino
Arrow right icon
View More author details
Toc

Table of Contents (21) Chapters Close

jBPM6 Developer Guide
Credits
About the Author
Acknowledgments
About the Author
About the Author
About the Reviewers
www.PacktPub.com
Preface
1. Why Do We Need Business Process Management? FREE CHAPTER 2. BPM Systems' Structure 3. Using BPMN 2.0 to Model Business Scenarios 4. Understanding the KIE Workbench 5. Creating a Process Project in the KIE Workbench 6. Human Interactions 7. Defining Your Environment with the Runtime Manager 8. Implementing Persistence and Transactions 9. Integration with Other Knowledge Definitions 10. Integrating KIE Workbench with External Systems The UberFire Framework Index

What is a rule?


The first thing we need to define in a clear manner before proceeding is what rules are. A rule, from the rule engine's perspective, is a constraint within a particular domain that will evaluate to true or false. When specific components within the domain evaluate the constraint of a specific rule to be true, we say that the particular rule is activated. When activated rules are fired (an operation that is usually separated from the activation of a rule), a particular action—specified within the rule—will be taken. Depending on the syntax, a rule structure can vary from implementation to implementation. However, the general structure of a rule will always be similar to the following code:

rule "rule name"
/* optional rule attributes */
when 
     /* a specific set of constraints in our domain */
then
    /* a specific set of actions to be taken when 
       the constraints evaluate to true */
end

A single rule by itself doesn't provide much value to describe a complex decision...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime
Visually different images