True, the University of Oklahoma and Gideon Taylor partnered together to update OU's current GT2 EPaf solution to the new GT 3.30 framework. This EPaf solution contained eight different forms to aid in personnel action requests. One of these forms is the Additional Pay e-form, which is used to issue a payment unrelated to the employee's base pay. The request for additional payments can be started by any initiator, but the department responsible for paying the employee must be one the initiator has access to. The solution was designed to be flexible yet efficient, as it combined two campuses' business processes into a single form. To get started, the initiator opens the EPaf homepage and searches for the employee they wish to request the payment for. Once the employee is located, they click on the green arrow to display the available actions and select "Add Additional Payment". The Additional Payee form opens, and at the top, the header displays the employee's name, employee ID, and employee record. The "View Job Data" button can be clicked to view the employee's current job details. The "Additional Pay Details" segment requests payment details from the initiator. The "Pay Period End Date" dropdown is based on a custom view that initializes with the current pay period's end date, but also displays the next two future pay periods and dates as options for the payment form. The form pre-population displays the employee group and home department for reference. If the initiator does not have access to the employee's home department through department security, a warning message appears asking the initiator to choose a department in which they have access to for this payment. The "Earnings Code" prompt is controlled by a setup table where the settings for earning codes are defined based on employee's company and employee group....