Systems and/or methods for dynamically configuring and evaluating rules with dynamic and/or user inputs at runtime

1. A method of preparing a web application for execution, wherein an instance of the web application is executable using a client-side client device including at least one processor and a memory operably coupled thereto, the method comprising:

earmarking programmatic elements in the web application;

setting up a bootstrap hook for the web application such that, when the instance is started up, metadata associated with the earmarked programmatic elements in the web application is retrieved using a computer-executable retrieval service; and

creating a plurality of hooks in the web application to enable an evaluation service to be injected into operation of the instance of the web application, the evaluation service being programmed to cause dynamic evaluation, at the client-side client device, of one or more configured rules against input provided in connection with the operation of the instance of the web application, the rules being definable in relation to the earmarked programmatic elements using the retrieved metadata, the rules specifying behavior of the web application and being configured in accordance with the mode in which the web application is coded to operate, the rules being both dynamically configurable and dynamically reconfigurable while the instance of the web application is running and being dynamically effective thereafter in the evaluation without requiring redeployment of the web application, even if (re)configured while the instance of the web application is running;

wherein the operation of the instance of the web application is responsive to the evaluation; and

wherein the web application is coded to operate in one of a plurality of different modes, a first mode permitting central rule configuration while prohibiting client-side rule configuration, and a second mode permitting client-side rule configuration.

2. The method of claim 1 , wherein the rules are configured post-deployment and are further (re)configurable post-deployment.

3. The method of claim 1 , further comprising deploying the packaged web application to the client-side client device.

4. The method of claim 1 , wherein the metadata is stored on a persistent store external to web application.

5. The method of claim 4 , wherein the persistent store is shareable by plural different web applications.

6. The method of claim 5 , wherein the plural different web applications are interoperable with one another.

7. The method of claim 1 , wherein the input comprises a value from a database, function, and/or remote API call.

8. The method of claim 1 , wherein a web application context object is used as at least some of the input for the dynamic evaluation.

9. A non-transitory computer readable storage medium tangibly storing instruction that, when performed by a computing system, prepare a web application for execution, wherein an instance of the web application is executable using a client-side client device including at least one processor and a memory operably coupled thereto, the web application being prepared for execution by performing operations comprising:

earmarking programmatic elements in the web application;

setting up a bootstrap hook for the web application such that, when the instance is started up, metadata associated with the earmarked programmatic elements in the web application is retrieved using a computer-executable retrieval service; and

creating a plurality of hooks in the web application to enable an evaluation service to be injected into operation of the instance of the web application, the evaluation service being programmed to cause dynamic evaluation, at the client-side client device, of one or more configured rules against input provided in connection with the operation of the instance of the web application, the rules being definable in relation to the earmarked programmatic elements using the retrieved metadata, the rules specifying behavior of the web application and being configured in accordance with the mode in which the web application is coded to operate, the rules being both dynamically configurable and dynamically reconfigurable while the instance of the web application is running and being dynamically effective thereafter in the evaluation without requiring redeployment of the web application, even if (re)configured while the instance of the web application is running;

wherein the operation of the instance of the web application is responsive to the evaluation; and

wherein the web application is coded to operate in one of a plurality of different modes, a first mode permitting central rule configuration while prohibiting client-side rule configuration, and a second mode permitting client-side rule configuration.

10. The non-transitory computer readable storage medium of claim 9 , wherein the rules are configured post-deployment and are further (re)configurable post-deployment.

11. The non-transitory computer readable storage medium of claim 9 , wherein the packaged web application is deployable to the client-side client device.

12. The non-transitory computer readable storage medium of claim 9 , wherein the metadata is stored on a persistent store external to web application.

13. The non-transitory computer readable storage medium of claim 12 , wherein the persistent store is shareable by plural different web applications.

14. The non-transitory computer readable storage medium of claim 13 , wherein the plural different web applications are interoperable with one another.

15. The non-transitory computer readable storage medium of claim 9 , wherein the input comprises a value from a database, function, and/or remote API call.

16. The non-transitory computer readable storage medium of claim 9 , wherein a web application context object is used as at least some of the input for the dynamic evaluation.

17. A computing system, the system comprising:

an administrative user interface module; and

a client-side client device configured to execute an instance of a web application prepared for execution by at least having:

earmarked programmatic elements in the web application;

a bootstrap hook set up for the web application such that, when the instance is started up, metadata associated with the earmarked programmatic elements in the web application is retrieved using a computer-executable retrieval service; and

a plurality of hooks created in the web application to enable an evaluation service to be injected into operation of the instance of the web application, the evaluation service being programmed to cause dynamic evaluation, at the client-side client device, of one or more configured rules against input provided in connection with the operation of the instance of the web application, the rules being definable in relation to the earmarked programmatic elements using the retrieved metadata, the rules specifying behavior of the web application and being configured in accordance with the mode in which the web application is coded to operate, the rules being both dynamically configurable and dynamically reconfigurable while the instance of the web application is running and being dynamically effective thereafter in the evaluation without requiring redeployment of the web application, even if (re)configured while the instance of the web application is running;

wherein the operation of the instance of the web application is responsive to the evaluation; and

wherein the web application is coded to operate in one of a plurality of different modes, a first mode permitting central rule configuration while prohibiting client-side rule configuration, and a second mode permitting client-side rule configuration;

wherein the administrative user interface module is configured to enable rule (re)configuration; and

wherein the computer-executable retrieval service and the evaluation service are packaged with the instance of the web application.

18. The system of claim 17 , further comprising a persistent store, the persistent store storing the metadata for the web application.

19. The system of claim 17 , wherein the administrative user interface module is not accessible by the client-side client device.

20. The system of claim 17 , wherein the administrative user interface module is packaged with the instance of the web application and is accessible by an end user using the instance of the web application.

21. The system of claim 17 , wherein the client-side client device is configured to execute the instance of the web application using a browser stored thereon.