The document provides an overview of the key features and benefits of a Business Rules Management System (BRMS). It discusses what a BRMS is, its main components like Guvnor, assets, rules, processes, and how it can be used with Eclipse. A BRMS provides a centralized repository for business logic, enables separation of logic and data, and allows non-technical users to define rules through a graphical interface.
62. A decision table at runtime is transformed in a series of DRL rules
63.
64. A scenario is made by a given section (list of facts and its initial state) and an expect section
65. What we can “assert” in a expect section? - Rule Validate that a certain rule fired. - Fact value Validate fact values for a fact created in the Given section. -Any fact that matches Validate that there is at least one fact in the knowledge base with the specified field values.
102. With a build every assets inside the package is validated
103. Status and Categories can be used to select only specific assets to include inside a snapshot (Use selector) (e.g. create a snaposhot only with assets belonging to category “Fraud” and with Status “Completed”)
104. A snapshot will be published inside the repository and accessible via a URL
105.
106.
107. Assets can be edited in Eclipse and committed to BRMS (complete roundtrip)
108. Eclipse gives the capability to compare different version of the same asset