GT eForms Versioning Behavior

GT eForms updates various version tables in PeopleSoft as it is used. This document explains what users should expect to see in PeopleSoft version tables as they use the GT eForms framework.

AFFECTED TABLES

These are some of the version tables that exist in PeopleSoft and the times when a user can expect to see them updated by GT eForms.

Version Table Groups	Incremented by GT
PCM, PGM	Never
XTM, PDM lock and version tables	Only for new char fields between 1-4 characters
RDP	Always for new/changed fields and records
SRM	Always for multi-field prompts (dynamic view records)
SYS	Whenever a user makes a change to form configuration with GT eForms.

These are the actions a user can perform with GT eForms that update versions in PeopleSoft. A user can check version synchronization after performing these actions to make sure the versions are synchronized.

Standard Form Types:

• Create a GS Segment Record
  • This can happen when a user creates or updates a segment and saves it
  • This can also occur after a user imports a form type into an environment (If the "Build SmartSources and GS Records/Fields on Import" button is checked in the Transporter Setup menu)
  • May occur when a user performs actions in the deprecated "Data Management" menu
    • We do not recommend using this deprecated tool. If users must do so, we recommend checking version synchronization after using the tool.

NOTE

Occasionally, a user may wish to turn off the "Build SmartSources and GS Records/Fields" checkbox before importing a form type – usually because they are troubleshooting the form. If this is the case, it is possible to build those objects later from the "Form Utilities" menu by clicking the "Rebuild Form Objects" button next to the imported form type.

Helium and Standard Form Types:

• Create a GS Field
  • This happens when a user creates a new field in Form Setup by typing a label and allowing the framework to automatically generate a new ID for the field
  • Importing a form type or rebuilding a form type may also complete this action
  • The deprecated Data Management tool can trigger this action (not recommended)
• Create or Drop Query Records
  • Synchronizing Query Record structure from the Query Records page in Form Setup after making changes to the form's setup may trigger this action
• Create Multi-Field Prompt Records
  • This may occur when a user sets a field as a multi-prompt field and saves the field configuration
  • Importing a form type or rebuilding a form type may also complete this action
  • The deprecated Data Management tool can trigger this action (not recommended)

VERIFYING SUCCESSFUL OPERATION

The following guidelines will be helpful in validating versioning after transporting an eForm from one environment to another.

1. Run the query found in Appendix 1.
2. Verify that the following rules are true of the query results. If they are true, then version numbers have been correctly incremented.
   1. psversion and pslock must be in sync for the same objecttypename
   2. psversion and pslock >= max(meta and meta-del tables)
      1. psversion and pslock = max(meta and meta-del tables)
         1. PCM
         2. RDM

APPENDIX 1

Use the following SQL Query to check PeopleSoft version numbers.

SELECT 'RDM-meta-rec',
       max(VERSION)
FROM PSRECDEFN
UNION
SELECT 'RDM-meta-rec-del',
       max(VERSION)
FROM PSRECDEL
UNION
SELECT 'RDM-meta-field',
       max(VERSION)
FROM PSDBFIELD
UNION
SELECT 'RDM-psversion',
       VERSION
FROM PSVERSION
WHERE objecttypename = 'RDM'
UNION
SELECT 'RDM-pslock',
       VERSION
FROM PSLOCK
WHERE objecttypename = 'RDM'
UNION
SELECT 'SRM-meta',
       max(VERSION)
FROM PSSQLDEFN
UNION
SELECT 'SRM-meta-del',
       max(VERSION)
FROM PSSQLDEL
UNION
SELECT 'SRM-psversion',
       VERSION
FROM PSVERSION
WHERE objecttypename = 'SRM'
UNION
SELECT 'SRM-pslock',
       VERSION
FROM PSLOCK
WHERE objecttypename = 'SRM'
UNION
SELECT 'PCM-meta',
       max(VERSION)
FROM PSPCMPROG
UNION
SELECT 'PCM-meta-del',
       max(VERSION)
FROM PSPCMPROGDEL
UNION
SELECT 'PCM-psversion',
       VERSION
FROM PSVERSION
WHERE objecttypename = 'PCM'
UNION
SELECT 'PCM-pslock',
       VERSION
FROM PSLOCK
WHERE objecttypename = 'PCM'
UNION
SELECT 'PGM-meta',
       max(VERSION)
FROM PSPNLGRPDEFN
UNION
SELECT 'PGM-meta-del',
       max(VERSION)
FROM PSPNLGRPDEL
UNION
SELECT 'PGM-psversion',
       VERSION
FROM PSVERSION
WHERE objecttypename = 'PGM'
UNION
SELECT 'PGM-pslock',
       VERSION
FROM PSLOCK
WHERE objecttypename = 'PGM'
UNION
SELECT 'PDM-meta',
       max(VERSION)
FROM PSPNLDEFN
UNION
SELECT 'PDM-meta-del',
       max(VERSION)
FROM PSPNLDEL
UNION
SELECT 'PDM-psversion',
       VERSION
FROM PSVERSION
WHERE objecttypename = 'PDM'
UNION
SELECT 'PDM-pslock',
       VERSION
FROM PSLOCK
WHERE objecttypename = 'PDM'
UNION
SELECT 'XTM-meta',
       max(VERSION)
FROM PSXLATDEFN
UNION
SELECT 'XTM-meta-del',
       max(VERSION)
FROM PSXLATDEFNDEL
UNION
SELECT 'XTM-psversion',
       VERSION
FROM PSVERSION
WHERE objecttypename = 'XTM'
UNION
SELECT 'XTM-pslock',
       VERSION
FROM PSLOCK
WHERE objecttypename = 'XTM'
UNION
SELECT 'SYS-psversion',
       VERSION
FROM PSVERSION
WHERE objecttypename = 'SYS'
UNION
SELECT 'SYS-pslock',
       VERSION
FROM PSLOCK
WHERE objecttypename = 'SYS' ;

NOTE

Users may also employ the following query to check ALL psversion tables:

select * from psversion order by objecttypename;