Some years ago I lived in Germany, moving there without a word of the language but full of confidence and optimism that once fully immersed I would quickly be conversing like a local. It took me longer than I thought, but I started to make sense of what people were saying and could follow the general flow of conversation. Becoming a confident speaker was a totally different challenge though.
There’s a similar learning curve when you start out with rules, reading and debugging are one thing, but being able to confidently express yourself, to write your own rules, well that’s a bit like speaking a new language, and that takes more time.
Long before automated translation became the norm, everyone packed a phrase book with them when they travelled overseas. And over the years, we’ve written our own phrase books, intended for people who speak Java and need to know how to say the same thing in Cúram Express Rules (CER).
The idea is that these basic syntax examples can be used as the building blocks for what will become your final rules masterpiece. Just don’t forget to follow the CER best practices
The first cheat sheet is available now, and the others will follow at regular intervals.
- Conditional Logic – This covers the typical &&, ||, !, <=> operations plus if/else branching.For the XML for the example attributes used in the cheatsheet, see Conditional logic example attributes
- Coming Soon! Types and Operations – Covering the basic types supported by CER, including String, Date and Number as well as typical operations like concatenation, calculating periods between dates, and basic mathematical operations.
- Coming Soon! Lists – Whether you’re looking to sort lists, remove duplicates, or map from one list to another, this is the place to start.
- Coming Soon! Structural- The final cheat sheet covers what’s left, like creating rule classes dynamically, or calling out to Java code.
So you can easily find them, we will group all the cheatsheet links here.
The CER Cheatsheet team (Sarah McGlynn, Larissa Silvera and Andrew Thomason), want to hear from you. Join the discussion and let us know if they are helpful, any changes that would improve them, or examples from your own projects that you use to help developers get up to speed.