Business rules manager

• US 9,330,117 B2
• Filed: 06/03/2013
• Issued: 05/03/2016
• Est. Priority Date: 06/08/2012
• Status: Active Grant

• Current Assignee: [24]7.ai, Inc.
• Original Assignee: 24/7 Customer Incorporated
• Inventors: Nguyen, Patrick
• Primary Examiner(s): Perveen, Rehana
• Assistant Examiner(s): Skhoun, Hicham
• Application Number:
  US13/908,961
• Publication Number:
  US 20130332411A1
• Time in Patent Office: 1,065 Days
• Field of Search: 707/609
• US Class Current: 1/1
• CPC Class Codes: G06F 16/21 Design, administration or maintenance of databases
• CPC Class Codes: G06F 16/2282 Tablespace storage structures; Management thereof
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/067 Enterprise or organisation modelling

Abstract

An apparatus and method is provided for creating, updating, and deleting business rules with ease by use of a rule manager. Business rules are represented as tables that map a set of inputs to a set of outputs. Inputs are represented as enumerations with predefined allowable values. All possible unique combinations of values for a given set of inputs are automatically generated, and a business user can then set the outputs for each desired input value combination.

Claims

1. A computer implemented method for creating, updating, and deleting business rules, comprising:

a processor accepting a set of defined attributes, which represent a known state of an application session in which rules are evaluated, where each attribute is an enumeration with a set of enumerators;

said processor accepting a set of rules tables, each of which contains one or more of the defined attributes;

a rules manager automatically generating all possible unique combinations of values for a given set of attribute value;

for each rules table, said processor generating a set of tuples, where each tuple represents one or more respective attribute value combinations and where no two tuples represent the same attribute value combination;

for each rules table, said processor accepting a set of settings, where the setting is assigned a value for each tuple;

A runtime interface for setting outputs for each desired attribute value combination in real-time and with which an application sets each attribute to a value and

said rules manager providing the value of a setting requested by the application by using a rules table associated with the setting and looking up the setting value assigned to the tuple whose combination of enumerators matches the current value of the corresponding attributes.

2. The method of claim 1, said rules manager providing an administrative environment for creating, maintaining, and managing attributes, settings, and rules tables, and a runtime interface with which said rules tables look up and return setting values in real-time.

3. The method of claim 1, wherein said processor automatically generates for each rules table one or more tuples, each of which represents a unique combination of enumerators for the attributes present in the rules table, and which collectively represent all possible combinations of said enumerators for said attributes in the rules table.

4. The method of claim 3, further comprising:

removing from a rules table a combination of attribute values that are of no interest, wherein a subset of the possible attribute value combinations remain in the rules table.

5. The method of claim 1, wherein the value of a setting assigned to a tuple is independent from the setting value of any other tuple, such that the setting value of one tuple cannot override a setting value of another tuple.

6. The method of claim 1, wherein said processor determines a setting value from a rules table by finding a tuple that represents said combination of input values in effect at the time of the request.

7. The method of claim 3, said processor further providing:

a wild card entry for use as an attribute value in a tuple to indicate all possible enumerators for that attribute; and

an ordering of attributes in a rules table wherein when a tuple has a wildcard in one attribute, then all following attributes are also set to wild cards.

8. The method of claim 7, said wild card entry further comprising an operation for expanding a tuple with said wild card entry to a set of tuples, each of which contains a unique enumerator value of the expanded attribute.

9. The method of claim 7, said wild card entry further comprising a reverse operation for collapsing a set of tuples that are otherwise identical, except for an enumerator value of a given attribute in each tuple, into a single tuple that has a wild card entry for that attribute.

10. The method of claim 1, wherein every attribute has a default value, wherein when a business application does not explicitly set a value of an attribute during an application session, said attribute is considered to have a value equal to a default value.

11. The method of claim 1, wherein every attribute is set to an allowable value at each point during an application session.

12. The method of claim 1, wherein each setting is associated with only one rules table, wherein the rules table to use for a setting is automatically determined without a business application explicitly specifying the rules table to use.

13. The method of claim 1, further comprising:

said business rules manager configured for responding to a business application, when said business application calls upon said business rules manager, by evaluating settings (outcomes or output variables) for said business application.

14. The method of claim 1, wherein each possible value combination for an attribute is represented by one and only one tuple.

15. The method of claim 1, further comprising:

said rules manager recalculating said set of tuples for a rules table in response to any of addition, deletion, and modification of an attribute enumerator to ensure that all possible valid attribute value combinations are present, and that no invalid attribute value combinations are present, wherein invalid attribute value combinations are those that contain at least one attribute value that is not in its corresponding attribute'"'"'s set of enumerators.

16. The method of claim 1, further comprising:

said rules manager automatically updating all tables that contain an attribute when an enumerator is added to said attribute to ensure that all possible attribute value combinations are represented.

17. The method of claim 1, further comprising:

said rules manager automatically updating all tables that contain an attribute when an enumerator is removed from that attribute by deleting all tuples that include the removed enumerator.

18. The method of claim 1, further comprising:

said rules manager sorting or filtering rows in a rules table to present a combination of attribute values of interest to a business user.

19. The method of claim 1, wherein a business application has knowledge of said attributes and settings, but not of said tuples or rows within said rules table;

wherein updating and restructuring of said rules table by adding or

removing attributes and by moving settings from one rules table to another is performed independently of, and without impact on, said business application.

20. The method of claim 1, further comprising:

multiple versions of said rules table;

wherein multiple rules tables can be in use concurrently.

21. The method of claim 1, further comprising:

said rules manager capturing snapshots of the state of said rules table at a point in time, for later reinstatement.