GT eForms 3.58.04 Release Notes
The 3.58.04 service pack includes 8 enhancements and 53 stability improvements. The enhancements include a faster Helium Form Type build for most Form Types and a Mass Withdraw Utility. The fixes include the resolution of Standard to Helium form conversion issues, eForms related data integrity errors, and a number of other fixes. We hope these improvements and enhancements empower you by making your form building more efficient and pleasant.
Service Pack Highlights
Form Build Duration
We recognize that having the form build process take a long time on larger forms makes it difficult to build and test eForms. We have spent a significant amount of time digging in to understand PeopleCode performance with the code structures and patterns we use and have very exciting progress to report. We imported a very large client eForm that took 7 hours to build in our environment. We then went through a variety of profiling and optimization cycles over several months and have been able to reduce that time down to 3 minutes! That's a 99% improvement! While we can't guarantee all Form Types will see the same dramatic improvement as eForms vary in size, complexity, and configuration/code patterns, we do anticipate most Form Types will build faster.
Standard to Helium Conversion
We also became aware of a data loss risk and usability issues that can occur when converting form transactions for a Form Type that was built in Standard (pre-3.5x) and converted to Helium. We have resolved these issues as part of this service pack. Please see this consolidated notice for more information.
If you are considering converting a Form Type from Standard to Helium Performance, you will need to upgrade to this version of GT eForms first to avoid the issues mentioned in the notice. This version contains processes that reliably convert form transactions from Standard (XML) to Helium (JSON).
Planning to apply the Service Pack
This service pack encompasses GT eForms product work completed since the release of 3.58.03
in January 2024. It 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
, 3.58.02
, or 3.58.03
before applying 3.58.04
, as it is cumulative and includes all the fixes and enhancements from those service packs. For information about any previous 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.04
Please contact support@gideontaylor.com with any questions. We are here to help!
Service Pack Details
The diagram below provides an overview of the different areas improved by the 63 items included in this release of GT eForms with the number of fixes/enhancements pertaining to each area.
Enhancement
Functional
Form
2024030 (GTC-5179) | Preserve URL parameters passed to an eForm on all its pages | This enhancement allows URL parameters passed to an eForm to be passed along to all form pages. This provides better compatibility with GT's other UI/UX products. A specific example of this parameter is the PTPN_POPUP_WINDOW URL parameter can be used to prevent each page in a Fluid eForm from reloading to take control of the full webpage. |
Form Setup
2024007 (GTC-1027) | Added "Email Templates" link to Notifications tab of Form Setup | Added an "Email Templates" button to the Notifications tab of Form Setup that allows user to open the Email Templates search menu in a new tab for ease of access |
2024052 (GTC-5385) | Added a prompt to the 'Application Class ID' field on Defined Roster setup | Added a prompt to the 'Application Class ID' field on Defined Roster setup to make it easier for users to select values |
2024053 (GTC-4698) | Added instructions to the Query Records tab | Added instructions to the Query Records tab to help users better understand the purpose and behavior of Query Records |
2024054 (GTC-5294) | Decrease Form Build duration | Improved the performance of the Form Build Traversal process. This enhancement also resolves some uncommon "Class Rowset method ShowAllRows" errors. |
2024071 (GTC-5418) | Deprecated 'parallel traversal processing' checkbox in Form Setup | Deprecated the “parallel traversal processing” option in Form Setup. This Service Pack includes such significant form build improvements that the parallel traversal processing feature is no longer needed. If you are currently using this feature, it is still available for you, but we recommend you turn it off to compare build times and consider using the new default form build process. |
Utility
2024023 (GTC-5026) | Created Mass Withdrawal utility | Created an administrative cleanup tool called the ‘Mass Withdrawal Utility’ that enables users to reset the status of multiple form transactions to ‘Withdrawn’ via the Process Scheduler |
2024049 (GTC-5374) | Implemented configurable control of action taken for Batch Tool BoltOn (submit or save) | Added the ability to designate whether the batch configuration should perform a Save or Submit action |
Issue Fix
Functional
API
2024072 (GTC-5421) | PreNav solution hooks do not fire when navigating to previous page | Fixed an issue that prevented PreNav hooks from firing when a user clicked the 'previous' button in the Form UI. These hooks now fire for both SegmentEvents and PageEvents now fire when using the Previous button to go back a page, as well as when advancing the form to the next page. |
Form
2024002 (GTC-5109) | Empty string value for Boolean JSON property causes improper rendering of grid fields | Fixed an issue with grid segments that caused them to incorrectly evaluate fields with a boolean data type, like a Visual If |
2024005 (GTC-5127) | Two labels in the Attachment custom segment couldn't be translated | Changed the "Attachment Required" and "File Name" labels in the File Attachments custom segment to message catalogs to enable translation of those labels |
2024010 (GTC-5115) | PT 8.60.05 issue: Action Item label incorrectly displays "message comment" on devices with small form factor | Fixed an issue with Action Items in PeopleTools version 8.60.05 that mistakenly displayed "message comment" in place of the correct action item label when a user accessed a form on a device with a small screen. |
2024012 (GTC-5145) | Record Class: . . . Not a valid field name" error appears when opening a form with a session language other than English | Fixed an issue that caused PeopleSoft to display an error when a user opened a form that contained a dropdown field with a Long or Short Translate dropdown source in a user session with a language other than English. The error read: "Record class: The assumed property [FIELDNAME] is not a valid field name. |
2024013 (GTC-5156) | Standard forms not showing highlights | Fixed an issue with Standard forms that prevented them from highlighting changes to a form even when the 'Show Highlights' checkbox was checked in Form Setup |
2024014 (GTC-5157) | Segment sequences greater than 100 cause improper display order | Fixed an issue that caused segments to appear out of order when there were multiple segments in a form and some of them had sequence values greater than 100 |
2024017 (GTC-5165) | Dropdown fields with invalid values not properly highlighted in code-generated form transactions | Fixed an issue with validation surfacing that prevented the system from properly highlighting dropdown fields with invalid values in red. This only occurred with code-generated form transactions using Helium Performance. |
2024018 (GTC-5034) | View Approval Route' button displays 'Approval App Instance returned null' error on denied forms | Incorporated logic into the 'View Approval Route' button on the delivered History Page of eForms that hides the button when the form has been denied. This is to avoid an error that sometimes appeared when a user attempted to view the workflow of a form that had none. |
2024020 (GTC-5178) | Issue with solution code validating current comment no longer working | A client's solution code depended on the current comment being available longer than it was after a change made for Helium. Resolved the issue by leaving the comment set and only clearing it out for Helium. |
2024027 (GTC-5184) | Form Keys not generated for fields in search config that are present but not checked for Use | Fixed an issue that prevented the framework from generating form keys for Search Configuration fields that had the 'Show' checkbox deactivated View Screenshots |
2024029 (GTC-5213) | First operand of . is NULL' error appears when clicking 'View Approval Route' | Fixed an issue that produced an error reading "First operand of . is NULL, so cannot access member id" when a user clicked the 'View Approval Route' or 'Refresh Log' buttons on the Results page of a form |
2024034 (GTC-5212) | Misspelling present in an attachment related error message | Fixed a typo in an error message that is surfaced when an attachment URL doesn't exist. |
2024035 (GTC-5214) | Custom segment grids render improperly on mobile/responsive layouts for forms using Helium Performance | Fixed an issue that caused custom segments grids (such as the form log that appears after submitting a form) to render improperly for form types using Helium Performance on mobile devices |
2024037 (GTC-5250) | ''Has Been Submitted' Visual If part returns true before form submission | Fixed an issue that caused the delivered 'Has Been Submitted' Visual If part to return True before a form was submitted |
2024040 (GTC-5173) | Data Integrity errors occasionally occur on eForms | This fix improves the versioning of GT generated objects to better align with what happens in Application Designer when creating objects. This source of data integrity errors in eForms has been resolved. |
2024041 (GTC-5265) | Configured Grid segments displaying incorrectly on Results and History pages | Fixed an issue with configured Grid segments that caused them to display at the bottom of the History and Results page instead of where it was configured to show |
2024044 (GTC-5176) | Form with InsertRow hooks has extra rows in grid segments when a user opens a form in the update, evaluate, or view tasks | Fixed an issue affecting forms with InsertRow hooks that inserted extra rows into a grid segment in the update, evaluate, or view tasks |
2024047 (GTC-5266) | On-page validation messages inconsistently aligned | Fixed an issue with the display of on-page validation messages that caused inconsistent alignment, with messages sometimes aligned with the highlighted field and other times left-justified on the page |
2024048 (GTC-5161) | Field length of G3POOL_FLD_ALIAS (30) is not long enough for all possible record tags and fieldnames (34) | Fixed an issue with the field length of G3POOL_FLD_ALIAS that made it too short for all the possible record tags and fieldnames it might hold |
2024056 (GTC-5386) | Configured field validations remain unresolved when the field changes based on configuration | Fixed an issue that prevented validations from properly clearing when they were triggered by data flows based on "update when this source changes" configuration |
2024058 (GTC-5390) | Form errors occur after new I9 form install | Fixed a part of the delivered 'Catalog Custom Parts' process that caused it to ignore some fields in the I9 form after a new installation of the solution, resulting in form errors |
2024059 (GTC-5365) | Form with a SaveOnNext hook errors when trying to open a transaction in the Update task | Fixed an issue involving forms that had multiple pages and used a SaveOnNext hook that caused them to error when opened in the Update task |
2024067 (GTC-5424) | Unnecessary 'save changes' prompt appears when leaving Results page | Fixed an issue that caused a 'Do you want to save your changes' message to appear unnecessarily when a user navigated away from the Results page in the View task of a form |
2024068 (GTC-5329) | 'Accessing Field Tag' error appears when leaving Rich Text field in Form UI | Fixed an issue that caused an error to appear when a user left a Rich Text field and the field had a Visual If configured and it had 'Span Columns' checked and it was placed in the right column. The error read: "A Field Tag of this name does not exist in the form setup." |
Form Setup
2024036 (GTC-5190) | "Class row" error appears when getting sample XML for form reports on Helium form types | Fixed an issue that caused an error to appear when getting sample XML for a form report on a Helium form type. The error read: "Class row: assumed property G3COMMENTS_DRV is not a valid record name." |
2024045 (GTC-5248) | CKEditor5 options not showing in Attachment Instructions | Made adjustments to the Rich Text Editor for attachment instructions in the Attachments tab of form setup. These adjustments restored some buttons that were missing from that menu. |
2024057 (GTC-5389) | Email notifications not firing for 'Approved' and 'Recycled' events on certain approval steps | Removed the option to use 'Approved' and 'Recycled' as email notification triggers for certain steps where they weren't designed to trigger email notifications |
2024066 (GTC-5416) | Segment names over 18 characters break changing fields in that segment for Standard form types | Fixed an issue with Standard form types that prevented users from making changes to fields in a segment if the segment had a name with more than 18 characters |
2024069 (GTC-5405) | Form Build Process fails when PeopleTools sort order is not set to "Binary" | Created an exception that fires at the beginning of the form build process if the PeopleTools environment's 'Sort Order' settings are set to anything other than 'Binary.' |
Search
2024003 (GTC-5131) | eForms search fields do not display translate values of 'T' | Fixed an issue with framework search fields that prevented them from displaying dropdown field values with a translate value of 'T' |
Utility
2024001 (GTC-5135) | "There are no prompt values currently available for this field" error appears in Deployment Tool | Fixed an issue with the Deployment Tool that prevented users from accessing it. This produced an error message: "There are no prompt values currently available for this field. The prompt table for this field is currently not specified." |
2024006 (GTC-5139) | Deployment tool incapable of processing extremely high sequence numbers | Set the max sequence value for the Deployment Tool to 9,999 to avoid issues that occur with extremely high values |
2024009 (GTC-5081) | LogicStacks don't work when SmartSource are manually typed in rather than selected | Fixed an issue with LogicStacks not working when a user manually typed the name of the SmartSource instead of using the lookup field to populate it. This caused the LogicStack to return a blank value for the SmartSource even if it had a value. |
2024016 (GTC-5168) | Errors fire related to the current comment or comment history | Fixed these two comment-related errors: "Variable contains a reference to a row object that has been deleted." and "First operand of . is NULL, so cannot access member G3COMMENT_HISTORY." that occur when accessing the form's current comment or comment history. |
2024026 (GTC-5194) | GT Robot Setup page missing Form Build link | Fixed an issue with the GT Robot Setup page that prevented it from displaying the ‘Form Build’ link on the page |
2024032 (GTC-1159) | Rows not properly deleting in 'Context Type' grid of GT Dev Debug Tool | Fixed an issue with the 'Context Type' grid in the GT Dev Debug Tool that prevented rows from deleting properly when users tried to remove them |
2024033 (GTC-5158) | Users can't generate BI Publisher reports for eForms in context-independent mode | Fixed an issue that occurred when a user tried to run a BI Publisher report for an eForm in context-independent mode. The issue caused users to encounter an error that read: "First operand of . Is NULL, so cannot access member G3COMMENT_HISTORY." |
2024038 (GTC-5186) | STOMP tool 'Last Update User ID' search field not displaying valid values | Fixed an issue with the 'Last Update User ID' prompt field in the STOMP tool that prevented it from showing users in the prompt |
2024042 (GTC-5337) | Issue with Form Log order in default XML generated for form reports | Fixed an issue with Form Log entries being in the wrong order in the Default XML generated for form reports (BI Publisher) |
2042043 (GTC-5191) | Restricted access to Workflow Tools to GT eForms Administrators | Changed the permission lists and Navigation Collection security of the Workflow Tools menu to allow only those with the GT eForms Administrator role to access it |
2024046 (GTC-5352) | SavePreChange method causing errors when a form is approved through the Form Admin Tool | Fixed an issue that prevented SavePreChange methods from firing correctly when a form was approved through the Form Admin Tool. This issue occasionally resulted in errors when a user tried to approve a form through the Form Admin Tool. The error message contained "First operand of . is NULL, so cannot access member..." |
2024060 (GTC-5257) | Standard forms not opening via GT WorkCenter | Fixed an issue that prevented users from opening forms using Standard performance via the GT WorkCenter |
2024061 (GTC-5391) | Created the Standard Form Data Converter | Added the ability for clients to use the Standard Form Data Converter to convert form transactions from Standard to Helium in batches |
Workflow
2024028 (GTC-5193) | Ad Hoc Approver lookup showing incorrect results | Fixed an issue with the G3AWE_APPVR_VW table that caused it to display the PS default Ad Hoc approver list instead of the correct list from the table when adding an Ad Hoc approver to a form |
2024031 (GTC-5233) | eForm worklist items remain visible even after approval when forms use custom workflow definition with 'All Approvers Required' | Fixed an issue that caused eForms to remain visible in the Worklist even after they were approved when the form utilized a custom workflow definition and had an approval step with the 'All Approvers Required' attribute configured |
Technical
API
2024015 (GTC-5163) | Process Token URL SmartSource produces errors when submitting a form via an App Engine | Fixed an issue with the Process Token URL SmartSource that caused it to produce a "First operand of . is Null" error because the %Request object does not exist in forms submitted via App Engine processes. |
Database
2024024 (GTC-5189) | G3QRY_TBLEXISTS SQL Definition references the wrong column id for SQL Server | Fixed an issue that caused environments running Microsoft SQL Server to process the G3QRY_TBLEXISTS SQL Definition incorrectly by referencing the TABLE_NAME column instead of the NAME column. Functionally, this presented errors when running the "Check for Built" function on the Query Records tab in Form Setup. |
Form
2024004 (GTC-5134) | FieldChange hook for a button/link in a grid is firing when the grid data is loaded | The scenario for this issue was when a user changed the EFFDT value in a form, a grid's data was also loaded. The issue was that it also fired the FieldChange hook for a button/link field in the grid, as though the user clicked the button/link. This fix resolves that issue so it only fires the FieldChange hook when the user clicks on the button/link. |
2024025 (GTC-5182) | File attachments not being deleted from app server after being transferred to the permanent storage | When a form is saved, the file attachments are transferred from temporary storage to a permanent storage location. Files were being stored on the app server as part of this transfer and this fix handles the garbage collection of those files from the app server. |
Package
2024022 (GTC-5175) | Solution code may conflict with GTC-5168 fix | Clients using an override comment segment driver may override set WORKREC which GTC-5168 removed. This fix adds it back in case clients are using it. |
Utility
2024021 (GTC-5160) | Load Custom Parts not completing for public search pattern | Fixed an error "First operand of. is NULL, so cannot access member GetParameterNames. (180.236)" caused by a solution code dependency on G3SEARCH:Search . This fix allows that class to be handled correctly in the 'Load Custom Parts' process. |
2024055 (GTC-5372) | Form Admin Tool uses a deprecated hook for form actions | Updated the Form Admin Tool to use the new SavePreChange hook instead of the deprecated SavePreChangeHook hook when taking form actions |
Documentation Changes
Functional Documents
New Documents
Document | Location | Applies to Version Starting With |
---|---|---|
Standard Form Data Converter | GT eForms Feature Documentation > Utilities | 3.58.04 |
Updated Documents
Document | Location | Applies to Version Starting With | Changes Made |
---|---|---|---|
Workflow Tools | GT eForms Feature Documentation > Utilities | 3.58.04 | Created a section for the new Mass Withdraw Utility |
Validations Tab (Feature Doc) | GT eForms Feature Documentation > Form Setup | 3.58.00 | Explained that 'Validation Messages' segment doesn't appear on mobile devices |
General Tab and Form Installation Table feature docs | GT eForms Feature Documentation > Form Setup or > Functional Setup > System Setup | 3.58.04 | Removed notes about parallel processing for form build, which is a deprecated feature. |
System Maintenance (Feature Doc) | GT eForms Feature Documentation > Technical Setup | 3.58.04 | Added a new section about the Conv Dat Cleanup maintenance process introduced in this version. |
Query Records (Feature Doc) | GT eForms Feature Documentation > Form Setup | 3.58.04 | Added a note explaining a possible reason query record data might appear out of sync and a method for re-syncing it. |
Form Admin Tool (Feature Doc) | GT eForms Feature Documentation > More > Other Tools and Options | 3.58.04 | Added a new section to the document explaining that the Admin Tool will now warn users against acting on form transactions that need to be converted to Helium. |
Technical Documents
New Documents
Document | Location | Applies to Version Starting With | Changes Made |
---|---|---|---|
3.58.04 Install Guide | GT eForms Feature Documentation > More > Install Documentation | 3.58.04 | Created a document explaining the installation process of GT eForms 3.58.04 . |