Design Proposal for a Form Processing Web Application to Implement Numerous Forms Larry Guentert, HRIS April 17, 2011

Today’s Agenda Motivation for Project Basics of Form Processing Roles of Form Processing Description of Goals What’s Under the Hood Brief Demo Questions?

Motivation for Project Department is floating in paper processing forms

Basic Form Processing Aspects of a typical form:  Collection of information  Identification of User / Requestor  Approval Information / Identification  Processing Information

Roles Associated with Form Typical Roles for Processing Requester: person initiating request Reviewer of information: Approver: one (or several) Processor: person who implements request

Goals of this Implementation Store form data in a generic way Have Role-based access to system Requester Reviewer Approver(s) Processer Developer Separate out aspects unique to each form into separate tables

Goals of this Implementation Main Form Data table consists of: 12 Text fields (varchar) 6 Dates fields 35 Decimal fields (for financial data types) 6 Integer fields (for flags) Designed to hold typical information found on forms.

Goals of this Implementation Data Captured (Request side): Auditing information (who, what, when) Request Status information (for tracking) 35 Decimal fields (for financial data types) 6 Integer fields (for status flags)

Goals of this Implementation Data Captured (Role Side): RequestApproverStatus All person information for those that interact Permission information for associated roles

What’s Under the Hood Summer PayCalc consists of: –SQL Server Database Tables 14 –7 Stored Procedures Coldfusion Scripts (~60) One automated SAP Query refreshes data in one table nightly.

What’s Under the Hood: Tables Tables unique to each application Tables used by all forms

Next Steps for this Project Test, Test, Test ITAP Security Scan User Training/Documentation Push to Production Go Live

Brief Demo

Questions? Thank you!