Abstract: A method may include generating a first user interface for providing, to a client, a first selection of inputs for attributes of a rule scenario for defining a rule. The rule may be applied to modify a data processing functionality of the application. Parameters of the rule may be determined based on the rule scenario and a first input from the first selection of inputs being selected via the first user interface. The parameters of the rule may correspond to data objects affected by the application of the rule. A second user interface for providing, to the client, a second selection of inputs for defining a condition of the rule may be generated. The condition of the rule may evaluate the parameters of the rule. The rule may be generated based on a second input from the second selection of inputs being selected via the second user interface.

Abstract: A method may include generating a first user interface for providing, to a client, a first selection of inputs for attributes of a rule scenario for defining a rule. The rule may be applied to modify a data processing functionality of the application. Parameters of the rule may be determined based on the rule scenario and a first input from the first selection of inputs being selected via the first user interface. The parameters of the rule may correspond to data objects affected by the application of the rule. A second user interface for providing, to the client, a second selection of inputs for defining a condition of the rule may be generated. The condition of the rule may evaluate the parameters of the rule. The rule may be generated based on a second input from the second selection of inputs being selected via the second user interface.

Abstract: A rules engine is provided that can work with various heterogeneous calling applications. Such a rules engine can be part of a larger framework which, for example, can provide calibration alerts and the like when certain rule conditions are met. In some implementations, the framework can allow for the identification and mitigation of bias against certain employees and/or classes of employees within a larger organization.

Abstract: A target application loads target application's user interface (UI) after an initial preoperational task is completed. A task for visualizing a progress status for the target application is delegated to a source application that is used for launching the target application in a new window. The source application creates a shared object and assigns a unique identifier (ID) to the shared object. The unique ID of the shared object is passed to the target application, when the target application is launched from the source application. The shared object is accessed by the target application during the performance of the initial preoperational task. The target application stores progress status of the initial preoperational task in the shared object. The source application monitors the progress status stored in the shared object and presents it continuously on source application's user interface.

Abstract: A target application loads target application's user interface (UI) after an initial preoperational task is completed. A task for visualizing a progress status for the target application is delegated to a source application that is used for launching the target application in a new window. The source application creates a shared object and assigns a unique identifier (ID) to the shared object. The unique ID of the shared object is passed to the target application, when the target application is launched from the source application. The shared object is accessed by the target application during the performance of the initial preoperational task. The target application stores progress status of the initial preoperational task in the shared object. The source application monitors the progress status stored in the shared object and presents it continuously on source application's user interface.