MC Corporate LOS Basic Administration Training AxeBRE Business Rules Engine

[Virtual Presenter] MC Corporate LOS Basic Administration Training AxeBRE Business Rules Engine.

[Audio] Business Rules Engine – Overview Business Rules Engine (B-R-E--) is a low-code environment where business users can model author validate and publish business rules. B-R-E is a business rule management tool for accommodating a large amount of business rules in a manageable manner. The business administrator can configure the business rules using B-R-E and then integrate it into B-P-M if the rule is needed during the process. Alternatively he/she can integrate it into G-U-I if the rule is meant for use on the screen. To log into B-R-E the admin can use any web browser (Chrome Firefox Edge et cetera) to reach the login screen and use the username and password provided by the system administrator. AxeGUI Direct call Called for ACP AxeBRE AxeBPM.

[Audio] Business Rules Engine – Main Components Vocabulary: Are Business Terms and that are the building blocks to writing rules. It represents the data that is necessary to generate Rule result. Query: Used to request for or do actions on data from a database table or combination of tables. This component requires basic knowledge in SQL. Xpression: Is the expressions configured to write a statement or formula which returns a value depending upon the values provided as variables. Ruleset: The ruleset section enables the user to automate and combine different types of business policies or procedures in an organized way..

[Audio] Business Rules Engine Example The screenshot shows a Ruleset Composer which allows users to define edit and manage the rules. In the image we can see the following sections: Ruleset This section allows you to create a new rule or edit an existing rule. In the example the rule is named “Approval Process RB” that checks the allowed limit cap for a customer Source Items This section specifies the data elements that the rule applies to. Conditions This section defines the conditions that must be met for the rule to be triggered. Actions This section defines the actions that will be taken if the conditions are met. In the example if the condition is met the system will alert the user with the message “Requested limits are breached limit cap of the customer”.

[Audio] Business Rules Engine Rule Composer Menu Datasources & Vocabulary : These two sections enables you to define the data to be used while building your business logic Query: The query section enables you to request for or do actions on data or information from a database table or combination of tables. Ruleset: The ruleset section enables you to automate different types of business policy or procedure. Xpression: The Xpression section enables you to configure statement or formula which returns a value depending upon the values provided as variables. Bulk : The Bulk section enables you to submit sequences of multiple actions on Query result Scheduler : The Scheduler section enables you to schedule a bulk query at a specific date and time and it can be in an “Recurrence” manner Activity Log : The Activity Log section provides you with all the information about the queries and rulesets being run to help you diagnose problems Audit Trail : The Audit trails section enables you track all types of action processed on the different components Settings : The setting section enables you to adjusts different configurations to your preference.

[Audio] Business Rules Engine Datasource Under the Rule Composer the administrator can find the datasources component. This component allows the user to link the B-R-E with an existing database. Once it is linked the B-R-E can read update insert into the tables in the database To add a new datasource the user should do the following: Choose on “New Datasource” to create a new datasource Enter a name for the datasource Set “SQL Server Address” with IP Address of your database server Select the Authentication Type Insert Database server username and password Click on Test Connection If the connection is successful the B-R-E will display the list of databases under that server and the admin should select the target database.

[Audio] Business Rules Engine Vocabularies Vocabularies are the building blocks to create a rule in B-R-E as they will be used along the logical & mathematical operators to create a business logic. The below graph demonstrates the attributes of a Vocabulary: Vocabularies Name Type Source Description Number String Boolean Value Input Query Attribute Python Ruleset Table Date Java Is Nullable PMML Folder List of possible Values Value: a static value Input: value provided during execution (parameters) Query: The result of a configured query Ruleset: The result of a configured Ruleset Python: The result of a configured Python file Java: The result of a configured Java file PMML: The result of a configured P-M-M-L file.

[Audio] New Vocabulary Vocabulary Attributes < List of Vocabularies What are Vocabularies? In a business rule engine vocabularies are essentially collections of terms or variables that are used to define the conditions and actions of business rules. These terms are typically given a user-friendly name to improve the readability and maintainability of the rules. This image displays a list of vocabularies within a business rule engine. Each vocabulary term represents a variable that can be used to define the conditions and actions of business rules. Key elements displayed in the screenshot may include: Name: This column shows the user-friendly name assigned to each vocabulary term. Type: This column specifies the data type of the vocabulary term such as number string or date. This helps ensure the vocabulary term is used appropriately within the rules. (Optional) Description: to add a brief description for each vocabulary term. This provides additional context and improves clarity for users working with the rules. (Optional) Other Columns: additional columns with information like “is Nullable“ "Folder" (categorization for the vocabulary term) or custom attributes specific to the vocabulary..

[Audio] Business Rules Engine Queries A query is a request for or do actions on data or information from a database table or combination of tables. This data or action may be generated as results returned by Structured Query. Fetch Queries are characterized by Fetch type can have the following as a returned value: Scalar: If it only returns one value Combo: If it is designated for a Datasource of a Combobox Table: If it may return more than one row or column The user can create three type of queries Fetch Query: Enables user to read information from databases and elaborate data mappings calculation and interrogate data sources. Add Row Query: Enables user to INSERT new records in the database’s tables. Amend Query: Enables user to modify the existing data in the tables and specifies which record(s) that should be UPDATED..

[Audio] New Query Fetch Query Composer < List of Queries What are Queries in a Business Rule Engine? In a business rule engine queries are used to retrieve update or insert data from a database that is required to evaluate the conditions and do actions of business rules. These queries can be used to: Fetch Data: This is the most common type of query and it retrieves data that is used to evaluate the conditions of a rule. For instance a rule might require fetching customer data to determine if a customer is eligible for a loan. Insert Data: In some cases a business rule might need to insert new data into a database. For example a rule might create a new account number when a customer signs the credit contract. Update Data: Business rules can also update existing data in a database. For example a rule might update a customer's account status after a successful repayment. The screenshot you provided shows an example of a Fetch Query. This type of query retrieves data from a database based on specific criteria. Here are some of the key elements of the screenshot: Name: This field specifies a name for the query which helps to identify its purpose. In the example the query is named “SME_GetApplicationType”. Distinct: This option specifies whether to eliminate duplicate records from the query results. Group By: This option allows you to group the results of the query based on one or more columns. => The query can be generated by the B-R-E for the user to checks it further if he/she wants to further verify the query.

[Audio] Business Rules Engine Fetch Queries Composer Composer Details Fetch Section Where Section Toolbox Composer Actions Order By Section Top Section Top Section entered value is the number of records to return. Distinct Checkbox Only distinct (different) values are selected when “Distinct” is checked Group by Checkbox Rows that have the same values are grouped into summary rows when “Group by” are checked.

[Audio] Business Rules Engine Expression The Xpression section enables the user to configure statement or formula which returns a value depending upon the values provided as variables. Access the Xpression section from the Rule Composer menu Manage the expressions under the Xpression section: Search for an Expression Filter Expressions Delete existing Expressions Refresh Expressions list Add a new Expressions Expand Expressions list.

[Audio] Mathematics Xpression section is a Simple Editor to edit expression and write expression with auto completion behavior in which the user is able to use created vocabs and different categories of function. To use a published vocabulary in an expression the following steps should be respected: Write “Vocab.” Click on “Ctrl plus Scape” buttons Once the mouse is over a vocabulary a tooltip containing the vocabulary source will be displayed Click on the desired vocabulary from the list of available vocabularies Add vocabulary inputs if needed after clicking on it.

[Audio] Business Rules Engine Ruleset The ruleset section empowers users to automate various business policies or procedures effectively. It encompasses five distinct types of rulesets designed to cater to different operational needs and requirements. Generic A ruleset aiming at returning an output and can be used for different purposes such as inserts updates et cetera Custom Error Handling (C-E-H--) A ruleset aiming at the generation of a blocking/warning message following certain conditions Pricing Condition Defines the pricing rules that apply based on set conditions. Start Workflow Defines the rules to be applied before starting a workflow based on set conditions. Accounting Schema Allow the user to create rulesets dedicated to generate accounting entries as ruleset actions..

[Audio] Toolbox for building a rule The rule List of Rulesets Action to be done if the condition is true In a business rule engine the ruleset is a set of actions (specific tasks) that are performed when the conditions of a rule are met. These actions can be used to automate a wide variety of tasks such as but not limited to : Updating data in a database: For instance a rule might update a customer's account balance after a repayment is received. Sending notifications: A business rule could trigger an email notification to the Relationship manage when the client’s loan is approved. Custom Error Handling (C-E-H--): Rules can be used to block or alert the user if there is a mistake/error/unallowed policy. For example the B-R-E might block the user if the customer exceeds the allowed limit.

[Audio] Message Action CEH Ruleset Each Rule in the Ruleset has two main blocks: Condition: The user can use Predicates and Vocabularies to set the different conditions that correspond to the rule. In addition it is possible to configure multiple conditions under the “Conditions” section. Action: In order to build the action of the rule the user can use one of the actions under the list of available action which depends on the created type of the ruleset. Assert Action Start Workflow Ruleset List of Actions Add Row Generic Ruleset Amend Pricing Ruleset Batch The execution mode of Ruleset’s actions can be synchronous or asynchronous to each action. Accounting Schema Pricing Action.

[Audio] Thank You. A black background with blue and orange text Description automatically generated with low confidence.