Fixed Issue List
Defects Fixed
The following defects were fixed as a part of DataGuide release:
|
Case Number
|
Defect Number
|
Description
|
Fixed Version
|
||
|---|---|---|---|---|---|
|
00182563
|
066961
|
Values configured in DataGuide logic rules were cleared unexpectedly during rule creation and editing. Numeric values entered in rule conditions disappeared after users added or modified conditions, and certain form fields entered in preview mode repeatedly cleared previously entered values, preventing users from completing the configuration. In some cases, values remained visible but the associated logic failed to execute, resulting in dependent fields not being updated.
|
12.0
|
||
|
00182522
|
066989
|
Submitted DataGuide forms appeared blank when users attempted to reopen and view previously submitted forms in the web application. Form submissions completed successfully and related records were created, but selecting a recently submitted form from the list of submitted forms displayed an empty form instead of the saved responses.
|
12.0
|
||
|
00181881
|
067003
|
Form Response records were not created when technicians submitted DataGuide forms through the Go application, even though the form data and document templates were generated successfully.
|
12.0
|
||
|
00183175
|
067093
|
Form Response records were not created for technician and community users after completing DataGuide forms, which prevented submitted data from being written to the Form Response object. The issue affected both sandbox and production environments and was observed primarily for technician and community user profiles.
|
12.0
|
||
|
00183860
|
067178
|
Case comments were duplicated after DataGuide form submissions when the Clear Hidden Question Valuessetting was configured as Never. Users observed duplicate case comment entries instead of a single comment containing the submitted question and answer data.
|
12.0
|
||
|
00184114
|
067288
|
DataGuide forms were submitted successfully even though mandatory fields were not completed. The issue occurred when users rapidly clicked the Submit button multiple times after reaching the final page of the form and accepting the submission confirmation overlays. Under these conditions, the form bypassed mandatory field validation and was submitted with incomplete data. The defect occurred because the application did not prevent multiple submit actions from being processed simultaneously, allowing validation checks to be bypassed during repeated submit operations.
|
12.0
|
||
|
00183285
|
067605
|
The required-field logic intermittently failed in the form, causing mandatory validation to be skipped for affected work orders. In several cases, data tables that should have displayed service order line information appeared empty, and technicians were able to submit forms without completing the required field.
|
12.0
|
||
|
00184370
|
067527
|
A blank space was displayed in the Document Templates when forms were not submitted. The issue occurred because the system did not correctly handle scenarios where the Form pills were present in the template but the associated Forms were not submitted. When these Form pills were placed directly on the canvas, a space was allocated for them, which resulted in blank spaces being displayed in the PDF. This impacted the layout and readability.
|
11.3.0
|
||
|
NA
|
NA
|
App version is upgraded due to an internal defect fix in FieldFX deployment.
|
11.2.0 HotFix
|
||
|
00182718
|
066929
|
Certain fields were incorrectly displayed or unavailable in the DataGuide Form Action mapping configuration. When administrators attempted to configure field mappings in the Form Designer, a custom text field on the Installed Product object did not appear in the list of fields available for update. At the same time, a formula field, which should not have been selectable for updates, appeared in the field selection list. This behavior prevented administrators from mapping the correct text field and allowed selection of a field type that should not support updates.
The issue occurred because fields on related objects had identical API names but different data types. The system did not correctly handle scenarios where multiple fields across objects shared the same API name. Due to this conflict, the mapping logic misidentified the fields, which caused the valid text field to be excluded and the formula field to be incorrectly displayed as an available option in the Form Action.
|
11.2.0
|
||
|
00179732
|
066004
|
The renamed None option in checkbox-type questions was not reflected correctly in generated Document Templates. When administrators enabled the None option and renamed it to N/A, the submitted Form correctly captured the value as N/A, but the generated document displayed the value as None.
|
11.1.0
|
||
|
00179434
|
066073
|
Form Actions failed to display nested questions in the question selection picklist when configuring Form Actions. When a question was placed inside nested panels within the Form Designer, it was not available for selection in the Form Actions tab and triggered an error message indicating that the configured question could not be selected.
|
11.1.0
|
||
|
00179388
|
066148
|
DataGuide documents generated in the browser did not retrieve all related child line records, while the same documents rendered correctly in the Go App. In affected cases, only a subset of related form responses was displayed in the generated document, even though additional records existed.
|
11.1.0
|
||
|
00181077
|
066398
|
The collapse and expand icons in DataGuide Forms appeared large in the Go App after upgrading to version 13.0.0. The issue was visible when users expanded or collapsed sections within Forms, where the arrow icons rendered at a large size compared to previous versions.
|
11.1.0
|
||
|
00181122
|
066429
|
DataGuide Document Templates failed to load in the Go App version 13.0.0 and in the browser. When users attempted to open a Document Template, the application returned an error stating that the DataGuide report could not be generated.
|
11.1.0
|
||
|
00181217
00181144
|
066442
|
DataGuide Document Templates did not display translations correctly in the Go App version 13.0.0. When users attempted to open Document Template configured with Japanese or other non-English languages, the Document Template loaded with incorrect or garbled characters.
|
11.1.0
|
||
|
00181217
|
066442
|
DataGuide Document Templates did not display translations correctly in the Go App version 13.0.0. When users attempted to open Document Template configured with Japanese or other non-English languages, the Document Template loaded with incorrect or garbled characters.
|
DataGuide 11.0 Hotfix
|
||
|
00181122
|
066429
|
DataGuide Document Templates failed to load in the Go App version 13.0.0 and in the browser. When users attempted to open a Document Template, the application returned an error stating that the DataGuide report could not be generated.
|
DataGuide 11.0 Hotfix
|
Known Issue and Limitation
Administrators selects fields for mapping and configures Form Actions. The Form displays formula text fields along with other fields that shared the same API name in the Form Action tab.
Workaround: Administrators should explicitly identify and select the non-formula text fields during configuration.