Business rules management system
Computer systems are used to facilitate the sale of mortgages into the secondary market. For example, the computer systems are used to facilitate the administration of loan delivery and other business rules across multiple customer-facing applications. The computer systems provide a shared service for customer-facing applications to integrate with a centralized business rules engine. The computer systems enable the integrated applications to request specific groups or categories of business rules to be executed by the centralized business rules engine. The computer systems request execution of stored business rules based on a loan, format the results, and provide feedback to the calling applications based on the results.
1. A method performed by a business rules orchestrator computing system comprising a processor, memory and computer-executable instructions stored thereon, the computer-executable instructions, when executed by the processor, structured to perform operations comprising:
generating, by an administration circuit of the business rules orchestrator computing system, a business rule comprising a multiple-selection computer application identifier property, the multiple-selection computer application identifier property structured to hold a plurality of computer application identifiers such that the business rule is made applicable across a plurality of customer-facing computer applications based on the plurality of computer application identifiers, the business rule being deployable without modifying source code of the plurality of the customer-facing computer applications, wherein being deployable without modifying source code decreases production update time for at least one of a rule message, a severity, and an override, and the business rule comprising a first instance of metadata related to the business rule and stored on a data storage media associated with the business rules orchestrator computing system;
providing, by a user interface circuit of the business rules orchestrator computing system, an interface to a computing device operated by a user of the system, wherein the interface is structured to display the business rule;
receiving, by the administration circuit of the business rules orchestrator computing system, a request from the user via the interface, the request including a modification of the business rule, wherein the modification comprises a rule logic override related to modifying a user-selected subset of customer-facing computer applications from the plurality of customer-facing computer applications; and
applying, by the administration circuit, the modification to the business rule for the user-selected subset of customer-facing computer applications based on the request, comprising the operations of:
generating a second instance of metadata related to the business rule, wherein the second instance of metadata is associated with the rule logic override that modifies the user-selected subset of customer-facing computer applications; and
storing the second instance of metadata on the data storage media;
wherein both the first instance of metadata and the second instance of metadata remain selectable for execution of either the business rule or the modification via the user interface circuit, wherein the metadata is searchable by filtering on a desired customer-facing computer application.
2. The method of claim 1 , further comprising:
assigning an approver to the business rule based on a message received from an administrator via the interface; and
receiving approval from the approver via the interface.
3. The method of claim 2 , further comprising, upon receiving the request from the user:
determining the approver based on the business rule; and
generating an approval request at the interface based on the approver.
4. The method of claim 2 , wherein the approver includes two or more associated persons.
5. The method of claim 1 , wherein the request from the user includes an expiration date associated with the modification.
6. The method of claim 5 , further comprising deactivating the modification upon the expiration date.
7. The method of claim 1 , wherein the business rule is associated with a feedback message, and wherein applying the modification includes suppressing the feedback message.
8. A business rules orchestrator computing system, comprising a processor, memory, and a user interface circuit comprising computer-executable instructions stored in the memory, the computer-executable instructions, when executed by the processor, structured to perform the following operations:
generate a business rule comprising a multiple-selection computer application identifier property, the multiple-selection computer application identifier property structured to hold a plurality of computer application identifiers such that the business rule is made applicable across a plurality of customer-facing computer applications based on the plurality of computer application identifiers, the business rule being deployable without modifying source code of the plurality of the customer-facing computer applications, wherein being deployable without modifying source code decreases production update time for at least one of a rule message, a severity, and an override, and the business rule comprising a first instance of metadata related to the business rule and stored on a data storage media associated with the business rules orchestrator computing system;
provide an interface to a computing device operated by a user of the system, wherein the interface is structured to display the business rule
receive a request from the user via the interface, the request including a modification of the business rule, wherein the modification comprises a rule logic override related to modifying a user-selected subset of customer-facing computer applications from the plurality of customer-facing computer applications; and
a rules management circuit structured to apply the modification, comprising circuitry structured to:
generate a second instance of metadata related to the business rule, wherein the second instance of metadata is associated with the rule logic override that modifies the user-selected subset of customer-facing computer applications; and
store the second instance of metadata on the data storage media;
wherein both the first instance of metadata and the second instance of metadata are selectable for execution of either the business rule or the modification via the user interface circuit, wherein the metadata is searchable by filtering on a desired customer-facing computer application.
9. The system of claim 8 , wherein the rules management circuit is further structured to assign an approver to the business rule based on a message received from an administrator via the interface, and wherein the user interface circuit is further structured to receive approval from the approver via the interface.
10. The system of claim 9 , wherein the rules management circuit is structured to, upon receipt of the request from the user:
determine the approver based on the business rule; and
generate an approval request at the interface based on the approver.
11. The system of claim 9 , wherein the rules management circuit is structured to assign two or more associated persons as the approver.
12. The system of claim 8 , wherein the request from the user includes an expiration date associated with the modification.
13. The system of claim 12 , wherein the rules management circuit is structured to deactivate the modification upon the expiration date.
14. The system of claim 8 , wherein the business rule is associated with a feedback message, and wherein applying the modification includes suppressing the feedback message.
15. The method of claim 1 , wherein the business rule is associated with an external message intended for a customer.
16. The method of claim 15 , wherein the modification modifies at least one of a text, a trigger date, and a severity associated with the external message.
17. The method of claim 15 , wherein the modification relates to an exception associated with the business rule, further comprising suppressing sending of the external message to the customer based on the exception.
18. The method of claim 17 , wherein the exception is related to at least one of a seller and a loan.