GT eForms 3.58.03 Release Notes
The 3.58.03 service pack continues to provide fixes that enhance the stability of GT eForms as well as provide small enhancements. Such enhancements include the introduction of a web service for the GT Form Transporter, a streamlined Permission List Version History, and many more. Additionally, a noteworthy fix included in this release is we have identified and fixed the cause of data integrity errors that sometimes occur when using multi-field prompts on a GT eForm. We hope the fixes and performance improvements included in this release enhance your form-building experience.
The diagram below provides an overview of the different areas improved by the 76 items included in this release of GT eForms with the number of fixes/enhancements pertaining to each area.
Service Pack Overview
There are 63 issue fixes and 13 small enhancements in this 3.58.03 service pack. It encompasses GT eForms product work completed since the release of 3.58.02 in September 2023.
This service pack must be applied on top of 3.58.00. If you are on a release prior to 3.58.00, you will need to upgrade to 3.58.00 first. Please plan to apply this upgrade and test your forms in a development and test environment prior to moving to production. You do not need to apply 3.58.01 or 3.58.02 before applying 3.58.03, as it is cumulative and includes all the fixes and enhancements from the .01 and .02 service packs. For information about either the 3.58.01 or 3.58.02 releases, please see the historical release notes.
The upgrade package and instructions are located here:
Online GT Library > Documents > Framework Updates > 3.x > R3.58.03
Please contact support@gideontaylor.com with any questions. We are here to help!
Service Pack Details
As we shared in our last email update, release notes 2023236 and 2023205 are important issue fixes and enhancements to be aware of.
These release notes are also stored in a spreadsheet format to support sorting and filtering:
Customer Self-Service > Documents > Documentation > Latest Release Notes > 3.58.03 Service Pack Release Notes.xlsx
The table below has details of the enhancements and issues resolved.
Release Note Legend
Type: Enhancement or Issue
The type is either enhancement or issue.
Impact: Functional, Technical, Sys Admin
Impact pertains to who would likely encounter the issue or do work that would be most impacted by the issue/enhancement.
If an issue/enhancement involves configuration, it's Functional.
If an issue/enhancement involves code or other App Designer work, it's Technical.
If an issue/enhancement involves applying of an upgrade package or system maintenance, it's Sys Admin.
Area: Form, Form Setup, Utility, etc.
The area of the product refers to the area of the product the enhancement or issue most affects. Form refers to the end-user experience using the form. Form Setup refers to the configuration of a form type.
Release Number | Summary | Details and Link to view screenshots if applicable |
Enhancement
Functional
Form Setup
2023167 (GTC-4771) | Added text to the warning message that appears when a user turns off Helium Performance for a form type | Added text to the warning message that appears when a user turns off Helium Performance for a form type. New text warns users of potential ramifications that involve newer features released with recent GT eForms versions. | View Screenshots |
2023189 (GTC-4929) | Added Multi-language support for file attachments | Added the ability to configure multi-language translations for file attachment instructions and descriptions | View Screenshots |
2023192 (GTC-4803) | Added Multi-language support for navigation button labels | Added the ability to configure multi-language translations for navigation button labels | View Screenshots |
2023206 (GTC-5029) | Made improvements to the tabbing order of fields in Form Setup | Made changes to the order in which a user may select fields in the Segment configuration of Form Setup. To be more consistent with the rest of the framework, this menu will now allow users to tab through fields row by row. | |
2023229 (GTC-4815) | Added multi-language compatibility for configured freeform text validations | Added the ability for form builders to configure language translations for freeform text validation messages | |
2023230 (GTC-4816) | Multi-language translations for value lists | Added the capability for form builders to configure language translation values for Value Lists | View Screenshots |
2023234 (GTC-4802) | Added multi-language compatibility for Instruction field types | Added the ability to configure multi-language translations for instruction field types in Form Setup |
Sys Admin
Package
2023245 (GTC-5105) | Created Permission List Version History | Created a way of reviewing historical changes to GT Delivered Permission Lists for comparing changes with framework upgrades going forward. Clients can view these details by reviewing the Historical GT eForms Permission List Changes document. |
Technical
API
2023194 (GTC-4857) | Created a new property for developers to retrieve field values | Added a currentValue property to the FieldTag class. This allows a developer to retrieve the value of the field tag without triggering a dependency network resolution. |
2023208 (GTC-5033) | Improved consistency in Form Solution Events | This enhancement allows for the new SavePreChange and SavePostChange hooks to be recognized as solution methods for Form-level events |
Form Setup
2023197 (GTC-4861) | Alert user when PSPCMTXT is missing entries | Building an eForm with coded hooks and parts requires evaluating PeopleCode stored in PSPCMTXT. This enhancement ensures that users are alerted if an application class is missing from the PSPCMTXT table when building the form. |
Utility
2023179 (GTC-4945) | Made improvements to memory utilization of the GT Robot | Added "CollectGarbage()" function to GT Robot to improve memory utilization issues |
2023205 (GTC-4934) | Created a Transporter API and user interface | Created an API for the Form Transporter as well as a new PS component to view historical API requests and import/export forms independently of the eForms From Transporter. This enables the automation of eForm exports and imports. |
Issue Fix
Functional
API
2023218 (GTC-5041) | Visual Ifs don't fire when the fields they reference are changed via code | Fixed an issue with Visual Ifs that prevented them from firing when the field values they referenced were changed with a code hook |
Form
2023168 (GTC-4925) | Configured pop-up validations not appearing for grid fields | Fixed an issue with configured validations that prevented pop-up validations from displaying for grid fields |
2023170 (GTC-4741) | Segments added to the Delivered Results Page are editable when they should be read-only automatically | Fixed an issue with the framework that was allowing users to edit config segments on Delivered Results Pages |
2023171 (GTC-4926) | Custom Save button returns "Class Record: assumed property is not a valid field name" error | Fixed an issue with custom Save buttons that caused the buttons to throw an error that read “Class Record: assumed property is not a valid field name” |
2023173 (GTC-4033) | "FormType is required to create a Form instance" error appears in IB Log of Form Admin Tool | Fixed an issue with the form handler that caused the Integration Broker to lose a Form ID and fail |
2023182 (GTC-4951) | Navigation button can't be hidden when only one button is present | Fixed an issue with navigation buttons and visual Ifs that made it so a user couldn’t hide a navigation button unless there was at least one other visible navigation button on the page |
2023183 (GTC-4947) | FieldChange hook causes "Not enough parameters given" error on grid fields | Fixed an issue with grid segments that prevented them from properly processing FieldChange hooks |
2023185 (GTC-4953) | Date fields not working on Search pages | Fixed a variety of issues with Date fields on search pages that prevented them from functioning correctly, even causing them to occasionally produce SQL errors |
2023187 (GTC-4961) | Users struggling to access worklist item links due to autopopulation of OPRID field in Search pages | Fixed an issue with search pages that caused them to automatically populate OPRID fields with the OPRID of whichever user accessed the page. This is useful and intended in specific scenarios, but with this fix, it now only occurs when it is supposed to. This fixes issues that made it difficult for users to access worklist item links and approval email links. For additional details, read the Helium Functional Reference document. |
2023188 (GTC-4935) | Search sets with apostrophe characters cause errors on form import | Fixed an issue with the Form Transporter that caused it to produce errors when users imported a form type contained in a Search Set with an apostrophe character in the name |
2023190 (GTC-4684) | Ad-hoc approvers added on config pages get removed once a form is submitted | Fixed an issue with the "View Approval Route (Add Ad Hoc Approver)" button on config pages where if a user added an Ad Hoc approver on one of those pages, the workflow would be reset upon form submission and the approvers were removed from the workflow. The resetting of workflow upon form submission is intended, so we removed the ability for users to add Ad Hoc approvers on config pages. |
2023207 (GTC-5032) | Form throws errors with complex grid dependencies | Fixed an issue with grid segments that caused a form to throw errors when the grid contained complex dependencies. The error read: "Fetching array element 2: index is not in range 1 to 1" (uncommon scenario) |
2023210 (GTC-4963) | Form instructional text has formatting issues after 3.58.02 upgrade | Fixed an issue that arose in 3.58.02 and caused some instructional text fields to alter the formatting of text, occasionally removing line breaks |
2023214 (GTC-5054) | Standard forms error: "An error occurred trying to get [Grid Segment] row" | Fixed an issue with Standard forms with complicated Grid segment configuration that caused them to throw an error stating: "An error occurred trying to get [Grid Segment] row" |
2023217 (GTC-4756) | "Invalid Lookup Value" warning doesn't include the field label | Modified the "Invalid Lookup Value" warning that sometimes appears in forms to include the label of the field to which it refers |
2023223 (GTC-4949) | "First operand is null" error appears when disabling highlights | Fixed an error that would appear when a user disabled highlights after populating a grid segment with values |
2023232 (GTC-5074) | Added the link, blockquote, and code block options back to Fluid rich text editor | Added the link, blockquote, and code block options back to the Quill rich text editor interface that is available to end users in a form |
2023236 (GTC-4962) | Data integrity errors appear due to Multifield Prompt caching issue | Addressed unexpected PeopleTools version updates that occasionally caused data integrity errors and user expulsion from eForms. We found that this PeopleSoft behavior was related to Multifield Prompts and have coded to account for the behavior and resolve the issue. |
Form Setup
2023169 (GTC-2438) | "Editable" Visual If visible when first adding a segment to any task | The “Editable” visual if was appearing when a user added a new segment to any task. With this fix, the visual if now appears only when it is applicable. | |
2023172 (GTC-4930) | Form Transporter Version doesn't appear on Form Installation Table | Updated the transporter version number on the Form Installation Table | |
2023175 (GTC-3237) | Image and Link buttons in CKEditor are unsupported with PT 8.59+ | Removed the unsupported image and link buttons from the CKEditor interface in Form Setup. | |
2023180 (GTC-1943) | Plus and Minus buttons not aligned in Visual If setup | Made improvements to the visual alignment of the Plus and Minus buttons that appear when a user selects the "Is In" parameter in the Visual If configuration window | |
2023181 (GTC-4950) | Smart Sources used in the "Allowed Auto-Approvers" roster of eForms routing are not included in the dependency network | Fixed an issue with SmartSources used in the Auto-Approvers roster of the Routing tab that prevented the SmartSources from being included in the Dependency Network, causing errors with routing | |
2023184 (GTC-4957) | Custom SQL parameters don't work on lowest level keys in Data Pool records | Fixed an issue with custom SQL in Data Pool records that prevented users from using it to limit the results of the lowest key in the record | |
2023196 (GTC-2334) | Blank column appears in Action Item Table | Removed a blank column that was left over from a deprecated feature in the Action Item setup table in Form Setup | |
2023200 (GTC-1030) | Revert button doesn't do anything on the default condition in Form Setup | Removed the revert button from the default condition in Form Setup to avoid confusion as the default condition can not be reverted | |
2023202 (GTC-1928) | Blank columns appear in Pages tab and Routing tab of Form Setup | Removed blank columns that were left over from deprecated features in the Pages tab and the Routing tab in Form Setup | |
2023203 (GTC-4910) | Updating Query Defined Roster setup produces "Data being added conflicts with existing data" error | Fixed an error with the Query Defined Roster setup that would occasionally produce a "Data being added conflicts with existing data" error when a user updated the name of the query used in the roster | |
2023213 (GTC-5040) | G3PPC_ID field should have length of 100 | In the 3.58.00 Service Pack, we increased the length of PeopleSoft field G3PPC_ID from 60 to 100. The G3PPC_ID field was excluded from that, but will now be included with this Service Pack. | |
2023216 (GTC-4735) | Initialize/Update lookup fields in Form Setup get reset when the "Initialize From" dropdown changes | Fixed an issue that caused the "Update when This Source Changes" field to reset when a user changes the "Initialize from" dropdown selection. | |
2023222 (GTC-4960) | Changing a Record/Table name in a Data Pool Source does not clear out Custom SQL | Fixed an issue with the Data Pool menu in Form Setup that prevented it from properly clearing out data relating to a Record or Query after changing the Record or Query | |
2023233 (GTC-4928) | Changing a field display type resets the field's initialization settings | Fixed an issue with Segment Field Configuration that caused it to clear out a field's initialization settings if a form builder changed the field's display type | View Screenshots |
2023238 (GTC-5091) | "Class Row: assumed property" error appears when a user clicks the "Languages" button in the Value Lists setup menu | Fixed an issue with the multilanguage configuration button in the Value Lists setup menu that caused it to display an error that read "Class Row: assumed property G3SEGMENT_FLDS is not a valid record name" when a user clicked the button | |
2023240 (GTC-5094) | Derived records are created for segments created in new Helium Form Types before saving the form type | Fixed an issue that caused the creation of derived records for segments in Helium Form types if a user created the segments in a brand new form type before saving it. This issue had no affect on form functionality, but could potentially cause confusion if the derived records were to fall out of sync and appear on an audit report. | |
2023242 (GTC-5098) | Removed all Validation Code related to Segment Record Tags matching Data Pool Tags and vice versa | Removed controls to prevent users from creating segments and Data Pool sources with matching Pool Tags and Record Tags. Also removed messages that warn users of such action. It’s important for GT eForms users to note that they should still never give Data Pool sources a Pool Tag that matches an existing segment’s Record Tag or vice versa. Doing so will compromise the functionality of those Data Pool sources and segments. |
Search
2023209 (GTC-5030) | G3ORIGINAL_OPRID and G3LAST_OPRID are automatically capitalized in Form Search | Fixed an issue with form searches automatically capitalizing user entry that caused it to automatically capitalize G3ORIGINAL_OPRID and G3LAST_OPRID fields. These fields will no longer be capitalized automatically in a form search. For additional details, read the Helium Functional Reference document. |
2023231 (GTC-4919) | Search is failing' error occurs when a form has a custom search record | Fixed an issue with Search Configuration that occasionally caused shared search tasks like the Update task to look at the form's Add task search record when one existed. This issue would cause a search to return the an error that stated: "Search is failing when trying to return this search key: . . ." |
Utility
2023176 (GTC-3166) | Standard forms show form keys from other form types in Form Admin Tool | Fixed an issue with the Form Key Update Utility that caused it to show form keys for standard forms in the Form Admin Tool for other form types in the same family | |
2023178 (GTC-1529) | Worklist Items tab in the Admin Tool shows superfluous information | Removed a column from the Worklist Items tab in the Form Admin Tool that contained information about email addresses. This column was deemed unnecessary as users can send emails via the Admin Tool. | View Screenshots |
2023191 (GTC-3059) | Unhelpful options appear in Network ID selector of Network Visualizer Utility | Removed Network ID options that contained "Code," "Ext," and "Config" suffixes from the Network Id search field in the Network Visualizer utility. Users can still view these options by clicking the new "Show more networks" slider underneath the search field. | |
2023193 (GTC-4543) | Search Configuration shows duplicated fields and sometimes exceeds maximum allowable rows in Search Config after Form Import | Fixed an issue with the Form Transporter in which it would not clear out Search Configuration if a user imported a form type into an environment where its Family or Search Set already existed, but the form type did not yet exist. This occasionally caused issues with Search Configuration in Form Families and Search Sets. | |
2023198 (GTC-4958) | Network Visualizer shows disorganized fields when a user tabs out of the network ID search field | Fixed an issue with the Network ID search field in the Network Visualizer that caused the page to display fields out of order and make them inaccessible | |
2023215 (GTC-2238) | Form Admin Tool IB Log shows prior processes when authorizing a form | Made changes to the Form Admin Tool IB Log so that it no longer shows logs from prior processes when a user authorizes a form | |
2023221 (GTC-4959) | Network Visualizer throws "Invalid token" error when a user clears/tabs out of the Network Id field | Fixed an issue with the Network Visualizer utility that caused it to display fields out of order and throw an “Invalid token” error when a user cleared or tabbed out of the Network Id search field | |
2023224 (GTC-3239) | "First operand is null" error appears in Form Admin Tool when authorizing a form that has no approval workflow | Fixed an error that appeared in the Form Admin Tool when a user authorized a form transaction that was only saved and had no approval workflow | |
2023225 (GTC-4923) | Form Build Status not properly updated when subtask fails | Fixed an issue with the Form Build utility that prevented build tasks from displaying error messages for subtasks | View Screenshots |
2023228 (GTC-5056) | Last row's down arrow in Value List setup isn't read-only when it should be | Fixed an issue with the Value Lists component that caused the down arrow in the last row to continue to function even when it should be disabled | View Screenshots |
2023235 (GTC-2027) | Moving a Form Type from one Form Family to another causes the Search Config to leave orphaned rows | Fixed an issue that occurred when a user moved a Form Type from one Form Family to another that caused the Search Config to leave orphaned rows that affected the search page | |
2023237 (GTC-5086) | Form Admin Tool displays "First operand of . is NULL" error when a form has workflow active but no pending step | Fixed an issue that occasionally occured when a form had workflow active but no pending workflow step that prevented users from opening the form in the Form Admin Tool | |
2023243 (GTC-5100) | Build Failed for form type error on Import occurs and references derived records for Helium Form Types | Fixed an issue with the Form Transporter that caused it to produce an error when users imported a Helium Form Type that contained segments with derived records. The error read: "Build failed for [Form Type] Error creating [DERIVED_RECORD.FIELD] Could not load record." |
Workflow
2023195 (GTC-3016) | Workflow Pushback doesn't clear Worklist items for the de-activated step | Fixed an issue with the Workflow Pushback action that allowed worklist items created for pending approvers before the pushback to persist. Now, those worklist items will be cleared out on pushback. |
2023212 (GTC-5047) | G3AweCriteriaStartTrueShim does not check for Pushed Back form status | Fixed an uncommon issue that occurred when a user performed a Pushback on a form in which one or more steps in the workflow used GT's “Start True” criteria shim. This issue negatively affected the AWE's ability to evaluate potential approvers for a form. |
Sys Admin
Package
2023226 (GTC-5057) | G3FORMFUNC and G3FORMTECH Permission Lists missing permissions to some new features | Added permission to access the new language configuration in the Navigation Button Defaults to the G3FORMFUNC Permission List and access to some components under GT Technical Setup to the G3FORMTECH Permission List. For more details, see the Historical GT eForms Permission List Changes document. |
Utility
2023227 (GTC-4917) | Form Transporter Build Process creates GS segment derived records for Helium form types | Fixed an issue that caused the Form Transporter process to create derived records for segments in the form. This issue had no affect on form functionality, but could potentially cause confusion if the derived records were to fall out of sync and appear on an audit report. |
Technical
API
2023199 (GTC-4970) | Inefficiency identified with field value logic | Previously, setting a field audit value would trigger a network resolve, which was potentially problematic. Now, the system will use the API method created in release 2023194 to capture the field's value without resolving it. |
2023211 (GTC-5038) | FormSearchKeyEvent doesn't fire on Standard Form Update Task | Fixed an issue with the FormSearchKeyEvent not firing on the Update task of Standard forms |
2023219 (GTC-5048) | SetSortDropDown hooks not working in grid segments | Fixed an issue with SetSortDropDown hooks that prevented them from firing when they referenced a field in a grid segment with a Long Translate, Short Translate, or Value List source |
2023244 (GTC-5104) | Solution validation to prevent a recycle or deny until a comment is entered no longer working | Amended a fix (2023139) from the 3.58.02 Service Pack that prevented WORKREC from properly updating on the Form Admin tool. This affected clients with custom code referencing comments and would sometimes produce errors referencing "G3COMMENT_HISTORY". |
Form
2023177 (GTC-3162) | Field Style Class isn't getting cleared out if the same field type is used in the same location on two pages | Fixed an issue with Standard forms that prevented them from clearing out the Field Style Class if the same field was used in the same location on two pages |
Package
2023186 (GTC-4967) | G3SEARCH page missing from project | Re-added the G3SEARCH page to the upgrade project, as it was missing from the 3.58.02 project |
2023204 (GTC-5007) | Inline comments processed as SQL statements in Change Assistant | We found a parsing issue with Oracle Change Assistant that causes it to parse inline comments as SQL statements. As this issue does not exist with multiline comments, we replaced several inline comments in G3 SQL objects and replaced them with multiline comments to work around the parsing issue. |
2023241 (GTC-5101) | Cleaned up deprecated JQuery references in framework | Removed references to the G3CFG_HTML object, as it has been deprecated |
Utility
2023220 (GTC-5066) | Added ITEMNAME to the G3PL_PAGE view | Added the ITEMNAME field the the G3PL_PAGE view to document changes to GT delivered page security from version to version |
Documentation
Functional Documents
New Documents
Document | Location | Applicable to Versions Starting With |
---|---|---|
eForm Approval History View | Tips N Tricks > Functional | 3.58.01 |
Updated Documents
Document | Location | Applies to Version Starting With | Changes Made |
---|---|---|---|
GT Batch Form Processing | GT eForms Feature Documentation > BoltOns | 3.58.00 | Added details about compatibility with 3.58.00 features |
Form Admin Tool | GT eForms Feature Documentation > Form Admin Tool | 3.30.04 | Updated explanation of the "Authorize without IB" feature |
Form Admin Tool Security | GT eForms Feature Documentation > Functional Setup > System Setup | 3.30.04 | Updated explanation of the "Authorize without IB" feature |
3.5x Helium Functional Reference | GT eForms Feature Documentation > More | 3.30.04 | Added a section explaining that grid fields can not be used as SmartSources without Technical work. Explained new behavior of GT Special Fields compared with PS Fields |
3.5x Helium Solution Migration Guide | Tips N Trics > Technical | 3.58.03 | Updated information regarding the migration process |
Technical Document Changes
New Documents
Document | Location | Applicable to Versions Starting With |
---|---|---|
Parallel Traversal Processing | Tips N Tricks > Technical | 3.58.02 |
Updated Documents
Document | Location | Applies to Version Starting With | Changes Made |
---|---|---|---|
GT 3 API Documentation | GT eForms Feature Documentation > API | 3.58.03 | Added new FieldTag currentValue property Added "Allow AWE’s Pushback Event" section Corrected minor details |
3.5x Helium Technical Reference | GT eForms Feature Documentation > More | 3.58.03 | Added information about the PSPCMTXT table Added getConfigField and getRowConfigField methods to GField and GFieldGrid Added "Invalid Object References" section (think-time functions) Added information about the Tech Trigger feature |