...

1. An editor. There are KRL plugins for many popular editors
2. A Github account
3. An account on a KRE instance. The easiest way to do this is to use the Kynetx hosted instance of KRE. 

Creating a Pico

Image Added

Writing KRL

Do the following:

1. Create a git repo for your KRL rulesets and put it on Github. You can create a different repo for each ruleset if you like or create one repo and put multiple rulesets in it. 

2. Create  file in your ruleset repo called hello.krl and put the following in it:

   Code Block
   theme Confluence language javascript
   ruleset hello_world { meta { name "Hello World" description << A first ruleset for the Quickstart >> author "Phil Windley" logging on sharing on provides hello } global { hello = function(obj) { msg = "Hello " + obj msg }; } rule hello_world is active { select when echo hello send_directive("say") with something = "Hello World"; } }

3. Use one of the methods in Tips for Developers to validate (parse) your ruleset.

   Info
   Installing and using the KRL command line parser can be a real time saver if you're going to be writing several rulesets. Checking in and trying to execute rulesets that don't parse is one of the primary frustrations of beginning KRL developers.

4. Check your ruleset into Github. 

Registering Your Ruleset

Getting your parsed ruleset into Github is a great first step, but the rules engine doesn't know anything about it. Registering a ruleset gives it a Ruleset ID (RID) in the rules engine so that other users can install and run it. 

To register the ruleset, we will use the KRL Developer Tools at Pico Labs. 

When you click on the "Register Rulesets" menu item in the KRl KRL Developer tools, you will see this page that shows all your registered rulesets and a menu item to register a new ruleset:

When you click on "Register a new ruleset" you'll see this page:

...

Clicking on the ruleset you just installed will show you information about it (and give you a button for uninstalling it if you choose):

Flushing the Ruleset

When the rules engine reads a ruleset from the URL where it is located, the rules engine parses it, optimizes it, and caches the result. The next time the ruleset engine needs the ruleset it uses the cached copy, saving time in getting, parsing, and optimizing. 

...

Testing the Ruleset

Debugging the Ruleset