00171286

063620

Records from DataGuide Forms that included date and datetime answers did not display correctly in reports. The report columns such as Answer Date and Answer Datetime showed #Error! instead of values whenever the underlying text could not be converted into a date/datetime. This behavior misled users into thinking data was broken or missing in reporting outputs.

11.0

00173662

064266

The default value always appeared in UTC rather than in the user’s local timezone, when a DateTime question was opened on Go Windows, even though other platforms (Web, iOS, Android) displayed device or user time.

11.0

00174075

064372

Configured validations were not triggered for number questions configured with minimum and maximum values, when an invalid number was entered and Save for Later was selected. The entered value was truncated or blanked.

11.0

00174482

064755

Document Template output that included multi-column headers did not render borders consistently, and headers sometimes displayed border segments with varying or incorrect spans. Border lines appeared randomly on or off, producing inconsistent visual formatting in generated documents.

11.0

00178029

065552

Currency fields added into a DataGuide document template did not show any values when previewing or generating the template, even though the currency field in the Work Order contained a valid value. This resulted in missing currency output in generated document templates across environments.

11.0

00176154

065016

The forms converted text values containing commas into decimal numbers during Work Order updates. For example, an entered value of 44,60 was changed to 44.6, resulting in the loss of both the comma and the trailing zero. Although the fields were defined as text, they were incorrectly processed as numeric values during expression evaluation. This behavior caused data inconsistencies between the form responses and the Work Order record.

10.4.0

00177078

065334

Parts and related details such as Name and Description were not displayed in service reports generated from Document Templates. Only the quantity appeared, leaving critical information missing in the PDFs. The issue occurred due to incorrect property references in the data mapping logic, which prevented the system from retrieving values from related objects like the Product record.

10.4.0

N/A

N/A

There was an issue with PDF generation in the Background mode when a DataGuide Form was submitted in the Service Task execution flow.

10.3.0

00162226

00172430

061733

063932

A browser specific issue occurred when a Form Action was configured to generate the Document Template in Background mode. Pop-up blockers in these browsers prevented the output window from opening, which caused failures in PDF generation.

The flow is enhanced to handle browser-specific pop-up blocking. After a user submits the form, a consent prompt appears with a message. If the user selects Continue, the PDF generation is triggered on a new tab, which then automatically closes. If the user selects Cancel, the PDF is not generated.

For more information, see Generating PDF on Form Submission.

10.2.0

00174424

064472

In the Go app, the generated PDF did not appear in the Document section after a form was finalized in offline mode.

10.2.0

00175142

064742

An issue occurred where a data table with an expression was added to an existing document template, it did not fetch any results. Without the expression, the data table returned all related Installed Products; however, with the expression applied, no records were displayed even when valid records existed.

10.2.0

00169483

063158

The expression-configured data table in the Document Template did not display any records when a filter was applied, even though qualifying records existed. The table without the filter displayed all records correctly. This issue occurred specifically when both the source and the child objects were the same, and a filter was applied using standard SFM expressions. Additionally, a filter intended to show only labor lines with a specific record type failed to exclude non-matching records, indicating that the filter did not function as expected on related custom Work Order records.

10.1.0

00172430

063932

The PDF did not consistently attach to the Work Order when the checklist was completed and PDF was generated in background execution mode. In some instances, the PDF failed to generate or attach, while in other attempts on the same Work Order, it succeeded.

10.1.0

00162226

061733

The PDF failed to generate when the execution mode was set to background, due to browser pop-up blockers preventing the document window from opening.

10.1.0