📄️ Attachment Administration
Purpose: Attachments are an optional, supported feature of GT eForms. These pages aid in defining the default attachment setup data for all forms. Settings can be further refined per form type within Form Setup.
📄️ AWE Setup
Approval Workflow Engine (AWE) Setup allows users to create multiple Definition IDs within a custom Process ID at one time. This tool uses the same criteria and functionality as PeopleSoft Approval Framework.
📄️ Content Reference Naming
The framework is set to only show/hide GT eForm links in the WorkCenter, or Fluid side panel, based on participation rosters. Sometimes you may want to manually create navigation links (Content References) using your custom naming conventions, rather than GT eForm link naming conventions, and want participation rosters to hide/show those custom links. To make this possible, a setup table is available that indicates where you can configure the prefix for your naming convention.
📄️ Email URL Override Table
The Email URL Override Table is used to set up redirect URLs for eForm links (evaluate, update and view). If the target environment has one or more separate portals than default Peoplesoft, the Email URL override table allows URL parameters to be defined for the separate portals so when email notifications are sent out, the eForm links (evaluate, update and/or view) will point to the correct portal, and not default Peoplesoft. The URL Override Type for the default portal will automatically be filled in based on the environment the first time an email is generated if a separate portal is not defined. Use the URL Override Type tab to define additional override types, such as a public portal, for example.
📄️ Form Admin Tool Security
Form Admin Tool Security allows users to control access to the Form Admin Tool and its segments as shown on the Form Admin Tool page. The access is based on permission lists and can be controlled at the Form Type and Form Condition levels.
📄️ Form Family Table
The Form Family Table is a setup table that holds form family definitions. Form types that have similar traits and attributes can be grouped under the same family definitions. In this way, they can share a Home Page structure, search lookups, edit and business rules, setup tables, and more.
📄️ Form Installation Table
The Form Installation Table can be used to change the eForm ID numbering as well as to change user access on the GT eForms Debugging tool.
📄️ Form Key Update Utility
The GT Form Key Update Utility was created to provide an easy way to retroactively update form keys after form search configuration and/or form search records were changed.
📄️ Message Catalog Security Setup
The objective of this message catalog utility is to limit access to update certain message catalogs. With the delivered message catalog that PeopleSoft provides, if a user has access to the component/page, the user can update any message catalog set. GT created a utility that allows limited access to the message catalogs so forms builders/business analysts can create and update a restricted list of message sets for use within GT eForms.
📄️ Navigation Button Defaults
The Navigation Button Defaults setup page allows functional users to define the default buttons and their settings for all Form Types using Helium Performance in GT eForms Framework version 3.58.00 and later. Any changes made on this page will apply to the GT Framework, meaning it will impact all form types and form tasks that use Helium Performance and default buttons. If a functional user desires to change the button settings for a specific form type and task, they can navigate to Form Setup and go to the Pages tab to override the default buttons for that task on the selected form type. See the Pages Tab feature document for more information.
📄️ Robot Setup
If you have a situation that requires a human user to keep forms in a queue and periodically check if they can be acted upon, then configuring a robot approver can help you! The Robot Setup page is used to configure an automated evaluator where the rules for taking action (approve, deny, etc) can be defined through GT’s Visual Ifs. We lovingly refer to our robot as Rosie the Robot. Rosie can do anything if a form is routed to her user ID and a visual if is configured for her to know when to act on the form. She can be the only user the form routes to, or she can be included among other users in the form’s workflow roster. Below are some sample use cases when you might want to have forms routed to Rosie and wait for her to take action on your forms.
📄️ Search Configuration
By default, search pages will be made up of a combination of General, Form, and Search Record fields, as applicable. The Search Page Configuration can be modified by using the Search Configuration tool.
📄️ Search Sets Setup
Search Sets are an optional way to group form types together. Using search sets, form types from different form families can be grouped together and a new landing page, security, and search records can be applied to the search set.
📄️ Test Mode Setup
Test Mode Setup allows form administrators to specify special test users on a form-by-form basis. This setup table can be used in conjunction with the Test Mode User Visual If part (or other custom code) to grant users specific access to various sections of the form for testing purposes. For example, you can use Test Mode User to restrict the CI segments page to testers or administrators.