Abstract: Architecture for handling large data selections with small and substantially constant memory footprints. The architecture facilitates the creation of sets of data objects (e.g., rows) of a data source based on selection of the data objects. The set structures can be defined according to a range (span) of data objects selected and a pattern of the objects selected. These set structures are then saved in memory, rather than the data objects, to provide optimized memory usage. In a database implementation, the solution stores the set representation (the structure) in nearly a constant amount of memory, regardless of the number of rows in the grid, and regardless of the number of rows selected. Memory usage can be proportional to the number of discontinuous spans of rows selected by the user. Structures in memory can be consolidated, replaced, or eliminated dynamically as the user changes row selections and pattern criteria.

Abstract: Architecture for handling large data selections with small and substantially constant memory footprints. The architecture facilitates the creation of sets of data objects (e.g., rows) of a data source based on selection of the data objects. The set structures can be defined according to a range (span) of data objects selected and a pattern of the objects selected. These set structures are then saved in memory, rather than the data objects, to provide optimized memory usage. In a database implementation, the solution stores the set representation (the structure) in nearly a constant amount of memory, regardless of the number of rows in the grid, and regardless of the number of rows selected. Memory usage can be proportional to the number of discontinuous spans of rows selected by the user. Structures in memory can be consolidated, replaced, or eliminated dynamically as the user changes row selections and pattern criteria.

Abstract: Architecture for handling large data selections with small and substantially constant memory footprints. The architecture facilitates the creation of sets of data objects (e.g., rows) of a data source based on selection of the data objects. The set structures can be defined according to a range (span) of data objects selected and a pattern of the objects selected. These set structures are then saved in memory, rather than the data objects, to provide optimized memory usage. In a database implementation, the solution stores the set representation (the structure) in nearly a constant amount of memory, regardless of the number of rows in the grid, and regardless of the number of rows selected. Memory usage can be proportional to the number of discontinuous spans of rows selected by the user. Structures in memory can be consolidated, replaced, or eliminated dynamically as the user changes row selections and pattern criteria.

Abstract: Publishing a document from a cloud storage and/or productivity application is described. A cloud storage and/or productivity application can include a command to publish that may be executed from a user interface to the cloud storage and/or productivity application. In response to receiving a request to publish the document through a user interface, a copy of a document to be published can be communicated to a publish service of a content delivery system. The copy of the document can be a productivity application file.

Abstract: The publishing and distribution of productivity documents to collections are described. Document collections distribution and publishing can be facilitated by a service that receives documents to publish and stores the documents at a storage of the service. The documents can be stored in the file formats they were created in, including productivity application file formats such as word processing file format and presentation file format. The service also stores metadata associated with each document, including a collection identifier that identifies each collection that a document is added to. The documents and the collections to which the documents may be associated with are searchable and discoverable through the service.

Abstract: Techniques to implement time intelligence for application program are described. An apparatus may include a calendar application module. The calendar application module may be arranged to define and generate a calendar for an application program, the calendar application module to define time members for a time dimension of a multidimensional data model, assign a monotonically increasing unique identifier to each time member, and generate the calendar with time members from the time dimension using the unique identifiers. Other embodiments are described and claimed.

Abstract: Financial intelligence architecture that employs financial types that are combined with rules to build financial behavior into the product. Types have behaviors such that types can be assigned that lead to the physical creation of underlying code which embodies the behaviors. Extensibility is provided at least by type parameterization and new type creation. Because types are a design time experience, types are two-way and can be modified, even after instantiation. This allows for mixing and matching of types and underlying behavior giving the system more flexibility at design time while providing a huge simplification of all the details that actually go into such financial applications. The type library is a set of rules that produce metadata, which metadata is later processed by a separate engine to produce the physical schema. The type library defines the basic interactions, data types, and behaviors for predefined dimensions in the system.

Abstract: Computer-implemented methods, computer-readable media, and an application system are disclosed for creating and deploying metadata-generated applications. Access is provided to one or more type libraries that each include one or more defined object types configurable for use in generating the application. The defined object types include data structure types, rule types, and data types. Input is elicited from a user regarding desired content and function of the application. Based on the user input, metadata is generated to adapt the defined object types to generate the application. Metadata is generated to adapt the defined data structure types to create one or more application databases, to adapt the defined rule types to create one or more application behaviors, and to adapt the defined data types to create one or more application data types.

Abstract: Architecture for handling large data selections with small and substantially constant memory footprints. The architecture facilitates the creation of sets of data objects (e.g., rows) of a data source based on selection of the data objects. The set structures can be defined according to a range (span) of data objects selected and a pattern of the objects selected. These set structures are then saved in memory, rather than the data objects, to provide optimized memory usage. In a database implementation, the solution stores the set representation (the structure) in nearly a constant amount of memory, regardless of the number of rows in the grid, and regardless of the number of rows selected. Memory usage can be proportional to the number of discontinuous spans of rows selected by the user. Structures in memory can be consolidated, replaced, or eliminated dynamically as the user changes row selections and pattern criteria.

Abstract: 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.

Abstract: Computer-implemented methods, computer-readable media, and an application system are disclosed for creating and deploying metadata-generated applications. Access is provided to one or more type libraries that each include one or more defined object types configurable for use in generating the application. The defined object types include data structure types, rule types, and data types. Input is elicited from a user regarding desired content and function of the application. Based on the user input, metadata is generated to adapt the defined object types to generate the application. Metadata is generated to adapt the defined data structure types to create one or more application databases, to adapt the defined rule types to create one or more application behaviors, and to adapt the defined data types to create one or more application data types.

Abstract: Techniques to implement time intelligence for application program are described. An apparatus may include a calendar application module. The calendar application module may be arranged to define and generate a calendar for an application program, the calendar application module to define time members for a time dimension of a multidimensional data model, assign a monotonically increasing unique identifier to each time member, and generate the calendar with time members from the time dimension using the unique identifiers. Other embodiments are described and claimed.

Abstract: Financial intelligence architecture that employs financial types that are combined with rules to build financial behavior into the product. Types have behaviors such that types can be assigned that lead to the physical creation of underlying code which embodies the behaviors. Extensibility is provided at least by type parameterization and new type creation. Because types are a design time experience, types are two-way and can be modified, even after instantiation. This allows for mixing and matching of types and underlying behavior giving the system more flexibility at design time while providing a huge simplification of all the details that actually go into such financial applications. The type library is a set of rules that produce metadata, which metadata is later processed by a separate engine to produce the physical schema. The type library defines the basic interactions, data types, and behaviors for predefined dimensions in the system.

Abstract: 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.