Forms automation system implementation5563998Abstract A system and method for the electronic design, storage, and distribution of business forms maximizes all of these functions, utilizing a forms automation platform and a central library facility. The forms automation platform includes customer profile, form profile, form field description, and distribution information files each having a unique customer identifier, and typically also having a unique form identifier, and including detailed information about each form. The central library facility includes customer profile, geographic profile, printer profile, distribution data, form profile, and form output format files; again unique customer identifiers, as well as specific form identifiers, are provided. Forms are automatically distributed by the central library facility to end user sites, at which remote computers are located, by polling for forms to be released, establishing a session with the end users to which release is to be made, and then electronically transferring the forms. Form profile information that is typically stored--in order to effectively process requests--include the software package used to design the form, a description of the form, the date of form creation and/or last revision, the number of parts, whether the form has landscape or portrait mode, the length, and the width of the form. Claims What is claimed is: Description BACKGROUND AND SUMMARY OF THE INVENTION
______________________________________
Form Profile Library Reports Utility Exit
Run Form Design Program
Enter Customer ID: 3-1234567-00000
Form SW
JFDESIGN
PERFORM
F3
Char Mode: Replace Page 3 Count: 3
______________________________________
For downloading information (e.g. forms and release dates) to the CLF 12:
______________________________________
Update Exit
Update Central Library with Selected Forms.
CLF ID:
SAVANNAH CENTRAL LIBRARY UPDATE
Dist
Select
Customer ID Form ID Rev Status
Date
______________________________________
3-1234567-00000
TINFORM 0 Com-
pleted
3-1234567-00000
SIGDEMO 0 Com-
pleted
3-1234567-00000
UMIVFILL 0 Com-
pleted
Press [F5] to return to menu
To select Form for Library Update, enter `*`.
To save selections, press [F10].
Char Mode: Replace Page 1 Count: 3
______________________________________
For encoding a variable data information field, which is sent to the CLF 12 and verified there:
______________________________________
Profile Query Ext
Define Form Profile for current form.
FORM FIELDS
Field Name
TIMFLD1 Sequence 1 Location 2.times.4in
Field Type
CHAR Length 8 Format*******X
Validation
NONE
Calculation
NONE
Field Name
TIMFLD2 Sequence 2 Location 2.times.3in
Field Type
CHAR Length 10 Format********X
Validation
NONE
Calculation
NONE
Field Name
TIMFLD3 Sequence 3 Location 4.times.4in
Field Type
DATE Length 8 FormatMM-DD-YY
Validation
NONE
Calculation
NONE
Press [F5] to return to menu
Char Mode: Replace Page 2 Count: 3
______________________________________
For illustrating form profile information for form which has been created:
__________________________________________________________________________
Fields Query Exit
Define Form Fields for current form.
FORM PROFILE INFORMATION
Cust ID
3-1234567-00000
Cust Name
XYZ BANK
Form ID
TINFORM
Descr CUSTOMER ADD & TIN CHANGES-HP W/S2 CART.
Revision
0 Form Status
NEW Release Status COMPLETED
Form Path
C:.backslash.XYZBANK
Form Width
8.5 No. of Pages 1
FORM FILES:
Form Length
11 No. of Parts 1
File Name
PD Type
CLF ID
Orientation
PORTRAIT
Duplex N
TINFORM.IFD
HP S SAVANNAH
Form SW
JFDESIGN TINFORM.MDF
HP C SAVANNAH
TINFORM.PRT
HP P SAVANNAH
By Date
Created
FAP 19-NOV-90
Modified
FAP 19-NOV-90
Released
Press [F5] to return to menu
Char Mode: Replace Page 1 Count: 1
__________________________________________________________________________
An exemplary screen for inputting data, e.g. customer profiles, is:
__________________________________________________________________________
Query Exit
Move to query screen
CUSTOMER PROFILE INFORMATION
Cust ID 3-1234567-00000
Directory C:.backslash.CSBANK
Cust Name XYZ BANK
Phone Number (800) 800-8000
Contact S. Jones Fax Number (800) 800-8001
CUSTOMER ADDRESS: SHIPPING ADDRESS:
Addr 222 MAIN STREET
Addr 222 MAIN STREET
City SPRINGFIELD City SPRINGFIELD
State ME
Zip 00001
Cntry USA
State ME
Zip 00001
Cntry USA
Attn S. JONES
HW/SW HW/SW Name:
Description
S JFDESIGN JETFORM DESIGN V. 2.1
H HPLJIID HEWLETT-PACKARD LASERJET IID
S PERFORM PERFORM V.2.1
Press [F5] to return to menu
Char Mode: Replace Page 1 Count 1
__________________________________________________________________________
An exemplary screen for inputting CLF profile information is:
______________________________________
Query Exit
Move to query screen
CENTRAL LIBRARY FACILITY PROFILE
INFORMATION
Customer ID
CLF ID SPRINGFIELD 3-1234567-00000
Location XYZ BANK, SPRINGFIELD,
ME
Description
IBM PS/2 MODEL 80,
)S/2 V. 1.2
Administrator
S. JONES
Phone (800) 800-8000
Number
Modem (800) 800-8002
Number
Fax Number
(800) 800-8001
Press [F5] to move to menu
Char Mode: Replace Page 1 Count 1
Exit
Return to master record
An exemplary customer profile query screen is:
CUSTOMER PROFILE
QUERY
Cust ID
3-1234567-00000
Hardware/Software
CLF ID Type Name
______________________________________
SAVANNAH H HPLJIID
S JFDESIGN
S PERFORM
______________________________________
The data model diagram for FAP 14 is provided in FIG. 6. The same conventions are utilized here and as in the CLF data model diagram of FIG. 11. The connections in FIG. 6 refer to the relationship between the two entities; i.e. two entities connected by an arrow with one arrow head at one end and a double arrow head at the other end are said to have a "one-to-many" relationship. In a relational database construct, this means that for each parent record in the first entity there may/shall exist many child records in the second entity. A glossary of the individual tables of the FAP 14 illustrated in FIG. 6 is as follows:
______________________________________
FORMS AUTOMATION PLATFORM TABLES
DATA Ref.
ENTITY NAME ALIAS #
______________________________________
ASSOCIATION CUSTOMER/CLF 76
INFO ASSOCIATION TABLE
CLF PROFILE CLF MASTER TABLE 77
CUSTOMER CUSTOMER MASTER 78
PROFILE TABLE
DISTRIBUTION FORM DISTRIBUTION 79
INFO TABLE
FIELD FORM FIELD DEFINITION
80
DESCRIPTIONS TABLE
FORM FORM DISTRIBUTION 81
FILENAMES FILENAMES TABLE
FORM FORM MASTER TABLE 82
PROFILES
FORM SW & FORMS SW/PRINTERS 83
PRINTER INFO TABLE
PRINTER FORM FILE PRINTER 84
IDENTIFIERS TYPES TABLE
SYSTEM FAP SYSTEM PARAMETER
85
PARAMETER INFO
TABLE
______________________________________
Each file typically has a number of elements, either of the number or character type, having predefined lengths. A listing of the elements, type (characters or numerical), field length, and description of the elements, for each of the tables 76-85 of FIG. 6 is as follows: ##SPC1## FIG. 7 is a data flow diagram for the FAP 14. Utility, report generation, archiving, form maintenance, profile maintenance, and CLF 12 updating functions are provided, as illustrated in FIG. 7. The interrelationships between the various components as shown in FIG. 7 are more fully indicated by FIGS. 8a-8e. FIG. 9 provides a flow chart indicating the general steps executed by FAP 14 for accessing the CLF 12 from the FAP to transfer form information. The program is initiated from a command file, as indicated at 100. A session with a target CLF 12 is allocated. This step is indicated since typically a vendor's FAP 14 can be associated with more than one CLF 12, for example a centralized location for the FAP 14 may serve a number of CLFs 12, one associated with each different customer (each customer having a plurality of geographically remote user stations). At 102, the files indicated for transfer are transferred from the FAP 14 to the targeted CLF 12, and confirmation is provided at 13. Then the remote CLF table population function is initiated at 104, and when that function is completed it is confirmed at 105. Data may then be sent to and from the CLF 12 from and to the FAP 14 at 106, for example data useful for determining the status of the forms. An acknowledgement is issued at 107, and any post completion processing done at 108 before the processing ends. As illustrated in FIG. 10, the CLF 12 preferably communicates via modems 41 with the FAP 14, or token ring if located in the same facility, and via modems 42 with the host computer 34. In order to provide human interface, a terminal 143 having a video display 144 and a keyboard 145 and/or mouse 146, is provided associated with the CLF 12. Other technologies could also be utilized, such as optical disks, and the like, to store the forms on either magnetic or optical media. As illustrated schematically in FIG. 3, major functions of the CLF 12 are forms management and distribution. The application software 29 creates, maintains, up-dates and ensures the integrity of the database 29 provided by CLF 12. The CLF 12 also processes end user requests inputted by device 143 (e.g. via the various electronic communications facilities already discussed), and distributes electronic forms to all of the user locations 15. Inherent in the CLF 12 is restricted user access based on security levels, the production of desired reports to support the customer's requirements, sorting of the contents of the library based upon user specified parameters, and up-dated processing. At the CLF a search will be conducted of the electronic forms database 29 on a predetermined basis, to determine all forms scheduled for release on a specified date. The forms will then be distributed based upon the end user profiles which have been designated. The CLF 12 is a logical entity, and its processes may be distributed over one or more processors, either directly on the customer's main frame 34, or at the vendor's facility, utilizing a file server, or the like. User interface software executed by CLF 12 is menu driven in the preferred embodiment. The major menu items provided to the user of the CLF 12 main menu screen utilizing terminal 143 are forms, profile management, distribution management, release function, queries and report, and utilities. A typical main menu screen is as follows:
______________________________________
CENTRAL LIBRARY FACILITY
MAIN MENU
______________________________________
Enter the Capital Letter of the Item Below and
Press Enter ->
Forms management
Profile management
Distribution management
Release function
Queries and reports
Utilities
F3=EXIT
______________________________________
The first item of selection is "Forms management". The Forms management menu typically appears as follows:
______________________________________
CENTRAL LIBRARY FACILITY
FORMS MANAGEMENT MENU
______________________________________
Enter the Capital Letter of the Item Below and
Press Enter ->
List/delete/update forms
Field information list
Output format list
Print form
F2=REFRESH F3=EXIT
______________________________________
The first selectable item from the Forms management menu is the forms list. A forms list screen, showing descriptions and other information of a few exemplary forms might appear as follows:
__________________________________________________________________________
CENTRAL LIBRARY FACILITY
FORMS LIST
Type a P in the action column to print and press PF4.
Revision
Release
Creation
Action Form Id
Status
Date Date Date Forms Description
__________________________________________________________________________
.sub.-- CSADRTIN
CUR -- -- -- CUSTOMER ADDRESS & TI
.sub.-- CSDEMOGR
CUR -- -- -- DEMOGRAPHIC INFORMATI
.sub.-- CSSGNCRD
CUR -- -- -- SIGNATURE CARD
.sub.-- CSUNIVER
CUR -- -- -- UNIVERSAL FORM
.sub.--
.sub.--
.sub.--
F3-EXIT F4=QUEUE PRINT
__________________________________________________________________________
The last of the selectable items in the Forms management menu is the forms print selection, the screen for which might appear as follows:
__________________________________________________________________________
CENTRAL LIBRARY FACILITY
PRINT FORMS
__________________________________________________________________________
Enter number of copies and destination for each form More: +
NUMBER
PRINTER
SITE
CANCEL
FORM ID
FORM DESCRIPTION COPIES
ID ID PRINT
CSSGNCRD
SIGNATURE CARD N
PF3=EXIT PF4=PROCESS REQUEST PF8=NEXT FORM
__________________________________________________________________________
By filling information into the prompt sections of this screen, an operator of CLF terminal 43 can schedule printing of a desired number of copies of specific forms to a desired printer at a desired use location. The second menu item in the main menu is the profile management option. The typical profile management menu screen appears as follows:
______________________________________
CENTRAL LIBRARY FACILITY
PROFILE MANAGEMENT MENU
______________________________________
Enter the Capital Letter of the Item Below and
Press Enter ->
User profile
Category profile
Site profile
corporate proFile
Geographic profile
cusTomer profile
grOup profile
Printer profile
F2=REFRESH F3=EXIT
______________________________________
The first selectable item of the profile management menu is the user profile, a screen of which appears as follows:
__________________________________________________________________________
USER PROFILE
__________________________________________________________________________
Update/Delete: Type "U" and/or "D" in ACTION column and press "ENTER"
Add: Press F4; Associations: Type an "S" i ACTION column and press F6
USER CORP GEO.
****** LOCK OUT ******
ACT
ID USER NAME
ID ID FLAG
DATE TIME
__________________________________________________________________________
-- TOM Tom
-- CLA Cristie 111 Y 12-10-1990
10:10:10
-- DLY Donna
-- FEA Fran
-- JOE Joe 111 232
-- JZA Julie
-- SAN SAM
D002 **** END OF OUTPUT ****
F2=REFRESH F3=EXIT F4=ADD
__________________________________________________________________________
If F4 is actuated from the above screen, then the following screen appears:
__________________________________________________________________________
USER PROFILE ADD
__________________________________________________________________________
Enter Data in all fields - THEN press "ENTER"
User ID . . . : User Name . . . :
Corporate ID . . . :
Geographic ID . . . :
Telephone No . . . :
Distribution Tickler Flag . . ..sub.-- Amin.
flag..sub.--
*******************************Lock Out Data******************************
Lock Out Date:
Lock Out Time: Lock Out Flag.:.sub.--
version 0.1
ekF2=REFRESH F3=EXIT
__________________________________________________________________________
The third selectable item from the profile management menu is the site profile. The site profile screen appears as follows:
______________________________________
CENTRAL LIBRARY FACILITY
SITE PROFILE
______________________________________
Customer ID: 2-4561686-00000
Customer Name:
State Bank
Site ID
Site Description
Geographic ID
Network ID
______________________________________
FLA001 Tampa Banking Dept
TPA001 FLATPA01
GE0001 Atlanta Branch ATL001 GE0ATL01
NYC002 New York Branch
NYC001 NYNYC02
CHI003 Chicago Branch CHI001 ILCHI01
SCA001 South Carolina Office
CAE001 SCACAE01
PF3=EXIT
______________________________________
The sixth menu item on the profile management menu screen is the customer profile. When that menu item is selected, the customer profile screen typically appears as follows:
______________________________________
CENTRAL LIBRARY FACILITY
CUSTOMER PROFILE
______________________________________
Customer ID: 2-4561686-00000
Customer Name: State Bank
Address: The American Road
Atlanta
GA 30123 USA
Contact Name: Don Jones
Phone Number: 800-321-1234
PF3=EXIT
______________________________________
The Group profile of groups list item provides the following exemplary screen:
__________________________________________________________________________
GROUPS LIST
__________________________________________________________________________
UPDATE/DELETE: Type U and/or D in action column and press Enter. ADD:
Press F4;
ASSOCIATION: Type an S in action column and press F6.
Action
Group ID
Seq. # Group Description
__________________________________________________________________________
-- G1 1 Test 1
-- G2 1 Test 2
-- G2 2 Test 3
-- G3 1 Test 4
-- G3 2 Test 5
-- G3 3 Test 6
-- GRP101
1 New Group Added
-- NRC001
1 First MRC Group
D002
***** END OF OUTPUT
****
F3=EXIT F4=ADD F6=ASSOCIATIONS F12=CANCEL
__________________________________________________________________________
If F4 is actuated from the above screen, then the following exemplary screen appears.
______________________________________
ADD DISTRIBUTION GROUP
______________________________________
Type in entries for the distribution group and press
<Enter> to add.
Group Id . . .
Sequence Number . . .
Group Description . . .
F3=EXIT E12=Cancel
______________________________________
If F6 is actuated from the Groups list screen, then the following appears:
______________________________________
ASSOCIATION MENU
______________________________________
Type the Id of a base item and press <Enter>, OR type an "S"
and press <Enter> for a selection listing of the base item.
Association
Base Item Id Items
______________________________________
.sub.-- FORM . . . .sub.-- GROUPS
.sub.-- GROUP ID . . . .sub.-- FORMS
.sub.-- SITES
SEQ. NUMBER . . .
.sub.-- USER . . . .sub.-- SITES
.sub.-- SITE . . . .sub.-- USERS
.sub.-- PRINTERS
.sub.-- GROUPS
.sub.-- PRINTER . . . .sub.-- SITES
F3=Exit F12=Cancel
______________________________________
Upon insertion of a particular group ID from the groups list screen (e.g. "G1"), the following exemplary screen appears:
__________________________________________________________________________
SITES ASSOCIATED WITH A GROUP
__________________________________________________________________________
Group ID: GI SEQ: 1 DESC: TEST 1
ADD: Press F4; DELETE: Type a "D" in action column and press <Enter>.
SITE CORP
GEO. NET
ACT
ID DESCRIPTION
ID ID MODEM TELEPHONE
ID
__________________________________________________________________________
-- KANSAS
KANSAS
-- S1
-- SIT101
NEW SITE ADDED
-- WISC WISCONSIN
D002 **** END OF OUTPUT ****
F3=EXIT F4=ADD F12=CANCEL
__________________________________________________________________________
If F4 is actuated from the above screen, then the following exemplary screen appears, to support data entry to get sites associated with a group:
__________________________________________________________________________
ADD SITES ASSOCIATED WITH A GROUP
__________________________________________________________________________
To add items to the association list, type one or more "S" in MORE: +
the action column and press <Enter>
SITE CORP
GEO. NET
ACT
ID DESCRIPTION
ID ID MODEM TELEPHONE
ID
__________________________________________________________________________
-- ALA ALABAMA
-- CALIF CALIFORNIA
-- COLO COLORADO COLNET
-- FLA FLORIDA FLANET
-- KANSAS
KANSAS
-- MASS MASSACHUSETTS
-- MICH MICHIGAN
-- MINN MINNESOTA 55543210000000000
-- S1
-- S2
-- S3
-- SIT101
NEW SITE ADDED 12-1-90
F3=EXIT F8=FWD F12=CANCEL
__________________________________________________________________________
The last selectable item on the profile management menu is the printer profile option. When the printer profile option is selected, the screen that typically appears is as follows:
______________________________________
CENTRAL LIBRARY FACILITY
PRINTER PROFILE
______________________________________
Customer ID:
2-4561686-00000
Customer Name:
State Bank
Printer ID
Printer Type
Printer Manufacturer Name
______________________________________
01 PS Adobe PostScript
02 HP Hewlett Packard LaserJet
03 AF IBM 3800 Printers
04 AF IBM 4019 Printer
05 MF XEROX 9700 Printer
PF3=EXIT
______________________________________
The third selectable item on the main menu is the distribution management function. If that function is selected, the screen that typically appears is as follows:
______________________________________
CENTRAL LIBRARY FACILITY
DISTRIBUTION MENU
______________________________________
Enter the Capital Letter of the Item Below and
Press Enter->
New form distribution cycle
Add form distribution
Delete form distribution
FS=REFRESH F3=EXIT
______________________________________
The fourth selectable item on the main menu is the release function. If that function is selected, the screen that typically would appear is as follows:
______________________________________
CENTRAL LIBRARY FACILITY
RELEASE FORMS MENU
______________________________________
Enter the Capital Letter of the Item Below and
Press Enter ->
Release forms to site
Automatic release
release From remote site
F2=REFRESH F3=EXIT
______________________________________
The first selectable item on the release forms menu is to release the form to desired sites. If that item is selected, the typical screen that would appear is as follows:
______________________________________
CENTRAL LIBRARY FACILITY
RELEASE TO SITES
______________________________________
Do you wish to release New/revised forms (N) or
All forms (A)?
Enter Selection here (N, A) > .sub.--
Also select one of the choices below:
.sub.-- Release All Forms to All Sites
.sub.-- Release All Forms for Specific Site(s)
.sub.-- Release Specific Forms(s) to All Sites
.sub.-- Release Specific Form(s) to Specific Sites
F2=Refresh F3=Exit
______________________________________
The above provides a description for the major screens that appear in the implementation of the CLF 12 functions, although other screens are provided too, for example customer specific screens depending upon what queries and reports are desired, and conventional utilities functions. FIG. 11 is a data model diagram for the CLF 12. The individual components illustrated in FIG. 11 are individual files which have particular elements or records therein in predefined fields and with predefined addresses. The bare essentials of the system are contained within the dotted lines, but the other files are also important for ultimate maximum utilization. The connections in FIG. 11 refer to the relationship between the two entities; i.e. two entities connected by an arrow with one arrow head at one end and a double arrow head at the other end are said to have a "one-to-many" relationship. In a relational database construct, this means that for each parent record in the first entity there may/shall exist many child records in the second entity. In the preferred embodiment, the various files have the following major elements: The customer profile file 150 contains all relevant information about the customer. The configuration of that file is as follow:
__________________________________________________________________________
TABLE NAME: CUSTOMER PROFILE ALIAS: CP
__________________________________________________________________________
ELEMENT/RECORD
DB TABLE ELE.
KEY LEN DEFINITION
__________________________________________________________________________
CLF Customer ID
CP.sub.-- CUS.sub.-- ID
1 006 Uniquely identifies each customer.
Country Indicator
CP.sub.-- MBF.sub.-- CTRY.sub.-- ID
E 001 Country indicator for the customer ID.
Customer ID CP.sub.-- MBF.sub.-- ID
E 015 Corporate identifier for a customer.
Customer Name
CP-NME E 030 Name of customer.
ADDR1 CP.sub.-- ADR.sub.-- 1
E 030 Street address one.
ADDR2 CP.sub.-- ADR.sub.-- 2
E 030 Street address two.
City CP.sub.-- CTY
E 030 Name of city.
State Prov CP.sub.-- STE
E 004 State or province abbreviation.
Zip CP.sub.-- ZIP
E 010 The customer's zip code (U.S.) or
postal code.
Country CP.sub.-- CTRY
E 004 Name of country in which the customer
is located.
Num Versions CP.sub.-- NBR.sub.-- ARC
E 001 Number of archived form versions to
keep.
Contact Name CP.sub.-- CTC
E 030 Name of the contact person at the
customer location.
Contact Phone
CP.sub.-- CTC.sub.-- TEL
E 015 Phone number of the customer contact
person.
Customer Status
CP.sub.-- STA.sub.-- CDE
E 001 Current CLF customer status `D` =
deleted `A` = Activated
Customer Status Date
CP.sub.-- STA.sub.-- DTE
E 008 Date of status change for customer
CLF ID CP.sub.-- CLF.sub.-- ID
E 010 A unique identifier for each customer's
CLF
Num Levels CP.sub.-- NBR.sub.-- LVL
E 001 The number of corporate organization
levels to be used
Level Name 1 CP.sub.-- CORP.sub.-- LVL.sub.-- 1
E 015 First name for corporate level
definition
Level Name 2 CP.sub.-- CORP.sub.-- LVL.sub.-- 2
E 015 Second name for corporate level
definition
Level Name 3 CP.sub.-- CORP.sub.-- LVL.sub.-- 3
E 015 Third name for corporate level
definition
__________________________________________________________________________
Key Data:
Primary Key
(CLF Customer ID)
__________________________________________________________________________
Indexes:
Name On Columns
Type of Work
__________________________________________________________________________
Cusidx
CLF Customer ID
Primary, Ascending, Unique
__________________________________________________________________________
Relationship to Other Tables:
Parent of:
Form Profile
Category Profile
Printer Profile
Corporate Profile
Geographic Profile
User Profile
Site Profile
Group Profile
All Tables are Access Thru CLF Customer
__________________________________________________________________________
ID
As many corporate level definitions may be provided as is necessary in order to meet the customer's needs. The corporate profile provides a file 151 for the customer to charge back the forms to various entities within the organization. This file typically has the same number of levels as the number of levels for the corporate level definition in the customer profile file 150. An exemplary corporate profile file 151 is as follows:
______________________________________
TABLE NAME: CORPORATE PROFILE ALIAS: CO
______________________________________
DB
ELEMENT/ TABLE
RECORD ELE. KEY LEN DEFINITION
______________________________________
CLF 1 006 Uniquely identifies.
Customer ID each customer.
Corporate ID 2 006 Code for each different
corporate profile for
a customer
Level 1 E 020 Highest level in corporate
organization.
Level 2 E 020 Second highest level in
corporate organization.
Level 3 E 020 Third highest level in
corporate organization.
______________________________________
Key Data:
Primary Key (CLF Customer ID, Corporate ID)
Foreign Key FK.sub.-- CORPA (CLF Customer ID)
References Customer Profile
on Delete Cascade;
______________________________________
Indexes:
Name On Columns Type of Index
______________________________________
CORPIDX CLF Customer ID
Primary, Ascending, Unique
Corporate ID
______________________________________
Relationship to Other Tables:
Parent of: User Profile Thru CLF Customer ID,
Corporate ID
Site Profile Thru CLF Customer ID,
Corporate ID
Dependent of:
Customer Profile Thru CLF Customer ID
______________________________________
The geographic profile file 152 has data for the various geographically remote user locations, such as branches, offices, etc. A typical geographical profile file 152 is configured as follows:
______________________________________
TABLE NAME: GEOGRAPHIC PROFILE ALIAS: GP
______________________________________
DB
ELEMENT/ TABLE
RECORD ELE. KEY LEN DEFINITION
______________________________________
CLF 1 006 Uniquely identifies
Customer ID each customer.
Geographic ID 2 006 Unique Code for each
different geographic
profile used
SMSA-Code E 003
Country Name E 004 Name of Country
(International Code).
Region Name E 020 Name of Region.
State/Province E 004 Name of State or
Name Province.
State Region E 020 Name of Region with-
Name in a State or Province.
City Name E 030 Name of City.
City Region E 030 Name of Region with-
Name in City.
Building/Branch E 015 Code to Identify a
ID Building or Branch.
Floor Number E 003 Number of the Floor
in the Building.
______________________________________
Key Data:
Primary Key (CLF Customer ID, Geographic ID)
Foreign Key FK.sub.-- GEOA (CLF Customer ID)
References Customer Profile
on Delete Cascade;
______________________________________
INDEXES:
Name On Columns Type of Index
______________________________________
DEOIDX CLF CUSTOMER PRIMARY, ASCENDING,
ID UNIQUE
GEOGRAPHIC ID
______________________________________
Relationship to other Tables:
Parent of: User Profile Thru CLF Customer ID,
Geographic ID
Site Profile Thru CLF Customer ID,
Geographic ID
Dependent of:
Customer Profile Thru CLF Customer ID
______________________________________
The security table 153 limits access to the various files in the data model of FIG. 11 to ensure that only people with the appropriate responsibility can command the system to perform important functions. The typical configuration of the security table 153 is as follows:
__________________________________________________________________________
TABLE NAME: SECURITY ALIAS: SE
__________________________________________________________________________
ELEMENT/RECORD
DB TABLE ELE.
KEY
LEN
DEFINITION
__________________________________________________________________________
CLF Customer ID 1 006
Uniquely identifies each customer.
User ID 2 006
The Logon ID associated with each CLF user.
Password 3 006
The Password associated with each user ID.
Security Funct E 001
The Authority to maintain the security
table.
Prof Mgmt Funct E 001
The Authority to maintain profile tables.
Form Mgmt Funct E 001
The Authority to maintain the central forms
library.
Dist Funct E 001
The Authority to control form distribution
to end site.
Release Funct E 001
The Authority to release forms to the end
user site.
Report Funct E 001
The Ability to produce reports.
Security Level E 001
Defines the level of authority for each
user.
Distribution Tickler Flag
E 001
Flag to indicate if new forms have arrived
in the
system.
__________________________________________________________________________
Key Data:
Primary Key
(CLF Customer ID, User ID, Password)
Foreign Key
FK.sub.-- Sea (CLF Customer ID, User ID)
References User Profile
On Delete Cascade;
__________________________________________________________________________
Indexes:
Name On Columns
Type of Work
__________________________________________________________________________
SEIDX
CLF Customer ID
Primary, Ascending, Unique
User ID
Password
__________________________________________________________________________
Relationship to Other Tables:
Dependent of:
User Profile Thru CLF Customer ID, User ID
__________________________________________________________________________
The user profile file 154 describes the end user, and it is interrelated with the security table 153. A typical configuration of the user profile file 154 is as follows:
__________________________________________________________________________
TABLE NAME: USER PROFILE ALIAS: UP
__________________________________________________________________________
ELEMENT/RECORD
DB TABLE ELE.
KEY
LEN
DEFINITION
__________________________________________________________________________
CLF Customer ID 1 006
Uniquely identifies each customer.
User ID 2 006
The Logon ID associated with each CLF user.
User Name E 030
Name of User.
User Phone E 015
Telephone number of user.
Lock Out Flag E 001
Indicator which allows or prevents a user
from signing
on.
Lock Out Date E 002
Date a user's ID is locked due to invalid
access
attempts.
Lock Out Time E 008
Time a user's ID is locked due to invalid
access
attempts.
Corporate ID E 006
Code for each different corporate profile
for a
customer.
Geographic ID E 006
Unique code for each different geographic
profile
used.
Distribution Tickler Flag
E 001
Flag to indicate new forms have arrived in
the
database.
__________________________________________________________________________
Key Data:
Primary Key
(CLF Customer ID, User ID)
Foreign Key
FK.sub.-- USERA (CLF Customer ID, Corporate ID)
References Corporate Profile
On Delete Restrict;
Foreign Key
FK.sub.-- USERB (CLF Customer ID, Geographic ID)
References Geographic Profile
On Delete Restrict;
Foreign Key
FK.sub.-- USERC (CLF Customer ID)
References Customer Profile
On Delete Restrict;
__________________________________________________________________________
Indexes:
Name On Columns
Type of Index
__________________________________________________________________________
USERIDX
CLF Customer ID
Primary, Ascending, Unique
User ID
USERIDXA
CLF Customer ID
Ascending
Corporate ID
USERIDXB
CLF Customer ID
Ascending
Geographic ID
Relationship to Other Tables:
Parent of:
User/Site Thru CLF Customer ID, Site
Security Thru CLF Customer ID, User ID
Dependent of:
Customer Profile thru CLF Customer ID
Corporate Profile thru CLF Customer ID, Corporate ID
Geographic Profile thru CLF Customer ID, Geographic
__________________________________________________________________________
ID
The site profile 155 is interrelated with the geographic and corporate profiles. A file in the site profile 155 is provided for each user location. Typically hardware, such as a printer 16 and/or a PC (e.g. 94, at 15), is provided at the geographically remote user locations which correspond to the files in the site profile 155. A typical configuration of the site profile file 155 is as follows:
__________________________________________________________________________
TABLE NAME: SITE PROFILE ALIAS: ST
__________________________________________________________________________
ELEMENT/RECORD
DB TABLE ELE.
KEY
LEN
DEFINITION
__________________________________________________________________________
CLF Customer ID
ST.sub.-- CLF .sub.-- CUS.sub.-- ID
1 006
Uniquely identifies each customer.
Site ID ST.sub.-- SITE.sub.-- ID
2 006
Identifier to uniquely identify a site for a
customer.
Site Description
ST.sub.-- DESCRIPTION
E 030
Description of site
Corporate ID
ST.sub.-- CORP.sub.-- ID
E 006
Code for each different corporate profile
for a
customer
Geographic ID
ST.sub.-- GEO.sub.-- ID
E 006
Unique code for each different geographic
profile used
Modem Phone ST.sub.-- MODEM.sub.-- TEL
E 015
The phone number to be dialed for
communications.
Network ID ST.sub.-- NETWORK.sub.-- ID
E 004
The physical communication identifier
Data Type ST.sub.-- CHR.sub.-- TYP
E 001
Code to indicate if the site is ASCII or
EBCIDIC
data type
__________________________________________________________________________
Key Data:
Primary Key
(CLF Customer ID, Site ID)
Foreign Key
FK.sub.-- SITEA (CLF Customer ID)
References Customer Profile
On Delete Restrict;
Foreign Key
FK.sub.-- SITEB (CLF Customer ID, Corporate ID)
References Corporate Profile
On Delete Restrict;
Foreign Key
FK.sub.-- SITEC (CLF Customer ID, Geographic ID)
References Geographic Profile
On Delete Restrict;
__________________________________________________________________________
Indexes:
Name On Columns
Type of Work
__________________________________________________________________________
SITEIDX
CLF Customer ID
Primary, Ascending, Unique
Site ID
SITEIDXA
CLF Customer ID
Ascending
Corporate ID
SITEIDXB
CLF Customer ID
Ascending
Geographic ID
__________________________________________________________________________
Relationship to Other Tables:
Parent of:
User/Site Profile thru CLF Customer ID, Site ID
Site/Printer Profile thru CLF Customer ID, Site ID
Site/Group Profile thru CLF Customer ID, Site ID
Dependent of:
Customer Profile thru CLF Customer ID
Corporate Profile thru CLF Customer ID, Corporate ID
Geographic Profile thru CLF Customer ID, Geographic
__________________________________________________________________________
ID
Interrelated with the user profile 154 and the site profile 155 is the user/site data file 156. This relates a user to a site; a user can only access forms and perform functions as they relate to their accelerated site. A typical configuration of element 156 is as follows:
______________________________________
TABLE NAME: SITE/USER DATA ALIAS: SU
______________________________________
DB
ELEMENT/ TABLE
RECORD ELE. KEY LEN DEFINITION
______________________________________
CLF 1 006 Uniquely identifies
Customer ID each customer.
Site ID 2 006 Identifier to uniquely
identify a site for a
customer
User ID 3 006 The Logon ID associated
with each CLE user.
______________________________________
Key Data
Primary Key (CLF Customer ID, Site ID, User ID)
Foreign Key FK.sub.-- SUA (CLF Customer ID, User ID)
References User Profile
On Delete Cascade;
Foreign Key FK.sub.-- SUB (Clf Customer ID, Site ID)
References Site Profile
On Delete Cascade;
______________________________________
Indexes:
Name On Columns Type of Index
______________________________________
SUIDX CLF Customer ID
Primary, Ascending, Unique
Site ID
User ID
SUIDXA CLF Customer ID
Ascending
User ID
SUIDXB CLF Customer ID
Ascending
Site ID
______________________________________
Relationship to Other Tables:
Dependent of:
User Profile thru CLF Customer ID, User ID
Site Profile thru CLF Customer ID, Site ID
______________________________________
The group profile file 157 relates to groups of forms. A group is a particular combination of electronic forms, i.e. a segmentation scheme for the forms, grouped for the purpose of distribution to sites or different organizations. A typical configuration of the group profile file 157 is as follows:
__________________________________________________________________________
TABLE NAME: GROUP PROFILE ALIAS: GR
__________________________________________________________________________
ELEMENT/RECORD
DB TABLE ELE.
KEY
LEN
DEFINITION
__________________________________________________________________________
CLF Customer ID
GR.sub.-- CLF.sub.-- CUS.sub.-- ID
1 006
Uniquely identifies each customer.
Group ID GR.sub.-- GRP.sub.-- ID
2 006
Code to uniquely identify the distribution
group.
Group Sequence Number
GR.sub.-- GRP.sub.-- SEQ.sub.-- NBR
3 003
Sequence number to control level within a
group.
Group Description
GR-GRP.sub.-- DSC
E 030
Description of the distribution
__________________________________________________________________________
group.
Key Data:
Primary Key
(CLF Customer ID, Group ID, Group Sequence Number)
Foreign Key
FK.sub.-- GRPA (CLF Customer ID)
References Customer Profile
On Delete Cascade;
__________________________________________________________________________
Indexes:
Name On Columns Type of Index
__________________________________________________________________________
GRPIDX
CLF Customer ID
Primary, Ascending, Unique
Group ID
Group Sequence Number
__________________________________________________________________________
Relationship to Other Tables:
Parent of:
Site/Group thru CLF Customer ID, Group ID, Group Sequence Number
Group/Form thru CLF Customer ID, Group ID, Group Sequence Number
Dependent of:
Customer Profile thru CLF Customer ID
__________________________________________________________________________
Interfacing between the site profile 155 and the group profile 157 is the site/group data file 158. This assigns a group to a site--i.e. specific groups of forms are distributed to the sites they are associated with. A typical configuration of the file 158 is as follows:
__________________________________________________________________________
TABLE NAME: SITE/GROUP DATA ALIAS: SG
__________________________________________________________________________
ELEMENT/RECORD
DB TABLE ELE.
KEY
LEN
DEFINITION
__________________________________________________________________________
CLF Customer ID
SG.sub.-- CLF.sub.-- CUS-ID
1 006
Uniquely identifies each customer.
Site ID SG.sub.-- SITE.sub.-- ID
2 006
Identifier to uniquely identify a site for
a customer
Group ID SG.sub.-- GRP.sub.-- ID
3 006
Code to uniquely identify the distribution
group
Group Sequence Number
SG.sub.-- GRP.sub.-- SEQ.sub.-- NBR
4 003
Sequence number to control level within a
group
__________________________________________________________________________
Key Data:
Primary Key
(CLF Customer ID, Site ID, Group ID, Group Sequence Number)
Foreign Key
FK.sub.-- SGA (CLF Customer ID, Site ID)
References Site Profile
On Delete Cascade;
Foreign Key
FK.sub.-- SGB (CLF Customer ID, Site ID)
References Group Profile
On Delete Cascade;
__________________________________________________________________________
Indexes:
Name On Columns Type of Index
__________________________________________________________________________
SGIDX CLF Customer ID
Primary, Ascending, Unique
Site ID
Group ID
Group Sequence Number
SGIDXA
CLF Customer ID
Ascending
Site ID
SGIDXB
CLF Customer ID
Ascending
Group ID
Group Sequence Number
__________________________________________________________________________
Relationship to Other Tables:
Dependent of:
Site Profile thru CLF Customer ID, Site ID
Group Profile thru CLF Customer ID, Group ID, Group Sequence
Number
__________________________________________________________________________
The printer profile file 159 has information regarding the model and manufacture of each of the printers that will be controlled by the computers of the system 10. The typical configuration of the printer profile file 159 is as follows:
__________________________________________________________________________
TABLE NAME: PRINTER PROFILE ALIAS: PP
__________________________________________________________________________
ELEMENT/RECORD
DB TABLE ELE.
KEY
LEN
DEFINITION
__________________________________________________________________________
CLF Customer ID
PP.sub.-- CLF.sub.-- CUS.sub.-- ID
1 006
Uniquely identifies each customer.
Printer ID PP.sub.-- PTR.sub.-- ID
2 006
Code to uniquely identify each printer.
Printer Type PP.sub.-- PTR.sub.-- TYP
E 002
Code of printer type (see list below).
Printer Type Description
PP.sub.-- PTR.sub.-- DSC
E 015
Description of the printer and printer
type
Printer MFR Name
PP.sub.-- PTR.sub.-- MFR.sub.-- NME
E 020
Name of printer manufacturer
__________________________________________________________________________
Key Data:
Primary Key
(CLF Customer ID, Printer ID)
Foreign Key
FK.sub.-- PTRA (CLF Customer ID)
References Customer Profile
On Delete Cascade;
__________________________________________________________________________
Indexes:
Name On Columns
Type of Index
__________________________________________________________________________
PTRIDX
CLF Customer ID
Primary, Ascending, Unique
Printer ID
__________________________________________________________________________
Relationship to Other Tables:
Parent of:
Site/Printer Thru CLF Customer ID, Printer ID
Dependent of:
Customer Profile thru CLF Customer ID
__________________________________________________________________________
Printer Type Codes:
Code
Description
__________________________________________________________________________
HP HP PCL
H5 HP PCL 5
AF AFP
MF META FILE
DT DOT MATRIX
XC XICS
PS POSTSCRIPT
DC DOT MATRIX COLOR
__________________________________________________________________________
Interrelated with the site profile file 155 and the printer profile file 159 is the site/printer data file 160. Some forms will be printed at the user sites, while other forms will be printed by the vendor. The site/printer data file 160 is utilized only for those forms which will be printed by the user at the user's locations, which printers (e.g. 16) may have different printer formats. A typical configuration of the site/printer data file 160 is as follows:
__________________________________________________________________________
TABLE NAME: SITE/PRINTER DATA ALIAS: SP
__________________________________________________________________________
ELEMENT/RECORD
DB TABLE ELE.
KEY
LEN
DEFINITION
__________________________________________________________________________
CLF Customer ID
SP.sub.-- CLF.sub.-- CUS.sub.-- ID
1 006
Uniquely identifies each customer
Site ID SP.sub.-- SITE.sub.-- ID
2 006
Identifier to uniquely identify a site for a
customer
Printer ID SP.sub.-- PTR.sub.-- ID
3 006
Identifier to uniquely identify a printer
Printer Type
SP.sub.-- PTR-TYP
4 002
Code of printer type (see list below under
printer
profile)
__________________________________________________________________________
Key Data:
Primary Key
(CLF Customer ID, Site ID, Printer Type)
Foreign Key
FK.sub.-- SPA (CLF Customer ID, Site ID)
References Site Profile
On Delete Cascade;
Foreign Key
FK.sub.-- SPB (CLF Customer ID, Printer ID)
References Printer Profile
On Delete Cascade;
__________________________________________________________________________
Indexes:
Name On Columns
Type of Index
__________________________________________________________________________
SPIDX
CLF Customer ID
Primary, Ascending, Unique
Site ID
Printer ID
SPIDXA
CLF Customer ID
Ascending
Site ID
SPIDXB
CLE Customer ID
Ascending
Printer ID
__________________________________________________________________________
Relationship to Other Tables:
Parent of:
Distribution Profile thru CLF Customer ID, Site ID, Printer ID
Dependent of:
Printer Profile thru CLF Customer ID, Printer ID
Site Profile Thru CLF Customer ID, Site ID
__________________________________________________________________________
The distribution data file 161 is interrelated to the site/printer data file 160 and the form profile data file 162. The typical configuration of the distribution data file 161 is as follows:
__________________________________________________________________________
TABLE NAME: DISTRIBUTION PROFILE ALIAS: DP
__________________________________________________________________________
ELEMENT/RECORD
DB TABLE ELE.
KEY
LEN
DEFINITION
__________________________________________________________________________
CLF Customer ID
DP.sub.-- CLF.sub.-- CUS.sub.-- ID
1 006
Uniquely identifies each customer
FORM ID DP.sub.-- FRM.sub.-- ID
2 008
Code to uniquely identify a form for a
customer
SITE ID DP.sub.-- SIT.sub.-- ID
3 006
Identifier to uniquely identify a site for a
customer
Printer Type
DP.sub.-- PTR.sub.-- TYPE
4 002
Code of printer type (see list on printer
profile)
Printer ID DP.sub.-- PTR.sub.-- ID
5 006
Code to uniquely identify a printer
Release Code
SP.sub.-- RLS.sub.-- CDE
E 001
Code to indicate release action (see list
below)
Xmit Date DP.sub.-- XMIT.sub.-- DTE
E 008
Date the form was transmitted (released) to
the site
__________________________________________________________________________
Key Data:
Primary Key
(CLF Customer ID, Form ID, Site ID, Printer ID)
Foreign Key
FK.sub.-- DPA (CLF Customer ID, Form ID)
References Form Profile
on Delete Cascade;
Foreign Key
FK.sub.-- DPB (CLF Customer ID, Site ID, Printer ID, Printer
Type)
References Site/Printer Data
On Delete Cascade;
__________________________________________________________________________
Indexes:
Name On Columns
Type of Index
__________________________________________________________________________
DPIDX CLF Customer ID
Primary, Ascending, Unique
Form ID
Site ID
Printer ID
DPIDXA
CLF Customer ID
Ascending
Form ID
DPIDXB
CLF Customer ID
Ascending
Site ID
Printer ID
Printer Type
DPIDXC
CLF Customer ID
Ascending
Printer Type
__________________________________________________________________________
Relationship to Other Tables:
Dependent of:
Site/Printer Data thru CLF Customer ID, Site ID, Printer ID
Form Profile thru CLF Customer ID, Form ID
__________________________________________________________________________
Release Codes:
Code
Description
__________________________________________________________________________
0 Form is current
1 Form is new to distribution
2 Forms has been revised
9 Form is inactive (logically deleted)
__________________________________________________________________________
The form profile data file 162 has stored therein the elements of each form and characteristics of the form, e.g. descriptive information. Typically, a number of electronic forms will be stored therein that are identical except for printer formatting since it is necessary to be able to print the same form on a number of different types of printers. The necessary elements for recordation of each form include a unique identifier, a description of the form, the name of the software package (e.g DOCS) used to design the form, a code to indicate whether the form is new or revised, when the form was created and/or last revised, when the form is to be released and/or the previous release dates, the number of parts to the form, the code to identify whether it has a landscape or portrait orientation, the length of the form, and the width of the form. A typical configuration of the form profile data file 162 is as follows:
__________________________________________________________________________
TABLE NAME: FORM PROFILE ALIAS: FP
__________________________________________________________________________
ELEMENT/RECORD DB TABLE ELE. KEY LEN DEFINITION
__________________________________________________________________________
CLF Customer ID
FP.sub.-- CLF.sub.-- CUS.sub.-- ID
1 006 Uniquely identifies each customer.
Form ID FP.sub.-- FORM.sub.-- ID
2 008 Code to uniquely identify a form
for a customer.
Form Sub ID FP.sub.-- FRM.sub.-- SUB.sub.-- ID
3 003 Code to uniquely identify each
revision of the form.
Customer Catalog Number
FP.sub.-- CUS.sub.-- CAT.sub.-- NBR
E 015 Customers number to identify the
form.
Form Description
FP-Description E 030 Description of form.
Form Design Software
FP.sub.-- Design.sub.-- SFW
E 010 Software package used to design the
form.
Form Status Code
FP.sub.-- STA.sub.-- CDE
E 001 Code to indicate that the form is
new or revised.
Form Creation Date
FP.sub.-- CRE-DATE
E 010 Date form was created (from FAP).
Form Revision Date
FP.sub.-- REV.sub.-- DATE
E 010 Date form was last revised (from
FAP).
Form Release Date
FP.sub.-- RLS.sub.-- DATE
E 010 Date the form is to be released to
users.
Prior Release Date
FP.sub.-- OLD.sub.-- RLS.sub.-- DTE
E 010 Date of the previous release date
Category ID FP.sub.-- CTG.sub.-- ID
E 010 Code of form category to which a
form is assigned
FAP ID FP.sub.-- FAP.sub.-- ID
E 010 Unique identifier of the FAP that
created the form.
FAP Phone Modem Number
FP.sub.-- FAP.sub.-- TEL.sub.-- MODEM
E 015 Telephone number of the FAP modem.
Number of Parts
FP.sub.-- NBR.sub.-- PRT
E 003 Number of parts to the form.
Forms Orientation
FP.sub.-- ORT E 001 Code to identify landscape (L) or
portrait (P) mode.
Length of Form FP.sub.-- LEN E 008 Length of the form.
Width of the Form
FP.sub.-- WID E 008 Width of the form.
__________________________________________________________________________
Key Data:
Primary Key
(CLF Customer ID, Form ID, Form Sub ID)
Foreign Key
FK.sub.-- FPA (CLF Customer ID)
References Customer Profile
On Delete Cascade;
Foreign Key
FK.sub.-- FPB (CLF Customer ID, Category ID)
References Category Profile
On Delete Set Null;
__________________________________________________________________________
Indexes:
Name On Columns
Type of Index
__________________________________________________________________________
FPIDX
CLF Customer ID
Primary, Ascending, Unique
Form ID
Form Sub ID
FPIDXA
CLF Customer ID
Ascending
Category ID
__________________________________________________________________________
Relationship to Other Tables:
Parent of:
Distribution Profile thru CLF Customer ID, Form ID
Form Output Format thru CLF Customer ID, Form ID, Form Sub ID
Form Field Information thru CLF Customer ID, Form ID, Sub ID
Dependent of:
Customer Profile thru CLF Customer ID
Category Profile thru CLF Customer ID, Category
__________________________________________________________________________
ID
The category table file 163 is utilized to indicate the form category to which a particular form has been assigned. A typical configuration of the category table 163 is as follows:
__________________________________________________________________________
TABLE NAME: CATEGORY TABLE ALIAS: CT
__________________________________________________________________________
ELEMENT/RECORD
DB TABLE ELE.
KEY
LEN
DEFINITION
__________________________________________________________________________
CLF Customer ID
CT.sub.-- CLF.sub.-- CUS.sub.-- ID
1 006
Uniquely identifies each customer.
Category ID CT.sub.-- CTG.sub.-- ID
2 010
Code of form category to which a form is
assigned.
Category Description
CT.sub.-- CTG.sub.-- DSC
E 030
Description of form category.
Key Data:
Primary Key (CLF Customer ID, Category ID)
Foreign Key (FK.sub.-- CTA (CLF Customer ID)
References Customer Profile
on Delete Restrict;
__________________________________________________________________________
Name On Columns Type of Index
__________________________________________________________________________
Indexes:
CTIDX CLF Customer ID Primary, Ascending, Unique
Category ID
Relationship to Other Tables:
Parent of: Form Profile thru Category ID
Dependent of: Customer Profile thru CLF Customer ID
__________________________________________________________________________
Also interrelated with the form profile data file 162 are the usage statistics file 164, the form field information file 165, and the form output format file 166. A typical configuration of the usage statistics file 164 is as follows:
__________________________________________________________________________
TABLE NAME: USAGE STATISTICS ALIAS: STAT
ELEMENT/RECORD
DB TABLE ELE.
KEY
LEN
DEFINITION
__________________________________________________________________________
CLF Customer ID E 006
Uniquely identifies each customer.
Form ID E 008
Code to uniquely identify a form for a
customer.
Form Sub ID E 002
Code to uniquely identify each revision of
the form.
User ID E 006
The logon ID associated with each CLF user.
Printer Type E 002
Code of printer type (HP-PCL, Postscript,
etc.).
Site ID E 006
Identifier to uniquely identify a site for a
customer.
Date Used E 002
Date the form was used
Time Used E 002
Time the form was used
Number of Copies E 002
The number of copies printed at user
__________________________________________________________________________
site.
A typical configuration of the form field information file 165 used for form fill capabilities is as follows:
__________________________________________________________________________
NAME: FORM FIELD INFORMATION ALIAS: FF
__________________________________________________________________________
ELEMENT/RECORD
DB TABLE ELE.
KEY
LEN
DEFINITION
__________________________________________________________________________
CLF Customer ID 1 006
Uniquely identifies each customer.
Form ID 2 008
Code to uniquely identify a form for a
customer.
Form SUB ID 3 003
Code to uniquely identify each revision of
the form.
Field Number 4 003
Sequential number of fields within a form.
Field Name E 020
Name of the field
Data Description E 040
Concise description of data used in this
field
Field Length E 002
Describes the length of the field
Field Format E 005
Describes the field format.
Field Type E 001
Defines the field type. I.E. Numeric
Field Location E 040
The location of the data in the users file
Key Data:
Primary Key (CLF Customer ID, Form ID, Form Sub ID, Field Number)
Foreign Key FK.sub.-- FF (CLF Customer ID, Form ID, Form Sub ID)
References Form Profile
on Delete Cascade;
__________________________________________________________________________
Name On Columns Type of Index
__________________________________________________________________________
Indexes:
FFIDX CLF Customer ID Primary, Ascending, Unique
Form ID
Form Sub ID
Field Number
Relationship to Other Tables:
Dependent of: Form Profile thru CLF Customer ID, Form ID,
Form Sub ID
__________________________________________________________________________
A typical configuration of the form output format file 166 provides how the form is to be printed--the various print formats available. It is as follows (note that the output format of each form may be "source", "print ready" (and various versions), or "compiled"):
__________________________________________________________________________
NAME: FORM OUTPUT FORMAT ALIAS: FO
__________________________________________________________________________
ELEMENT/RECORD
DB TABLE ELE.
KEY
LEN
DEFINITION
__________________________________________________________________________
CLF Customer ID
FO.sub.-- CLF.sub.-- CUS.sub.-- ID
1 006
Uniquely identifies each customer.
Form ID FO.sub.-- FORM.sub.-- ID
2 008
Code to uniquely identify a form for a
customer.
Form Sub ID FO.sub.-- FRM.sub.-- SUB.sub.-- ID
3 002
Code to uniquely identify each revision of
the form.
Output Format Type
FO.sub.-- FRMT.sub.-- TYP
4 001
Code that describes from type S = Source C
= Compile
P = Print Ready
Printer Type
FO.sub.-- PTR.sub.-- TYP
5 002
Code of printer type (HP-PCL, Postscript,
etc.).
Form Format File ID
FO.sub.-- FILE.sub.-- NAME
E 012
File ID where form format data is stored.
DOS 8.3
Format.
Compression Indicator
FO.sub.-- COMPRESS.sub.-- IND
E 001
Code to tell if the form is compressed. Y =
Yes N = No
Key Data:
Primary Key (CLF Customer ID, Form ID, Form Sub IS, Output Format Type,
Printer Type)
Foreign Key FK.sub.-- FOA (CLF Customer ID, Form ID, Form Sub ID)
References Form Profile
On Delete Cascade;
__________________________________________________________________________
Name On Columns Type of Index
__________________________________________________________________________
Indexes:
FOIDX CLF Customer ID Primary, Ascending, Unique
Form ID
Form Sub ID
Output Format Type
Printer Type
Relationship to Other Tables:
Dependent of: Form Profile thru CLF Customer ID, Form ID, Form
Sub ID
__________________________________________________________________________
The security interface for all of the files is provided through menu file 167. A typical configuration of the file 167 is as follows:
__________________________________________________________________________
NAME: MENU ALIAS: MENU
__________________________________________________________________________
ELEMENT/RECORD
DB TABLE ELE.
KEY
LEN
DEFINITION
__________________________________________________________________________
Security Level 1 000
Defines the level of authority for each
user.
Program ID
Program Name
Program Desc
Screen Loc
Trans ID
Key Data:
Primary Key (CLF Customer ID, ????)
Foreign Key CATA (CLF Customer ID)
References Customer Profile
On Delete Cascade;
__________________________________________________________________________
Where desired, as a dependent of the group profile file 157, a group/form file may be provided associates forms to a group. The group/form file is illustrated at 169 in FIG. 12. A typical configuration of the group/form file, if utilized, is as follows:
__________________________________________________________________________
NAME: GROUP/FORM ALIAS: GF
__________________________________________________________________________
ELEMENT/RECORD
DB TABLE ELE.
KEY
LEN
DEFINITION
__________________________________________________________________________
CLF Customer ID 1 006
Uniquely identifies each customer.
Group ID 2 006
Code to uniquely identify the distribution
group.
Group Sequence Number 3 003
Sequence number to control level within a
group
Form ID 4 008
Code to uniquely identify a form for a
customer.
Key Data:
Primary Key (CLF Customer ID, Group ID, Group Sequence Number, Form ID)
Foreign Key FK.sub.-- GFA (CLF Customer ID, Group ID, Group Sequence
Number)
References Group Profile
On Delete Cascade;
__________________________________________________________________________
Name On Columns Type of Index
__________________________________________________________________________
Indexes:
GFIDX CLF Customer ID Primary, Ascending, Unique
Group ID
Group Sequence Number
Form ID
GFIDXA CLF Customer ID Ascending
Group ID
Group Sequence Number
GFIDXB CLF Customer ID Ascending
Form ID
Relationship to Other Tables:
Dependent of: Group Profile thru CLF Customer ID, Group ID,
Group Sequence Number
__________________________________________________________________________
After selection of the appropriate form and other information, the form is printed and/or displayed, as indicated schematically at 168 in FIG. 11. FIG. 12 contains the same basic information as FIG. 11, but shows the data base relationships for referential integrity purposes, and is self-explanatory. FIGS. 13a through 13i provide a detailed structure chart which shows the program-defined menu structure for the CLF 12. The interrelationship between the individual figures are specifically illustrated thereon, and the relationships between the various elements are self-explanatory from FIGS. 13a through 13i. Elements 190 are elaborated upon in FIG. 14. FIG. 14 illustrates the general flow for the release of forms from the CLF 12 to the end user sites 15 (190 in FIG. 13a). At 201, the CLF software periodically (e.g every weekday) polls the distribution profile for forms in the computer hosting the CLF to release electronic forms based upon release date (that is, if the release date has now been reached). At 202, the forms available for release are gathered. At 203, the communications software is alerted, and the forms are passed in as an input. At 204, the forms are transferred using the telecommunications infrastructure in place to the sites 15 (e.g. the PCs 154 thereat), as defined by the distribution profile. At 205, the receiving site communication software (e.g. OS/2, version 1.2) receives the forms. At 206, upon receipt of the forms, the applications software is alerted for processing of the transmission. The forms are preferably initially stored on disk. Ultimately, at 207, the applications software may direct the electronic forms to be printed at a printer (e.g. 16), to produce a paper form. FIG. 15 indicates the general flow for sending a form to one of the geographically remote user locations from the CLF 12. At 210 the program is initiated from the CLF 12 applications file 29. A session with the desired remote station or stations (locations) is allocated at 211, and all requested files are sent at 212. Confirmation that the files have been sent is provided at 213. Any data to be received from the remote location is received at 214, and receipt acknowledged at 215, before the program ends. FIG. 16 illustrates the general flow chart for sending a print request from CLF 12 to a remote user location having a printer, e.g. 16, for actually printing the form that was sent according to 210-213. The program is started from the CLF 12 applications software 29 at 217, a session is allocated with the remote location at 218, the print request is sent at 219 to the corresponding software at the remote location, and is confirmed at 220 before the program ends. It will thus be seen that according to the present invention a system and method have been provided for eliminating or minimizing warehousing, inventory, and obsolescence costs that a customer typically incurs in association with preprinted paper forms. Forms distribution costs are minimized, and the number of preprinted forms can be greatly minimized (for example the number of forms can be dropped from 20,000 to 5,000 in conventional operations). Centralized control is provided for electronic forms design, and the co-existence of a form in electronic and paper media is provided. Labor savings are achieved by eliminating redundant entry and processing of information by providing a centralized system, and where a customer desires, off load processing may be provided from the customer's main frame computer 34 to the vendor's computer (e.g. location of the FAP 14). Based upon geographic location, volume requirements, form construction (e.g. number of parts, MCP, etc.), and equipment profiles, exactly how paper forms will be constructed and delivered to end user sites 15 will be determined. The system as described above has numerous special applications, and it is impossible within the scope of a patent application to designate all possible uses of the system for particular functions and businesses. However a rough and general description of one particular implementation may serve to illustrate the versatility and functionality of the invention. A FAP 14 is provided at the vendor's facility, and is used to design electronic and preprinted forms, to control variable data fields for the electronic forms, and to control and directly communicate with the CLF 12 located on the customer's premises. Upon release of new forms or update of existing forms, the CLF populates the forms library containing appropriate form images and updates the appropriate tables with and control information. This file is sent to a software distribution resource in a main frame computer at a centralized location, which is central to a number of geographically remote user locations which it will service. Preferably, a main frame computer utilizes the customer environment; although | ||||||
