1 / 14

Design Proposal for a Form Processing Web Application to Implement Numerous Forms

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?.

xanti
Download Presentation

Design Proposal for a Form Processing Web Application to Implement Numerous Forms

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. 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?

  3. Motivation for Project Department is floating in paper processing forms

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

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

  6. 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

  7. 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.

  8. 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)

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

  10. 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.

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

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

  13. Brief Demo

  14. Questions? Thank you!

More Related