Declarative Form Markup for PIM Customization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Personal Information Manager (PIM) applications face difficulties in customization and data consistency across enterprise-wide office suites due to proprietary tools and interfaces, making it challenging for software developers to implement and deploy customizations, and these customizations often get lost with new software versions.

Innovation Solution

The use of declarative form markup specifications to generate native UI forms within PIM applications, allowing for data binding and incorporation of custom business logic, enabling flexible and consistent customization across the enterprise while maintaining performance and reusability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If proprietary tools and interfaces are used for PIM customization, then the PIM can provide centralized portal to business information, but customizations become difficult to implement and deploy throughout the organization

Engineering Contradiction:
Improvecustomization capabilityVSAvoidease of implementation
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces a proprietary format file as an intermediary between the customization requirements and the PIM application. This file serves as a standardized interface that simplifies the customization process, allowing developers to implement customizations without directly dealing with complex proprietary tools. The file acts as a mediator that translates customization intentions into PIM-compatible configurations, making the process easier to implement and deploy across the organization.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent enables customization by allowing changes to specific parameters within the PIM application through the proprietary format file. Instead of requiring complete reconfiguration or complex tool-based modifications, the system allows targeted parameter changes that can be easily deployed. This approach maintains adaptability while significantly improving ease of implementation, as developers can modify specific parameters rather than navigating complex customization interfaces.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If proprietary tools are used for PIM customization, then the PIM can be tailored to business processes, but data cannot be exposed in a consistent fashion across applications

Engineering Contradiction:
Improvecustomization capabilityVSAvoiddata consistency
Core Design Contradiction:
Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The patent creates a universal proprietary format file that can be used across multiple PIM applications and contexts. This single file format serves multiple functions: it defines customizations, exposes data consistently, and works across different applications within the organization. By establishing this universal interface, the system achieves both customization capability and data consistency, as the same format ensures uniform data exposure across all applications that support it.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent segments the customization system into distinct components: the proprietary format file, the data exposure interface, and the application layer. This segmentation allows the data exposure mechanism to be independently standardized in the format file, ensuring consistency across applications. The separation enables customizations to be defined once in the format file and then consistently applied across multiple applications, maintaining data composition stability while preserving adaptability.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If customizations are made in PIM application, then the PIM can adapt to business processes, but customizations are difficult to incorporate in new PIM software versions

Engineering Contradiction:
Improvecustomization capabilityVSAvoidcustomization persistence
Core Design Contradiction:
Adaptability or versatilityVSDuration of action of stationary object

Solution Approach 1:

The patent uses the proprietary format file as a copyable, portable representation of customizations. Instead of hardcoding customizations into the PIM application or relying on complex installation processes, the customizations are captured in a file that can be easily copied and transferred. This copying mechanism ensures that customizations persist across software versions, as the file can be retained and applied to new versions without being lost or difficult to incorporate.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent enables preliminary definition of customizations in the proprietary format file, which can then be automatically incorporated into new PIM software versions. By preparing the customization specifications in advance in this standardized format, the system ensures that when new versions are deployed, the customizations are already defined and ready to be applied, eliminating the difficulty of incorporating customizations into new versions.

Inventive Principle:
Principle #10Preliminary action

4Productivity

If native UI forms are used in PIM, then performance is maintained, but flexibility for customizations is limited

Engineering Contradiction:
Improveapplication performanceVSAvoidcustomization flexibility
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent creates a composite customization solution that combines the proprietary format file (providing flexibility) with the native PIM form rendering engine (providing performance). The format file defines customizations in a flexible, declarative manner, while the PIM's native form renderer processes and displays these customizations using its optimized rendering pipeline. This composite approach allows the system to achieve both customization flexibility and native performance, as the flexible definition layer works seamlessly with the high-performance rendering layer.

Inventive Principle:
Principle #40Composite materials

Data Source

PatentUS9298684B2Implementing custom user interface forms in a personal information manager
Publication Date: 2016.03.29 MICROSOFT TECHNOLOGY LICENSING LLC
  • US9298684B2 patent drawing
  • US9298684B2 patent drawing
  • US9298684B2 patent drawing

AI summary

Technologies are described herein for incorporating custom user interface (UI) forms into a personal information manager (PIM) application using a declarative form markup specification. A native PIM form specification is generated from a file containing the declarative form markup describing the custom UI form. When a request to display the custom UI form is received, a PIM native form renderer invokes a forms runtime engine that loads the original declarative form markup to process data bindings and event subscriptions contained therein. The custom UI form is then rendered to the display by the PIM native form renderer in conjunction with the forms runtime engine.