Rule Repository
The rule repository contains all the rules that are applied to the incoming data feeds.
The repository is usually located on the same machine as
Falcon Expert.
Each rule author has a private workspace where they can access and modify rules before committing them to the repository. This prevents multiple users from overwriting each other's work, or inadvertently committing changes to the repository.
Editing a rule or ruleset comprises the following actions:
- Update
- Updating the rules and rulesets in your workspace ensures that you have the latest versions of the rules in the repository.
- Deploy
- Deploying sends the active, approved rules and rulesets from the repository to the Scoring Server for use on incoming data feeds. The Scoring Server does not automatically sync up to the repository; the repository must be specifically deployed in order to make rules available for production or test.
- Check Out
- Checking out an item locks it for editing so that other users cannot check it out from the repository, although they can still view the item. You can edit a rule or ruleset you have checked out, and save changes to your workspace. Other users cannot check out or edit the same item until you check it back in and they update their workspace.
- Edit
- You must be in edit mode before making any changes to a rule or ruleset. You can edit an item only after you have checked it out, and only if you have the proper authorization.
- Cancel Edit
- You can cancel editing for an item without checking it in, but once you cancel an edit, you must click Edit again to be able to make changes.
- Save
- Save stores your changes to the files in your personal workspace, but does not write them to the repository. You can save your changes, log off, and log back on later to continue editing the item. However, the saved changes will not be written to the repository, or be available for approval or deployment by other users, until you check in the changes. Save and Check In are separate operations.
- Check In
- Checking in a revised rule creates a new version of the rule in the repository. After you check in the rule, other users can see your changes once they do a workspace update from the repository.
- Approval Requested
- Sending your rule for approval displays the rule in the Activity list for those who have approval permission. The rule remains locked until it is approved or rejected.
- Approve Changes
- Approving changes made to a rule makes it eligible for deployment.
- Reject Changes
- Rejecting changes returns a rule back to an author for further work before requesting approval again.
- Cancel Check Out
- Checking in your changes unlocks the rule. However, if you do not want to commit changes, and no longer want to keep the lock, you can undo the check out. Your lock on the rule will be released without any changes being written to the repository.