Abstract: The present disclosure provides methods, systems, and computer products for providing state-based revisions in a document collaboration system. In some aspects, a plurality of users may be simultaneously editing the same document on their respective computing devices. The document may comprise a plurality of editable objects having unique objects identifiers. In such aspects, when a user edits an object in a local version of the document, a state-based revision (“SBR”) record is created. The SBR is populated with information such as, information describing the type of object being edited, a descriptor that uniquely identifies the specific instance of the object being edited, a collection of common references that can be adjusted by the document collaboration engine and an opaque binary stream comprising the modified state of the edited object. The SBR record is then transmitted to one or more additional devices.

Abstract: The present disclosure provides methods, systems, and computer products for providing state-based revisions in a document collaboration system. In some aspects, a plurality of users may be simultaneously editing the same document on their respective computing devices. The document may comprise a plurality of editable objects having unique objects identifiers. In such aspects, when a user edits an object in a local version of the document, a state-based revision (“SBR”) record is created. The SBR is populated with information such as, information describing the type of object being edited, a descriptor that uniquely identifies the specific instance of the object being edited, a collection of common references that can be adjusted by the document collaboration engine and an opaque binary stream comprising the modified state of the edited object. The SBR record is then transmitted to one or more additional devices.

Abstract: The present disclosure provides methods, systems, and computer products for providing state-based revisions in a document collaboration system. In some aspects, a plurality of users may be simultaneously editing the same document on their respective computing devices. The document may comprise a plurality of editable objects having unique objects identifiers. In such aspects, when a user edits an object in a local version of the document, a state-based revision (“SBR”) record is created. The SBR is populated with information such as, information describing the type of object being edited, a descriptor that uniquely identifies the specific instance of the object being edited, a collection of common references that can be adjusted by the document collaboration engine and an opaque binary stream comprising the modified state of the edited object. The SBR record is then transmitted to one or more additional devices.

Abstract: Slicers are configured to filter tabular data arranged in columns. A user may use the slicers to filter tabular data from a client application and/or a server based application/service. Slicers may be created for one or more columns and for all/portion of the tabular data within a column. Selection of a slicer element filters the associated tabular data and updates a display of the other slicers. Interaction with the slicers may also update other user interface controls that filter the tabular data (e.g. selecting a slicer element changes a value of a filtering setting in a drop down menu and/or selecting the filtering setting in the drop down menu changes a state of a slicer element). A slicer element may be associated with other objects in the spreadsheet and/or included within one or more functions of a spreadsheet.

Abstract: Slicers are configured to filter tabular data arranged in columns. A user may use the slicers to filter tabular data from a client application and/or a server based application/service. Slicers may be created for one or more columns and for all/portion of the tabular data within a column. Selection of a slicer element filters the associated tabular data and updates a display of the other slicers. Interaction with the slicers may also update other user interface controls that filter the tabular data (e.g. selecting a slicer element changes a value of a filtering setting in a drop down menu and/or selecting the filtering setting in the drop down menu changes a state of a slicer element). A slicer element may be associated with other objects in the spreadsheet and/or included within one or more functions of a spreadsheet.

Abstract: A database tier maintains and provides access to a database. An application tier receives and responds to requests for a form. The form includes data defining a first UI control for displaying a first value from the database and a second UI control for displaying a second value from the database that is dependent upon the first value. A client tier renders the form to show the first value in the first UI control and to show the second value in the second UI control. The client tier also detects a modification to the first value and causes an updated second value to be generated in response to detecting the modification to the first value. The updated second value is displayed by way of the second UI control. The updated second value is generated at the client tier, the application tier, the database tier, or at a combined application/database tier.

Abstract: Slicers are configured to filter tabular data arranged in columns. A user may use the slicers to filter tabular data from a client application and/or a server based application/service. Slicers may be created for one or more columns and for all/portion of the tabular data within a column. Selection of a slicer element filters the associated tabular data and updates a display of the other slicers. Interaction with the slicers may also update other user interface controls that filter the tabular data (e.g. selecting a slicer element changes a value of a filtering setting in a drop down menu and/or selecting the filtering setting in the drop down menu changes a state of a slicer element). A slicer element may be associated with other objects in the spreadsheet and/or included within one or more functions of a spreadsheet.

Abstract: The present disclosure provides methods, systems, and computer products for providing state-based revisions in a document collaboration system. In some aspects, a plurality of users may be simultaneously editing the same document on their respective computing devices. The document may comprise a plurality of editable objects having unique objects identifiers. In such aspects, when a user edits an object in a local version of the document, a state-based revision (“SBR”) record is created. The SBR is populated with information such as, information describing the type of object being edited, a descriptor that uniquely identifies the specific instance of the object being edited, a collection of common references that can be adjusted by the document collaboration engine and an opaque binary stream comprising the modified state of the edited object. The SBR record is then transmitted to one or more additional devices.

Abstract: Systems, methods, and software are disclosed herein for implementing enhanced testing for application services. In an implementation, revisions are made to a document in the context of an application service. The revisions invoke responses by at least a subset of the components of the service. At least some of the same revisions may then be applied to another instance of the document subject to various test components. Responses by the test components are invoked by the revisions, which may then be compared against the other responses to evaluate the test components.

Abstract: Embodiments are disclosed for a system to manage changes to a shared electronic document. In embodiments, a client side method is used to manage changes to a shared electronic document. The method includes receiving a change to a locally stored rendition of a shared electronic document, and updating a change history. In embodiments, the change history captures the change made to the locally stored rendition of a shared electronic document. The method also includes sending information regarding the change to a server, receiving information regarding a master copy of the shared electronic document, and determining based on the received information the change was accepted by the server and applied to the master copy of the shared electronic document.

Abstract: Slicers are configured to filter tabular data arranged in columns. A user may use the slicers to filter tabular data from a client application and/or a server based application/service. Slicers may be created for one or more columns and for all/portion of the tabular data within a column. Selection of a slicer element filters the associated tabular data and updates a display of the other slicers. Interaction with the slicers may also update other user interface controls that filter the tabular data (e.g. selecting a slicer element changes a value of a filtering setting in a drop down menu and/or selecting the filtering setting in the drop down menu changes a state of a slicer element). A slicer element may be associated with other objects in the spreadsheet and/or included within one or more functions of a spreadsheet.

Abstract: A database tier maintains and provides access to a database. An application tier receives and responds to requests for a form. The form includes data defining a first UI control for displaying a first value from the database and a second UI control for displaying a second value from the database that is dependent upon the first value. A client tier renders the form to show the first value in the first UI control and to show the second value in the second UI control. The client tier also detects a modification to the first value and causes an updated second value to be generated in response to detecting the modification to the first value. The updated second value is displayed by way of the second UI control. The updated second value is generated at the client tier, the application tier, the database tier, or at a combined application/database tier.

Abstract: A database tier maintains and provides access to a database. An application tier receives and responds to requests for a form. The form includes data defining a first UI control for displaying a first value from the database and a second UI control for displaying a second value from the database that is dependent upon the first value. A client tier renders the form to show the first value in the first UI control and to show the second value in the second UI control. The client tier also detects a modification to the first value and causes an updated second value to be generated in response to detecting the modification to the first value. The updated second value is displayed by way of the second UI control. The updated second value is generated at the client tier, the application tier, the database tier, or at a combined application/database tier.

Abstract: A database tier maintains and provides access to a database. An application tier receives and responds to requests for a form. The form includes data defining a first UI control for displaying a first value from the database and a second UI control for displaying a second value from the database that is dependent upon the first value. A client tier renders the form to show the first value in the first UI control and to show the second value in the second UI control. The client tier also detects a modification to the first value and causes an updated second value to be generated in response to detecting the modification to the first value. The updated second value is displayed by way of the second UI control. The updated second value is generated at the client tier, the application tier, the database tier, or at a combined application/database tier.

Abstract: User requested format alterations to interactive chart elements, including, but not limited to, legends, axes, gridlines, data labels, axes labels, error bars, and datapoints, whether they be represented as points, bars, pie wedges, etc., are persisted in spite of chart navigations, underlying data changes and/or format alterations. Interactive chart element format persistence is maintained by the association and storing of data identifying a format change on the data and index rule for the respective chart element.