11.2.0
Release Notes for DataGuide 11.2.0
Release Date: March 27, 2026
Release and Version Details
|
Release
|
App version
|
DataGuide Package version
|
|---|---|---|
|
11.2.0
|
11.2.0.31
|
11.100.0.1
|
 |
A package version change occurs only if there is a code change on the DataGuide package side. If there is only an App code change for any patch, the package version remains the same, while the App version increases.
|
Enhancement — Watermark photo with Geotagging and Timestamp
Feature Overview
The Form Designer now allows configuration of how photos are captured in a form and what watermarks are added to each photo. The Photo question supports selecting the image source and defining metadata such as date, time, location, or selected form fields to add as a watermark. This enhancement ensures that captured images include consistent context and supporting information across all form submissions.
User Impact
Administrators can allow camera-only image capture to enforce compliance requirements or allow both the camera and gallery. The system adds the selected metadata such as date, time, location, or selected form fields directly to the photo. These settings ensure that images include the information required for reporting, auditing, or field verification.
Defects Fixed
The following table lists the defect fixes for the patch release.
|
Case Number
|
Internal Defect
|
Description
|
|---|---|---|
|
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.
|
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.