Abstract: Each of a plurality of wire web components predicted to be included in a graphical user interface (GUI) for presentation at a client machine. Each data object instance may be associated with a respective data object instance identifier and a respective one or more data object fields. A wire web component graph that includes a plurality of nodes may be constructed. A node may correspond to a wire web component, a data object field, or an application procedure interface (API). One or more of the data values may be retrieved from the respective APIs based on the wire web component graph. A GUI message including the retrieved data values and the wire web component graph may be transmitted to the client machine.

Abstract: Systems and methods for performing user interface (UI) test automation may include receiving a document object model (DOM) associated with a web application, the web application having one or more web pages; generating a generic object representation of the web application based on the DOM using a page object model; generating a page object based on the generic page object representation in a first programing language; and storing the page object in the first programming language in a database to be accessed by test scripts associated with a UI test automation of the web application.

Abstract: Systems and methods for performing user interface (UI) test automation may include receiving a document object model (DOM) associated with a web application, the web application having one or more web pages; generating a generic object representation of the web application based on the DOM using a page object model; generating a page object based on the generic page object representation in a first programing language; and storing the page object in the first programming language in a database to be accessed by test scripts associated with a UI test automation of the web application.

Abstract: Each of a plurality of wire web components predicted to be included in a graphical user interface (GUI) for presentation at a client machine. Each data object instance may be associated with a respective data object instance identifier and a respective one or more data object fields. A wire web component graph that includes a plurality of nodes may be constructed. A node may correspond to a wire web component, a data object field, or an application procedure interface (API). One or more of the data values may be retrieved from the respective APIs based on the wire web component graph. A GUI message including the retrieved data values and the wire web component graph may be transmitted to the client machine.

Abstract: Each of a plurality of wire web components predicted to be included in a graphical user interface (GUI) for presentation at a client machine. Each data object instance may be associated with a respective data object instance identifier and a respective one or more data object fields. A wire web component graph that includes a plurality of nodes may be constructed. A node may correspond to a wire web component, a data object field, or an application procedure interface (API). One or more of the data values may be retrieved from the respective APIs based on the wire web component graph. A GUI message including the retrieved data values and the wire web component graph may be transmitted to the client machine.

Abstract: A wire web component may be included in a graphical user interface (GUI) being presented on a display device. The wire web component may include one or more data fields that are each associated with a respective data value. A designated node representing the designated wire web component may be removed from a wire web component graph that includes a plurality of nodes. Each of the data fields may be associated with a respective API in the wire web component graph. A document object model (DOM) tree stored in memory may be updated to remove the designated wire web component. The GUI presented on the display device may be updated based on the updated DOM tree.

Abstract: Disclosed are some implementations of systems, apparatus, methods and computer program products for encrypting and securely storing session data during a browser session using a session-based cryptographic key. The session data may be decrypted during the browser session or other browser sessions using the session-based cryptographic key or other backwards compatible session-based cryptographic keys. In addition, session-based cryptographic keys may be shared among browser sessions to enable encrypted session data to be decrypted across page refreshes and browser tabs.

Abstract: Disclosed are examples of systems, apparatus, methods and computer program products for providing a security model for component-based web applications. Documents for a web-based application are received, with the application containing custom components and Application Programming Interface (API) components. A Document Object Model (DOM) is processed corresponding to the web-based application, with the custom and API components modeled in hierarchical form. For each custom component, a key is assigned in accordance with the rules of capability security, accessible custom components are identified for which the custom component can provide the assigned key, a virtual DOM is generated for the custom component with the component and identified accessible custom components being modeled in hierarchical form, and the custom component is prohibited access to all inaccessible custom components.

Abstract: A wire web component graph that includes a plurality of nodes may be accessed to identify one or more application procedure interfaces (APIs) through which to update one or more data values included in a designated wire web component in a graphical user interface (GUI) being presented on a display device. Each of the data values may correspond to a respective data field represented in the wire web component graph, and each data field may be associated with a respective API in the wire web component graph. The graphical user interface may be updated based on one or more updated data values determined by communicating with the identified APIs over a network and via a communications interface.

Abstract: A wire web component graph may be constructed based on a request to provide a graphical user interface (GUI) at a client machine. The wire web component graph may include a plurality of nodes. Each of the nodes may correspond to a wire web component included in the GUI, a data value, or an application procedure interface (API). One or more API messages may be transmitted to retrieve the data values from the respective APIs based on the designated wire web component graph. A GUI including one or more of the retrieved data values may be displayed on a display device at the client machine.

Abstract: Each of a plurality of wire web components predicted to be included in a graphical user interface (GUI) for presentation at a client machine. Each data object instance may be associated with a respective data object instance identifier and a respective one or more data object fields. A wire web component graph that includes a plurality of nodes may be constructed. A node may correspond to a wire web component, a data object field, or an application procedure interface (API). One or more of the data values may be retrieved from the respective APIs based on the wire web component graph.

Abstract: A wire web component graph may be constructed based on a request to provide a graphical user interface (GUI) at a client machine. The wire web component graph may include a plurality of nodes. Each of the nodes may correspond to a wire web component included in the GUI, a data value, or an application procedure interface (API). One or more API messages may be transmitted to retrieve the data values from the respective APIs based on the designated wire web component graph. A GUI including one or more of the retrieved data values may be displayed on a display device at the client machine.

Abstract: A wire web component graph that includes a plurality of nodes may be accessed to identify one or more application procedure interfaces (APIs) through which to update one or more data values included in a designated wire web component in a graphical user interface (GUI) being presented on a display device. Each of the data values may correspond to a respective data field represented in the wire web component graph, and each data field may be associated with a respective API in the wire web component graph. The graphical user interface may be updated based on one or more updated data values determined by communicating with the identified APIs over a network and via a communications interface.

Abstract: A wire web component may be included in a graphical user interface (GUI) being presented on a display device. The wire web component may include one or more data fields that are each associated with a respective data value. A designated node representing the designated wire web component may be removed from a wire web component graph that includes a plurality of nodes. Each of the data fields may be associated with a respective API in the wire web component graph. A document object model (DOM) tree stored in memory may be updated to remove the designated wire web component. The GUI presented on the display device may be updated based on the updated DOM tree.

Abstract: Disclosed are some implementations of systems, apparatus, methods and computer program products for encrypting and securely storing session data during a browser session using a session-based cryptographic key. The session data may be decrypted during the browser session or other browser sessions using the session-based cryptographic key or other backwards compatible session-based cryptographic keys. In addition, session-based cryptographic keys may be shared among browser sessions to enable encrypted session data to be decrypted across page refreshes and browser tabs.

Abstract: Disclosed are some implementations of systems, apparatus, methods and computer program products for encrypting and securely storing session data during a browser session using a session-based cryptographic key. The session data may be decrypted during the browser session or other browser sessions using the session-based cryptographic key or other backwards compatible session-based cryptographic keys. In addition, session-based cryptographic keys may be shared among browser sessions to enable encrypted session data to be decrypted across page refreshes and browser tabs.

Abstract: Disclosed are examples of systems, apparatus, methods and computer program products for providing a security model for component-based web applications. Documents for a web-based application are received, with the application containing custom components and Application Programming Interface (API) components. A Document Object Model (DOM) is processed corresponding to the web-based application, with the custom and API components modeled in hierarchical form. For each custom component, a key is assigned in accordance with the rules of capability security, accessible custom components are identified for which the custom component can provide the assigned key, a virtual DOM is generated for the custom component with the component and identified accessible custom components being modeled in hierarchical form, and the custom component is prohibited access to all inaccessible custom components.

Abstract: Disclosed are examples of systems, apparatus, methods and computer program products for providing a security model for component-based web applications. Documents for a web-based application are received, with the application containing custom components and Application Programming Interface (API) components. A Document Object Model (DOM) is processed corresponding to the web-based application, with the custom and API components modeled in hierarchical form. For each custom component, a key is assigned in accordance with the rules of capability security, accessible custom components are identified for which the custom component can provide the assigned key, a virtual DOM is generated for the custom component with the component and identified accessible custom components being modeled in hierarchical form, and the custom component is prohibited access to all inaccessible custom components.

Abstract: Disclosed are examples of systems, apparatus, methods and computer program products for providing a security model for component-based web applications. Documents for a web-based application are received, with the application containing custom components and Application Programming Interface (API) components. A Document Object Model (DOM) is processed corresponding to the web-based application, with the components modeled in hierarchical form. Each API component is assigned to a system mode setting, where the system mode setting is configured to provide the API component access to all of the components in the application. One or more secure documents are generated for each custom component, with each secure document containing a key in accordance with the rules of capability security. Each custom component is then assigned to a user mode setting, where the user mode setting is configured to provide custom components access to other components in the application for which a key can be provided.

Abstract: Disclosed are examples of systems, apparatus, methods and computer program products for providing a security model for component-based web applications. Documents for a web-based application are received, with the application containing custom components and Application Programming Interface (API) components. A Document Object Model (DOM) is processed corresponding to the web-based application, with the custom and API components modeled in hierarchical form. For each custom component, a key is assigned in accordance with the rules of capability security, accessible custom components are identified for which the custom component can provide the assigned key, a virtual DOM is generated for the custom component with the component and identified accessible custom components being modeled in hierarchical form, and the custom component is prohibited access to all inaccessible custom components.