PRESERVING A STATE OF AN APPLICATION DURING UPDATE

• US 20090282396A1
• Filed: 05/07/2008
• Published: 11/12/2009
• Est. Priority Date: 05/07/2008
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Pugh, Sarah R., Smith, Braam P., Dunn, Eric, Boyer, John M.
• Application Number:
  US12/116,369
• Publication Number:
  US 20090282396A1
• Time in Patent Office: Days
• US Class Current: 717/170
• CPC Class Codes: G06F 40/174 Form filling; Merging
• CPC Class Codes: G06F 8/656 while running

Abstract

The present invention augments an application update with an automatic sequence of steps for instantiating the updated application in place of the currently running application, without unintended loss of the end-user generated data that comprises all or part of the current application state. The new version may consume most or all of the previously entered data to enter a state of needing a minimal amount of new information (which may be different from being in the state of ready to submit).

Claims

1. A computer-implemented method for preserving a state of an application during update, comprising:

providing an initial document template tagged by a name and a version number to represent an initial state of the application;

instantiating the application by providing a user with a copy of the initial document template, the instantiating yielding an instantiated document;

allowing the user to interact with the instantiated document;

performing a check for updates of the application; and

updating the application if the currently instantiated document application version is not a latest available version of the application, as follows;

obtaining a latest version of the initial document template;

obtaining a transformation description for converting end-user data in the instantiated document to an updated schema format, if an end-user data schema of the application has been changed,

creating a newly instantiated document on the latest version of the initial document template for the application,

transforming the end-user data using the transformation description if one was given, placing the end-user data or transformed end-user data into the newly instantiated document, and

replacing the instantiated document for the application with the new instantiated document for the application in the end-user experience.

2. The method of claim 1, the performing comprising performing the check for the updates at times in a document run time that are specified by at least one of a document run-time processor and the instantiated document.

3. The method of claim 2, the instantiated document or the document run-time processor run-time being capable of containing information relevant to accessing a web service that contains update information for the application.

4. The method of claim 2, the times comprising at least one of any start-up or reloading of the instantiated document, and selected attempts to perform a submission of the instantiated document to the server-side for transactional processing.

5. A system for preserving a state of an application during update, comprising:

providing an initial document template tagged by a name and a version number to represent an initial state of the application;

a module for instantiating the application by providing a user with a copy of the initial document template, the instantiating yielding an instantiated document;

a module for allowing the user to interact with the instantiated document;

a module for performing a check for updates of the application;

a module for updating the application if the currently instantiated document application version is not a latest available version of the application, the module for updating being configured to;

obtain a latest version of the initial document template,

obtain a transformation description for converting end-user data in the instantiated document to an updated schema format, if an end-user data schema of the application has been changed,

create a newly instantiated document on the latest version of the initial document template for the application,

transform the end-user data using the transformation description if one was given, placing the end-user data or transformed end-user data into the newly instantiated document, and

replace the instantiated document for the application with the new instantiated document for the application in the end-user experience.

6. The system of claim 5, the module for performing being configured to perform the check for the updates at times in a document run time that are specified by at least one of a document run-time processor and the instantiated document.

7. The system of claim 6, the instantiated document or the document run-time processor run-time being capable of containing information relevant to accessing a web service that contains update information for the application.

8. The system of claim 6, the times comprising at least one of any start-up or reloading of the instantiated document, and selected attempts to perform a submission of the instantiated document to the server-side for transactional processing.

9. A computer readable medium containing a program product for preserving a state of an application during update, the computer readable medium comprising program code for causing a computer system to:

provide an initial document template tagged by a name and a version number to represent an initial state of the application;

instantiate the application by providing a user with a copy of the initial document template, the instantiating yielding an instantiated document;

allow the user to interact with the instantiated document;

perform a check for updates of the application;

update the application if the currently instantiated document application version is not a latest available version of the application, as follows;

obtain a latest version of the initial document template,

obtain a transformation description for converting end-user data in the instantiated document to an updated schema format, if an end-user data schema of the application has been changed,

create a newly instantiated document on the latest version of the initial document template for the application,

transform the end-user data using the transformation description if one was given, placing the end-user data or transformed end-user data into the newly instantiated document, and

replace the instantiated document for the application with the new instantiated document for the application in the end-user experience.

10. The computer readable medium of claim 9, further comprising program code for causing the computer system to perform the check for the updates at times in a document run time that are specified by at least one of a document run-time processor and the instantiated document.

11. The computer readable medium of claim 10, the instantiated document or the document run-time processor run-time being capable of containing information relevant to accessing a web service that contains update information for the application.

12. The computer readable medium of claim 10, the times comprising at least one of any start-up or reloading of the instantiated document, and selected attempts to perform a submission of the instantiated document to the server-side for transactional processing.

13. A method for deploying an application for preserving a state of an application during update, comprising:

providing a computer infrastructure being operable to;

provide an initial document template tagged by a name and a version number to represent an initial state of the application;

instantiate the application by providing a user with a copy of the initial document template, the instantiating yielding an instantiated document;

allow the user to interact with the instantiated document;

perform a check for updates of the application;

update the application if the currently instantiated document application version is not a latest available version of the application, as follows;

obtain a latest version of the initial document template,

obtain a transformation description for converting end-user data in the instantiated document to an updated schema format, if an end-user data schema of the application has been changed,

create a newly instantiated document on the latest version of the initial document template for the application,

transform the end-user data using the transformation description if one was given, placing the end-user data or transformed end-user data into the newly instantiated document, and

replace the instantiated document for the application with the new instantiated document for the application in the end-user experience.

14. The method of claim 13, the computer infrastructure being further operable to perform the check for the updates at times in a document run time that are specified by at least one of a document run-time processor and the instantiated document.

16. The method of claim 14, the times comprising at least one of any start-up or reloading of the instantiated document, and selected attempts to perform a submission of the instantiated document to the server-side for transactional processing.

15. The method 14, the instantiated document or the document run-time processor run-time being capable of containing information relevant to accessing a web service that contains update information for the application.