Skip to content
110 Springfield Ave. | Berkeley Heights, NJ 07922
+1 (908) 464-5402
Back to blog

The Complete JDE Orchestrator Guide Part 3: Rules

Rules allow you to go far beyond the simple actions available in the other subcomponents and add more logic to your orchestrations. This is the secret to being able to carry out complex tasks. With rules, you create a pathway through your orchestration, making the appropriate decision at each fork in the path.

Building a Rule in Orchestrator Studio

  1. Inside the rule, you must define the match type. This could be Match All or Match Any. In a scenario using match all, the logic is AND. In a scenario using match any, the logic is OR. 
  2. In Value One in the rule, you must insert an input parameter. This is the variable you are passing in, the logical starting point for the rule. 
  3. Next, you choose an operator (the available options are based on the string type in the first field on the far left). These might include greater than, less than, equal to, starts with, is between, contains, is in list, etc.
  4. For value 2, you can enter another variable or a literal value that you are comparing it to. The “literal” toggle button is what allows you to choose if the input value is a variable or a literal value. 

Rules Overview 1

Note: In the above example, the Search Type could only be a ‘C’ OR a ‘T’. It could never be both values at the same time, so we use a “Match Any” Match Type.

Complete Guide to JDE Orchestrator CTA

Working with Logic Inside a Rule 

In our Add Address example, the rules component allows you to evaluate a statement and decide if it’s true. For example, you can use a simple rule to check a SearchType field and determine whether it is T or C. 

If equal to either, it evaluates as true and takes the top “true” path and continues through the rest of the steps. If none are equal to C or T, it evaluates as “false” and takes the bottom path (which results in no further action in this particular example).

Rules can be embedded into a path one after another to create complex decision trees, sifting through to get the data needed for the specific scenario you have in mind. The path can also include form requests and other subcomponents to retrieve and transform additional data along the way.

Rules Overview 2
Scripts to Create Complex Rules

You do have limitations using the basic functionality available in rules. You only have the option of Match Any or Match All. Sometimes, decisions aren’t that simple. For example, you might want to have a rule that checks for condition A & B or condition A & C. In those situations, you can use Groovy script to add this logical capability. With Groovy, you can write a script of actual code and put in any logic you want to evaluate the rule and whether it goes true or false. With custom scripting, you can test for virtually any scenario imaginable using any combination of values. 

Next up, we’ll talk about Cross References--the single most underused Orchestrator component. Prepare to learn about a powerful way to make JDE and outside applications work together.

See Previous Part See Next Part

Leave a Comment

Back to Blog

Subscribe To ACBM Solutions Blog