Patent application number | Description | Published |
20080208874 | Handling multi-dimensional data including writeback data - Embodiments are provided to use metadata to provide readable and/or writeable regions of a multi-dimensional space. In an embodiment, metadata can be used to define readable and/or writeable regions of a multi-dimensional data store. The various embodiments also use relational and/or multi-dimensional representations to resolve and validate readable and/or writeable regions of a multi-dimensional space. Metadata can also be used to in conjunction with writeback operations. | 08-28-2008 |
20080208918 | Efficient data handling representations - Embodiments are provided to use metadata to provide readable and/or writeable regions of a multi-dimensional space. In an embodiment, metadata can be used to define readable and/or writeable regions of a multi-dimensional data store. The various embodiments also use relational and/or multi-dimensional representations to resolve and validate readable and/or writeable regions of a multi-dimensional space. Metadata can also be used to designate a number of writeable and/or readable regions of a relational and/or multi-dimensional representation. | 08-28-2008 |
20080209435 | Scalable workflow management system - A scalable workflow management system is provided that includes queues for storing work items to be processed. Work items may be placed into the queues by front-end services executing within the workflow management system. When a work item is placed on a queue, it remains on the queue until an appropriate back-end service is available to de-queue the work item, validate the de-queued work item, and process the de-queued work item. Separate queues are provided for storing normal work items, work items generated according to a time schedule, and work items generated by job launching services. The state of operation of the workflow management system may be controlled by an administrative console application. | 08-28-2008 |
20100125471 | FINANCIAL JOURNALS IN FINANCIAL MODELS OF PERFORMANCE SERVERS - Architecture that employs a journal assignment that can be created on demand when journal is created, and operates outside the business cycle. The assignment is routed to reviewers and approvers based on predefined company policy that users define. The assignment encloses a changelist of data changes created by the journal. The changelist is used for rendition and calculation for reviewers and approvers (in addition to the journal contributor) to view/verify and modify the data as if the data is already written into the model. At the time that other users access this model, the data is not present. At the end of the successful workflow chain the changelist is written into the model. If failed, the changelist will be used as that basis for correction or the user can discard the changelist. | 05-20-2010 |
20100125549 | MAINTAINING CLIENT DATA INTEGRITY IN A DISTRIBUTED ENVIRONMENT USING ASYNCHRONOUS DATA SUBMISSION - Data processing architecture where submitters can write data and/or metadata changes to a destination through an asynchronous interface. The architecture includes a ticketing system that issues a ticket (a unique identifier) to the submitter in response to receiving a changelist from the submitter. When the changes are successfully completed at the destination, the cached destination data can be re-downloaded to the submitter, and the changes cached in the submitter, discarded. Absent this capability, a user has to manually manage the cached changes and cached data. The architecture can be distributed in that multiple submitters can submit changelists. The destination provides data integrity by managing submissions to assist in ensuring data integrity across multiple submissions. Automatic changelist cleanup is provided on the submitter so that changelists do not impact performance, memory, and storage. | 05-20-2010 |
20120254104 | MAINTAINING CLIENT DATA INTEGRITY IN A DISTRIBUTED ENVIRONMENT USING ASYNCHRONOUS DATA SUBMISSION - Data processing architecture where submitters can write data and/or metadata changes to a destination through an asynchronous interface. The architecture includes a ticketing system that issues a ticket (a unique identifier) to the submitter in response to receiving a changelist from the submitter. When the changes are successfully completed at the destination, the cached destination data can be re-downloaded to the submitter, and the changes cached in the submitter, discarded. Absent this capability, a user has to manually manage the cached changes and cached data. The architecture can be distributed in that multiple submitters can submit changelists. The destination provides data integrity by managing submissions to assist in ensuring data integrity across multiple submissions. Automatic changelist cleanup is provided on the submitter so that changelists do not impact performance, memory, and storage. | 10-04-2012 |
20130125145 | Cross-Platform Application Programming Interfaces for Applications - Concepts and technologies are described herein for cross-platform application programming interfaces for applications. In accordance with the concepts and technologies disclosed herein, the cross-platform APIs support interoperability and extensibility with various application programs using a single language and/or set of APIs. Extensions authored for a particular application program may be used with other application programs that expose the same or a similar set of APIs, even if other object models or APIs associated with the application programs differ from one another. Thus, the APIs support cross-platform, cross-device, and cross-version compatibility of extensions. | 05-16-2013 |
20140344838 | Cross-Platform Application Programming Interfaces for Applications - Concepts and technologies are described herein for cross-platform application programming interfaces for applications. In accordance with the concepts and technologies disclosed herein, the cross-platform APIs support interoperability and extensibility with various application programs using a single language and/or set of APIs. Extensions authored for a particular application program may be used with other application programs that expose the same or a similar set of APIs, even if other object models or APIs associated with the application programs differ from one another. Thus, the APIs support cross-platform, cross-device, and cross-version compatibility of extensions. | 11-20-2014 |