Browse Prior Art Database

Automated reorganization of structured data display Disclosure Number: IPCOM000179263D
Original Publication Date: 2009-Feb-10
Included in the Prior Art Database: 2009-Feb-10
Document File: 1 page(s) / 21K

Publishing Venue



If the original application contained instructions to add a button to the form page which is being broken into multiple pages, the new approach would be able to determine (based on hints from the developer) how to cause that button to be created on the correct one of the pages in the new multi-page form. The developer does not need to make any extra changes in the tangential pieces of the application, thereby reducing the likelihood of bugs due to an oversight.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 1

Automated reorganization of structured data display

Automated reorganization of structured data displayAutomated reorganization of structured data display

When using an automated Page Generation system for creating pages to display structured data or to provide a form for structured data, sometimes the data source is not in the arrangement one would like. This can be because there are too many fields to fit on a single page, or because the order and/or grouping of the fields is not satisfactory, Some technique is needed to instruct the page generation system in the desired page layout for the data or form. The proposed solution addresses the following problems which are exhibited by some or all of the existing solutions :

1. The new approach maintains flexibility if the layout of the data changes at the source . Hand-coded approaches like manually created JSP or struts pages do not have this flexibility .

2. The new approach manages the data validation along with the form presentation when the form is broken into multiple pages. This means that the no extra effort is required by the developer in order to perform validation page by page. In systems such as struts or JSF which do provide support for field validation, the developer would still have to re-target the validation declarations to refer to the new pages.

3. The approach works within an existing, working application without requiring any modification to the other parts of the application. Suppose you have an existing web-based application intended for use by a loan manager at a bank, and it has been decided that the form for initiating a new loan needs to be broken up from a single page into 3 pages. No doubt there are other pages/menus/etc. in the application which refer to the old one-page form, either invoking it, validating its data, or getting information from it. In most traditional systems, making this change would likely require some small (but easily overlooked) changes in the oth...