GT eForms 3.70.00 Upgrade Guide

GT delivers this Upgrade to all customers who are on active subscription or annual maintenance. This upgrade, like most modifications, contains potentially data destructive processes. The steps in this document must be followed and verified exactly to ensure that existing form data is not deleted from the environment. This document and its accompanying installation were designed for systems running GT eForms 3.58.00/3.58.01/3.58.02/3.58.03/3.58.04. If you are currently on a prior version, you must upgrade to 3.58.00 prior to following these instructions. Please contact the Help Center for assistance if needed. If you have any kind of post 3.58.00 customizations or extensions, you must contact the Help Center at support@gideontaylor.com.

Installation Package

The installation package includes the following directories:

• Docs - Installation instructions
• Projects - Application Designer project(s)
• Scripts - DMS script(s)
• Data - Data files for the DMS script(s)
• Logs - Log files for the DMS script(s)

The packages are located in the Online GT Library. Contact support if you need assistance gaining access to this site.

General Installation Instructions

IMPORTANT

It is always wise to make backups before importing new projects or adding a new product, but this guide contains no backup instructions or tasks.

Project Definition

1. Copy the Projects/G3FRM37000_UPG_V01 project from file to the target environment.

   • Be sure you use the file definition when copying the project into your environment and NOT the database definition if one exists.

2. Verify all done flags have been checked and review the copy log to ensure there are no errors.

3. Build all records and make sure that the following build options are checked:
   WARNING: do NOT do a destructive create or alter on these tables as data loss can occur.

   • Build Options:
     1. Create Tables
     2. Alter Tables
     3. Create Views
     4. Execute and build script
   • Recommended for DB2 Databases: Rebuild all GT views in case they depend on altered tables.
     1. Create a project with all the G3 and G_ views in your environment.
     2. If you have any G_ materialized views created for your eForm solutions, they can be excluded from the project as they are essentially tables. You can use this page to identify materialized views in your environment:
        PeopleTools > Utilities > Administration > Materialized Views > Enable Materialized Views
     3. Build the project with the following build options checked:
        1. Create Views
        2. Execute and build script

4. Compile Directive PeopleCode by completing the outlined steps for the following application classes:

   • G3FORM_NAV:StepPage
   • G3FTT:FTTValidations
   • G3SEARCH:Search
   
   
   1. Open the application package/class
   2. Add a space at the very beginning of the class
   3. Save and close the class

5. Copy the Projects/G3FRM37000_DEL_V01 project from file to the target environment.

   • Be sure you use the file definition when copying the project into your environment and NOT the database definition if one exists. This project will delete objects that were included in the initial 3.58.xx install/upgrade project that have since been deprecated.

6. Copy the Projects/G3FRM37000_CLT_OBJS project from file to the target environment, if it does not already exist in the environment.

   • This project includes objects that are delivered with the G_ naming convention to indicate they are designed to be modified as part of solution development if needed. They will not be included in future release packages.

7. Copy the G3FRM37000_COMPLEX_VIEWS_V01 project from file to the target environment, if it does not already exist in the environment.

   • Verify all done flags have been checked and review the copy log to ensure there are no errors.
   • Build all records and make sure that the following build options are checked:
     • Create Views
     • Execute and build script

DMS Script

There is a script provided in the upgrade: G3FRM37000_UPG_V01.dms. It needs to be run at install following the steps below.

1. Update the [FILEPATH] for the input and log files for the Script found in Scripts/G3FRM37000_UPG_V01.dms

2. Run the Scripts/G3FRM37000_UPG_V01.dms script. This will import the Framework configuration and message catalog entries for this upgrade.

   1. Important: If you have customized any GT delivered items in Message Catalog set 24842, be sure you re-apply these customizations after running this import DMS.
   NOTE

   This DMS contains delete statements for deprecated objects. If error messages for the objects (PS_G3DEF_MOD_LINE, PS_G3DEPBLD_MG_TBL, PS_G3FRM_EDT_SS_VW, PS_G3SRCH_FLDS) appear, they can be safely ignored, as the objects have already been removed from the environment.

Deploy Form Transporter

1. Navigate to Manage GT eForms 3.x > GT Technical Setup > Form Transporter Utilities. Go to the Form Transporter Deployment tab, and there will now be an updated version of the Standby Transporter UI. Deploy the Transporter using the button below the grid to update the Transporter Version.

Run the 3.70.00 System Maintenance Process

1. In the PIA, navigate to Manage GT eForms 3.x > GT Technical Setup > System Maintenance. Select the dropdown and choose the "eForms 37000 Updates". Once presented with the page shown below, select the "Run All" button to start the process.

NOTE

For Helium Form Types, the form build and this process replaces the "Load Custom Parts" process. The "Load Custom Parts" process is deprecated to only being needed/used for Standard Forms.

Build All Helium Form Types

If you have Helium Form Types, navigate in the PIA to Manage GT eForms 3.x > GT Utilities > Form Builder Utility to build all the Helium Form Types. After entering a Run Control ID of your choosing, be sure all Form Types are selected, and Run. More information about the Form Builder Utility can be found in its respective documentation.

Import GT Query Tree

1. Navigate to the GT Import Tree utility: Manage GT eForms 3.x > GT Utilities > Import Tree.

2. Copy the tree file to import utility.

   1. Open the G3FRMWRK_QRY_TREE.TXT file with any text editor. This is an export of the framework tree.
   2. Copy the contents of the tree file to the text editor clipboard.
   3. Paste the contents into the "Tree File Content" long edit box.
   IMPORTANT

   Make sure that the paste maintains all the structure in the original text file.

3. Click the "Import Tree" button. Note: Several informational message boxes should appear. Among the expected messages are:

   1. The Tree Structure Already Exists: ACCESS_GROUP. (125,51)
   2. PeopleSoft TreeMover Completed Successfully. (125,4)

Form Types Converted to Helium

If you have Form Types in your environment that have been converted from Standard to Helium Performance, you will need to perform two additional tasks. See Helium Form Conversion Notice for more information on why these steps are needed. Run the following query to find out whether you have Form Types that were converted to use Helium Performance.

SELECT
    ftt.g3form_type
FROM
    ps_g3form_type_tbl ftt
WHERE
    ftt.g3helium_perform = 'Y'
    AND EXISTS (
        SELECT
            'x'
        FROM
            ps_g3formlist fl
        WHERE
            fl.g3buffer_orig_key <> ' '
            AND fl.g3form_type = ftt.g3form_type
    );

If the query shows that you have Form Types that were converted to Helium Performance, you will need to do the following:

1. Run "HeliumConversionFix" System Maintenance process to resolve issues on form transactions that have been converted previously
   1. Navigate to Manage GT eForms 3.x > GT Technical Setup > System Maintenance
   2. Select the HeliumConversionFix group
   3. Click 'Run All'

Additional Documentation

See the System Maintenance documentation for additional instructions on how to use the System Maintenance tool.

1. Convert remaining Standard form transactions.
   • Read the Conversion Tool feature document for instructions on how to do this.

Environment Processes

The following steps do not have to be run immediately but should be run before general usage.

• Navigate to PeopleTools > Portal > Portal Security Sync and run the process for the Portal where GT eForms is installed.
• Navigate to PeopleTools > Portal > Portal Utilities > Sync Nav Collection Security and run the process for the Portal where GT eForms is installed.
• Shut down the application server.
• Clear the application server cache.
• Restart the application server(s).
• Restart the PUB/SUB server(s). (This must be done to ensure new IB services/operations are registered)

Contact GTC

If you have questions, contact support@gideontaylor.com