Abstract: Embodiments described herein are generally related to data analytics environments, and are particularly directed to systems and methods for providing a revision history for use with a data analytics environment. The system includes a computer that includes one or more processors and that provides access to the data analytics environment, a revision history handler application running at the data analytics environment, and a user interface running at a client device and being in operative communication with the revision history handler application. The revision history handler application is configured to store, in a workbook folder of an artifacts catalog of the data analytics environment, current workbook metadata relating to a current workbook, a plurality of previous workbook versions of the current workbook, and a plurality of previous workbook version metadata sets each being related to a corresponding one of a plurality of previous workbook versions of the current workbook.

Abstract: Embodiments can provide interactivity to one or more components (e.g., windows, dialog boxes, tool bar, etc.) in a visual analyzer application while blocking interactivity for other components displayed on a GUI of the application. A contribution mechanism can be leveraged where a broadcast message can be sent to various components displayed on the GUI of the application. The various components within the application can then indicate whether they would like to be kept interactive during a triggering event (e.g., upon selection of a certain component). Upon receiving the indication that the components would like to remain interactive, the application allows those components to remain interactive while preventing access to other components in the GUI.

Abstract: Embodiments can provide interactivity to one or more components (e.g., windows, dialog boxes, tool bar, etc.) in a visual analyzer application while blocking interactivity for other components displayed on a GUI of the application. A contribution mechanism can be leveraged where a broadcast message can be sent to various components displayed on the GUI of the application. The various components within the application can then indicate whether they would like to be kept interactive during a triggering event (e.g., upon selection of a certain component). Upon receiving the indication that the components would like to remain interactive, the application allows those components to remain interactive while preventing access to other components in the GUI.