Browse Prior Art Database

System and Method for Controlling Field Accessibility by Role and Document State

IP.com Disclosure Number: IPCOM000237882D
Publication Date: 2014-Jul-17
Document File: 9 page(s) / 129K

Publishing Venue

The IP.com Prior Art Database

Abstract

A web application that facilitates creation of a request (a multi-page form) for one or more contracted resources on a fixed-price contract.

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

Page 01 of 9

System and Method for Controlling Field Accessibility by Role and Document State

This invention is a web application that facilitates creation of a request (a multi-page form) for one or more contracted resources on a fixed-price contract. The request consists of several pages, each one prompting the user to specify required details (attributes of the project, milestones of the project, suggested suppliers to provide the resources, etc). Once the request is created, it proceeds through numerous states as it is approved, responded to, and ultimately submitted for purchase.

There are several different roles which access this request (Requester, Initiator, Buyer, Response Reviewer). Each page of the request contains multiple fields. Also, as stated previously, there are several different states through which this form proceeds, such as Draft, Submitted to Buyers, Submitted to Suppliers, etc. On any given page, the accessibility of the fields (whether mandatory, optional, read-only, or hidden) is dependent on the role of the user currently accessing the form, and the state of the request as a whole.

The solution consists of two relational database tables, which map each field on each page of the request to an access attribute (mandatory, optional, read-only, or hidden) based on the user role and the request state. The previous implementation of this application solved the problem by creating one read-write and one read-only form for each page and for each role. The disadvantage is that a single field change required changes to each form for each role, making maintenance of the application more complex than necessary.

Novelty Statement A typical application needs to handle one or more of the following view-layer restrictions:
role-based display
read only vs. read write
language / locales (currency, date, localization)
field restrictions / augmentations (size limits, character counter)
field accessibility (hidden, mandatory, optional)

Other frameworks have handled them separately and in different fashions, often resulting in duplicate coding efforts. Figure 1 shows a configuration-based mechanism along with tag libraries to handle all the above features in a single delivery, with all features delivered in the same way.

Figure 1

Comparison With Others In Field

Feature

                   JSTL 2.0 Struts 2.0 JSF Invention Inbuilt Accessibility Feature NO

Inbuilt Page Help Configuration

Inbuilt place holder for NO

NO

NO Yes

NO NO

NO Yes

NO

NO Yes

1


Page 02 of 9

JavaScript functions
Inbuilt definition of Date type form field NO

NO

NO Yes

Inbuilt definition of Currency field NO

NO

NO Yes

Inbuilt definition of counter for Text Area form field type NO

NO

NO Yes

Inbuilt Localization using tag libraries for particular role No

No

No

Yes

The invention consists of three parts:
I. The relational database tables, Figure 2
II. The custom tags in the tag library
III. The jsp

Figure 2
I. The relational database tables

2


Page 03 of 9

Acronyms used in Figure 2:

M - Master Table


R - R...