Oracle Validated Integration
GT eForms for PeopleSoft
Forms and workflow, built and run inside PeopleSoft. Configured by business analysts, approved on native AWE, written back to real records.
100 percent PeopleTools
No external runtime or separate database
Certified by Oracle
The only form builder with Oracle Validated Integration for PeopleSoft
100+ organizations
Universities, government agencies and enterprises, over 20 years
45 Second Video: Meet Max – just like your PeopleSoft users, he’s trapped by processes. Watch his transformation.
What GT eForms is
GT eForms is a form and workflow toolkit that runs inside PeopleSoft. Business analysts build forms through configuration rather than code. Approvals route on PeopleSoft’s native Approval Workflow Engine. Submitted data writes back to real PeopleSoft records, so there is no separate system to reconcile and no manual updates.
What GT eForms is used for
A sample of the processes teams have built. These are the published case studies — GT eForms runs at more than 100 organizations.

Read more →
Wakefern Food Corporation
Over 10,000 job change actions every week
Read more →
The University of Utah
200 hours of manual payroll processing eliminated
Read more →
University of South Carolina
15 Fluid eForms for HR self-service at go-live
Read more →
St. Joseph’s Health Care
Leader self-service for hires, job and position changes
Read more →
Xcel Energy
41 separate forms replaced by 3 intelligent eForms
Read more →
University of Oklahoma
Position descriptions neither Taleo nor PeopleSoft could handle
Read more →
University of California, Berkeley
Named a PeopleSoft Innovator for student and instructor forms
Read more →
Rochester Institute of Technology
PDF-based forms replaced across the student information system
Read more →
Princeton University
Student records front end rebuilt before the old server went dark
Read more →
University of Wisconsin–Madison
Student financial aid moved off paper
Read more →
College of the Holy Cross
Language placement automated across eight languages
Read more →
North Dakota University System
120+ forms built in one year across 11 campuses
Read more →
University of South Carolina
Two-thirds of 3,800 journal vouchers processed automatically
Read more →
University of Oklahoma Health Sciences Center
Grant proposals and agreements routed end to end
Read more →
State of North Dakota
$500,000 of legislative funding across 63 agencies
Inside PeopleSoft, not beside it
GT eForms adds capability to the environment you already run. It does not sit alongside it as a second system to secure, integrate and reconcile.
Built on PeopleTools
100 percent PeopleTools based. No external runtime, no separate database, no additional infrastructure to operate.
Oracle Validated Integration
The only form builder certified by Oracle for PeopleSoft.
Native approvals
Approvals run on PeopleSoft’s Approval Workflow Engine, using the routing and delegation your administrators already know.
Real records
Submitted data updates PeopleSoft components through supported interfaces, not a parallel data store.
Your security model
Access is governed by PeopleSoft permission lists and roles. There is no second set of user accounts to administer.
Scales with your environment
Supports user populations into the tens of thousands. Current PeopleSoft releases are supported; see the documentation for specifics.
When the process reaches past PeopleSoft
For workflow that spans PeopleSoft, Oracle Cloud and third-party systems, GT eFlow is the platform built for it — same team, same support.
Build, route, write back
Three steps, all of them inside PeopleSoft.
Configuration, not code
The form type designer is where conditional logic, dynamic data and participant lists get set. No PeopleCode, no separate build pipeline.
Your approval engine, not ours
Routing runs on PeopleSoft’s Approval Workflow Engine, with the delegation and notification your administrators already operate. Ten definitions are delivered.
One system of record
Submitted data updates PeopleSoft components through messaging queues. Nothing is rekeyed, and nothing lives in a parallel store waiting to be reconciled.
What you build with it
The parts a business analyst works with directly. Each is configured, not coded.
Fields populate from the source, not from a re-entered copy
A SmartSource reads live PeopleSoft data into the form as it opens, so the request carries the same values the record does.
Show, hide and branch — without writing code
Visual If sets the rule in the designer. The form reshapes itself around the answer as the requester fills it in.
Participant lists that decide who acts, and when
A roster resolves to people by role, so routing keeps working when someone changes jobs, leaves or delegates.
Caught on the way in, not sent back afterwards
Field-level rules raise an inline message at entry, so a request is corrected before submission rather than returned days later.
Ten delivered routing patterns you can mix and match
The common shapes — serial, parallel, conditional, self-approval bypass — ship as AWE definitions. Start from one, combine them, and configure them to meet your own approval requirements, rather than building routing from scratch.
…and six more, listed in the documentation.
The processes that never got modernized
Most organizations implemented PeopleSoft for their core transactions and stopped there. The work around the edges kept running the way it always had.
Work runs outside the system
Requests that PeopleSoft was never configured to handle still move on paper, email attachments and shared spreadsheets.
Approvals leave no trail
A request is approved by forwarding a message. No routing rule, no audit record, no reliable way to answer where something is.
Results get rekeyed
Someone retypes the outcome into PeopleSoft. That step is where transcription errors and processing delays enter the process.
The request is a PeopleSoft form
The same request runs as a configured eForm, with live PeopleSoft data in the fields and rules that stop bad entries at the door.
Approvals are routed and recorded
AWE carries the request through its steps. Every decision has a rule behind it and an audit record after it.
The record updates itself
Submitted data writes back to PeopleSoft components. Nobody retypes anything, so nothing drifts.
By module
Where teams apply it
Human Capital Management
Onboarding, job and position changes, leave and status requests, personal data updates.
GT eForms for HCM
Finance and Supply Chain
Requisitions, expense and payment approvals, vendor and supplier record maintenance, ChartField requests.
GT eForms for FSCM
Campus Solutions
Admissions processing, grade changes, academic petitions, registration exceptions, faculty requests.
GT eForms for Campus Solutions
Customers
What teams report
See GT eForms in action
Watch a business analyst configure a PeopleSoft form, route it for approval and write the result back to a record.
See GT eForms in your environment
Schedule a demonstration against the processes you are trying to move off paper.
- The only form builder certified by Oracle for PeopleSoft
- 100+ organizations, including universities, government agencies and enterprises
- Over 20 years serving the PeopleSoft community
- Training, documentation, a user community and AI assistance included
Request a demonstration
Questions
Frequently asked questions
What is GT eForms?
GT eForms is a form and workflow toolkit for PeopleSoft. It lets business analysts build electronic forms through configuration, route them for approval on PeopleSoft’s Approval Workflow Engine, and write the submitted data back to PeopleSoft records. It runs entirely inside the PeopleSoft environment.
How is GT eForms different from PeopleSoft Forms and Approval Builder?
PeopleSoft’s delivered Forms and Approval Builder covers straightforward forms with simple approval routing. GT eForms is built for processes that need more than that: conditional logic, live PeopleSoft data drawn into the form, participant lists, field-level validation and updates written back to PeopleSoft components. Both run inside PeopleSoft. The difference is the complexity of process each is designed to carry.
Do I need developers to build forms?
Business analysts build and modify forms without writing code. Organizations building forms that update PeopleSoft records in more complex ways often involve a developer for that part of the configuration. Customers describe both patterns, and many teams run a mix of the two.
Does GT eForms store data outside PeopleSoft?
No. GT eForms is 100 percent PeopleTools based. Form data lives in your PeopleSoft database, and submitted data updates PeopleSoft components through supported interfaces. There is no external runtime, separate database or third-party hosting to secure and audit.
Which PeopleSoft versions does GT eForms support?
GT eForms supports current PeopleSoft releases. Supported releases and minimum PeopleTools levels change as Oracle publishes new versions, so the current supported combinations are listed in the product documentation rather than here.
How long does it take to build a form?
Minutes and hours, not days or weeks. A straightforward form with standard routing can be configured in a single sitting. Forms carrying complex conditional logic, or writing back to several PeopleSoft components, take longer and often involve a developer.
Can people without PeopleSoft accounts take part in a workflow?
Yes. GT Tokens give external participants such as parents, vendors and board members secure access to the specific transaction they need to act on, without provisioning a PeopleSoft account for them. Access is controlled at the transaction level.
How do forms move from a test environment to production?
The Transporter tool migrates forms between environments and provides an API for teams that automate their release process. The Dependency Network Visualizer shows what a form depends on, and what depends on it, before a change is promoted.
What is GT eForms not designed for?
GT eForms is for processes that belong in PeopleSoft and act on PeopleSoft data. It is not a general-purpose survey tool, a public website form builder or a workflow engine for systems outside PeopleSoft. For enterprise workflow spanning systems beyond PeopleSoft, GT eFlow is the relevant product.