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.
Navigation: Manage GT eForms 3.x > GT Functional Setup > GT System Setup > Form Installation Table
GT eForms Install
Various pieces of information relating to the setup of the GT eForms™ application are found on this tab.
| GT eForms Installation Settings |
|---|
 |
| Field | Value/Use |
|---|---|
| Framework Version | Displays the version of GT eForms currently installed. |
| Last eForm ID | The last number assigned to an eForm. When a new form is created, the next number is generated via the formula of the current “Last eForm ID” plus 1. To adjust the numeric range of your eForms, simply change the number. Note: Decreasing the Last eForm ID value is not advised without first considering the impact of forms already existing in the environment. |
| eForm Default Setid | For backward compatibility. Newer clients do not need to populate this field. |
| eForm Default Business Unit | Optional field to default Business Unit if there is ONE that is used across all of the users. Otherwise, leave it blank. |
| PeopleSoft Product Installed | Optional value that displays the environment’s Application Version. |
| Unique Key Num | This value is used by the code to generate the Unique Keys for GT eForms™ 3.0. This number can be reset to 1 in new environments. In an existing environment, this value should not be changed. |
| Long Data Chunk Size | Set Long Data Chunk Size to the number of bytes/characters per chunk you decide you want. If you click on the “Load from PSOPTIONS” button, it will load the chunk size that is used in your environment for PeopleSoft file attachments. |
| Long Data Key | This value is used by the Long Data code to generate the Unique Keys for the G3FORMLIST table. This number can be reset to 1 in new environments. In an existing environment, this value should not be changed. |
| Override Email Address | If populated, all GT email notifications are sent to this email address. |
| Default Reply To Email | If populated, all email notifications sent will show this email as the sender. If the user hits Reply from the email, their email will also be sent to this address. |
| Send Notifications based on User Workflow Routing Preference | Check this box to force the Framework to review the Workflow Routing Preferences of the user. If an email is attempting to be sent to a user without Email User checked in their profile, the email will not generate. |
| Send emails through Integration Broker (SMTP Guarantee) | Sends Emails generated by GT eForms through the Integration Broker when this box is enabled, else send emails via GT eForms 3.x. When the checkbox is enabled, use the Asynchronous Services page to review the 'email sent' status, else use the Notification Log page on the GT Form Tool. |
| System Application Package | Packages used for technical parts or hooks across any form types, families, or search sets. |
| Allowed Query Record Action(s) | Determines which users will be able to build query records. This setting is at the Framework level. The four options available in the dropdown are: Allow Both, Allow Build, Allow Script, or None. |
| GT eForm Product Name | Lists the description of the current project versions installed. |
| Tools Analytics (checkbox) | Value tells the Tools Analytics utility to reference this Project when doing its analysis. |
| Project Name | Lists the names of the current project versions installed. |
| Open-Source Attributions | Opens a modal window that attributes open-source libraries GT eForms uses. See below for more details. |
Open-Source Attributions Details
These are the libraries in use:
- QuillJS for Rich Text Fields
- VisJS vis-network for Network Visualizer
- The OWASP Java HTML Sanitizer library to mitigate cross-site scripting risk in Rich Text Fields
- Additional Jar java libraries that OWASP depends on