SR-B68425 · Issue 317712
Text input focus corrected for repeating dynamic layout
Resolved in Pega Version 7.3.1
Clicking on the label of a text input for the second section in a repeating dynamic layout shifted focus to the first section's text input. This was caused by a missing repeating index for the attribute of the label when used in a RDL and has been fixed.
SR-B68425 · Issue 319425
Text input focus corrected for repeating dynamic layout
Resolved in Pega Version 7.3.1
Clicking on the label of a text input for the second section in a repeating dynamic layout shifted focus to the first section's text input. This was caused by a missing repeating index for the attribute of the label when used in a RDL and has been fixed.
SR-B56708 · Issue 312560
iPad honors disabled datetime control
Resolved in Pega Version 7.3.1
Date time control was not disabled for iPad even when the Disable condition specified was 'true' or Disable When was set to ALWAYS. This has been fixed by adding a disabled attribute for input type date/datetime generated for native date.
SR-B65152 · Issue 315490
Fixed Drag and Drop in it_IT locale
Resolved in Pega Version 7.3.1
Drag and Drop functionality was not working in Data Explorer with Italian Localization (it_IT as operator locale). This was traced to a coding error, and has been fixed.
SR-B56216 · Issue 313130
fr_FR pyCurrency control corrected for using USD property qualifier
Resolved in Pega Version 7.3.1
Due to an incorrect currency evaluation, a pyCurrency property qualifier with a value set as USD in the corresponding property appeared in read only mode for operators using the fr_FR locale. With default locale, "1234567.89" was displayed as "1234567.89 USD" but with fr_FR it was shown as as "1 USD". This has been fixed.
SR-B52001 · Issue 312409
Fixed save-as error linked to missing section property
Resolved in Pega Version 7.3.1
During save-as of a pyUniqueValuesGrid section, the error "pyContainerVisibleWhen : property Pega-ColumnFilterCriteria.isReportDef is undefined". This was caused by a lack of handling for a missing property in the ruleset, and has been corrected by creating the property "IsReportDef" in Pega-ColumnFilterCriteria class.
SR-B47292 · Issue 306742
Fixed jump left on wide grid filtering
Resolved in Pega Version 7.3.1
Filtering on a wide grid containing a scroll bar caused the screen to jump left. This has been fixed by updating the ui_grid JS to better handle the width of grids where width mode is fit to content.
SR-B48665 · Issue 309273
Image checkbox able to trigger local action
Resolved in Pega Version 7.3.1
Given a Check Box which is presented as read-only in a repeating grid with a value presented as image, clicking the row of the repeating grid did not trigger a local action as expected. This was an issue with the system not considering a click on the image of a read-only checkbox to be a click of the row; default event infrastructure treats images as actionable elements and expects them to have their own actions. To support this use, the "p.c.isActionableElement" method has been updated so the system will return false when an image with "chkBxCtl" and "checkbox" class is clicked.
SR-B48665 · Issue 310729
Image checkbox able to trigger local action
Resolved in Pega Version 7.3.1
Given a Check Box which is presented as read-only in a repeating grid with a value presented as image, clicking the row of the repeating grid did not trigger a local action as expected. This was an issue with the system not considering a click on the image of a read-only checkbox to be a click of the row; default event infrastructure treats images as actionable elements and expects them to have their own actions. To support this use, the "p.c.isActionableElement" method has been updated so the system will return false when an image with "chkBxCtl" and "checkbox" class is clicked.
SR-B48517 · Issue 310940
Handling added for Multiple pega:reference tags in paragraph
Resolved in Pega Version 7.3.1
Given a paragraph rule that includes more than one tag, offline testing on a mobile app displayed only the last reference. This was caused by a lack of handling for multiple pega:ref tags in same line, and has been fixed by tweaking regex to do a non-greedy match.