Skip to main content

Form Transporter 2.25 Release Notes

This document announces the release of version 2.25 of the Form Transporter.

Installation Prep​

How should you prepare to install this Release?

  • Review these Release Notes in their entirety.
  • Carefully review all Installation Instructions (IMPORTANT, very important).
  • Contact the GT Support Center with any questions. We are here to help.

Installation​

IMPORTANT

Target Version Required: There are two target version for this release as follows:
GT eForms Framework 3.14.15
GT eForms Framework 3.10.01 with the Transporter Installed

Warning: Do not install this on a Multilanguage Beta version.

This release does require that your environment be at a minimum of 3.10.01. If you have 3.14.15, no additional steps are required before applying this release of the transporter. If you have 3.10.01, you must have already installed the Transporter for version 3.10.01.

Initial Project Load​

  1. Login to Application Designer.
  2. Copy the Form Transporter project below:
  3. G3TRANS225_ALL_V01
  4. Verify that all objects copied as expected by reviewing the “Done” flags.
  5. Do the following for all projects that were installed:
  6. Open the project.
  7. Build the project (Build > Project) with the following options:
    1. Create Tables. This will select “Create Indexes” by default.
    2. Create Views.
    3. Alter Tables.
    4. Execute and build script.

Run Data Mover Scripts​

For Version 3.14.15 Only

The DMS script is only needed if you are on version 3.14.15. Please do not use this if you are in 3.10.01; it is not needed.

  1. Use IMPORT script G3TRANS225_UPG_IMP.DMS.
  2. Use DAT file G3TRANS225_UPG.DAT.
  3. Update the directory settings for the log and the dat file in the script.
  4. Run the script.

New Features​

NOTE

Transporter patch version 2.25 is a rollup patch and includes all fixes and enhancements included in prior versions. Those features were not updated with 2.21 but are included here for convenience.

Unified Codebase (Included in version 2.12)​

With the need to support a GT eForms Framework 3.10.01, a modification to the code line occurred post-release of 3.14.15. With the need to support different versions, modifications were made to the code to allow seamless support for multiple versions of the product. This resulted in a divergence of the Transporter application. This release updates both releases to a common code base.

Move from Change Analysis to Impact Analysis (Included in version 2.12)​

The feedback received in the short time the Form Transporter has been released is that the Change Analysis prior to import was not helpful and confusing. We have removed the Change Analysis which analyzed every change on the current form and any other form to only perform an Impact Analysis. The Impact Analysis backs up all forms in the target environment and checks against the objects in importing XML to see if there are any SHARED objects among the importing XML and the other forms in the environment. It will only display modifications to the objects that are present on other forms.

Reduces Orphaned Config Objects (Version 2.25)​

The new release has code to help reduce that chance that Orphaned objects get left in the target environment by improving the delete process during the “Complete the Import” step. Orphaned objects occur with the Transporter does not recognize that certain objects are still in the target environment that are removed from the new configuration in the source form. We have changed the code to catch orphan objects that may adversely impact the newly transported form.

Threaded Imports (Version 2.21)​

The importing process is now broken into discrete units of work. They are handled by multiple synchronous processes within Integration Broker. This will reduce stack usage by a single process in the Integration Broker. This allows the handling of larger forms for import.

Other Changes​

We are delivering a number of other changes with this release.

Export Engine (Updated in version 2.25)​

Email Template Binds​

  • All binds are now in the export and transported to new environment.
    • Previous to this change, some binds on the email templates would not be exported and therefore would not import into target environment.

Visual Ifs​

  • More robust export of complicated visual ifs.
    • In certain complex visual ifs, some child logic parts would not be identified correctly and therefore not included in the export.
  • Export Named Vis if Parts
    • Named visual if no export correctly.

Roster Groups​

  • Export Roster Groups
    • Roster Groups were not handled correctly prior to 2.12

Dependent Objects Node​

  • Dependent Objects Node Removed
    • The Dependent Objects node in the XML export is not used for anything. It was designed with a purpose in mind but that need became deprecated. We have now removed it to save space in the XML.

CDATA XML Types Extended​

  • CDATA Use Extended
    • We have now implemented the use of CDATA XML for all text fields. This was causing problems when XML characters were being used like ‘<’ and ‘>’.

Transporter Setup (Updated in version 2.25)​

Don’t Build On Import​

DeliverableDescription:
Default: NoNo: This behavior forces the building of the form after the transport of the configuration. If the build fails, the transport also fails and is rolled back and no changes will occur in the environment.
Yes: The import process will only transport the configuration and stop. It will not build the form. After the import completes, note that the form will not run but all the configuration objects will be in Form Setup. You will also be able to build the form manually from the Transporter Setup table.

Autofill Missing Fields​

DeliverableDescription:
Default: YesYes: If you have records in the target environment that have extra fields not in the export source file, the Transporter will populate them with blank values. This may or may not be the desired behavior and cause unexpected results but it will allow you to go into the configuration and change the values.
No: The import process will fail if any fields exist in the target database that are not in the xml structure in the source xml.

Prod DB Name​

DeliverableDescription:
Default: BlankIMPORTANT: This option is potentially data destructive and should only be used if you have a good understanding of the expected behavior.
Inserting the exact DB Name(s) in this table will result in no Impact Analysis and transport the form automatically on Import. All settings will be copied with no option to validate. Also, in version 2.25, only the form being imported will be backed up in the new environment. No other form will be exported to backup.
DeliverableLocation
Form Transporter Utilities (NEW)GT eForms Feature Documentation > Technical Setup