SR-B45056 · Issue 328736
XSS filtering added to getClassOfPageReference
Resolved in Pega Version 7.4
XSS filtering has been added to the URL produced when using getClassOfPageReference.
SR-B45056 · Issue 330368
XSS filtering added to getClassOfPageReference
Resolved in Pega Version 7.4
XSS filtering has been added to the URL produced when using getClassOfPageReference.
SR-A8915 · Issue 220454
Jump-back page reference fixed for Tree Navigation and TabbedScreenFlow
Resolved in Pega Version 7.2
When starting a ScreenFlow from a SplitForEach using using TreeNavigation7 and TabbedScreenFlow7, the navigation harnesses were not taking the correct interested page for a jump-back on a previous assignment. This has been resolved.
SR-A4589 · Issue 214117
Obj-Browse reads external mapping with external schema
Resolved in Pega Version 7.2
An Obj-Browse function missing the definition for the property/column lists was not reading the column-property mapping from the Class definition when using external schema. To correct this, getListSelectClause has been modified to use the property name as alias when external mapping is defined and a passed field value is a column name for classes mapped to an external table.
SR-A6903 · Issue 216455
Data Flow correctly handles table encountering null numeric columns
Resolved in Pega Version 7.2
When a data set was created on top of a exposed table which contains some null value in numeric columns, a Data flow executed using that data set used the value '0' instead of the expected null property. This was traced to the Data Flow batch run execution using the DSMClipboardPages, which weren't able to differentiate if a property was present or not and led to null being mapped to 0 in a numeric property. To correct this, the NativeSQLAPI will return null values as empty values when querying a DB and will not use them populate a DSM page or propagate them in the data flow.
SR-A6903 · Issue 216454
Data Flow correctly handles table encountering null numeric columns
Resolved in Pega Version 7.2
When a data set was created on top of a exposed table which contains some null value in numeric columns, a Data flow executed using that data set used the value '0' instead of the expected null property. This was traced to the Data Flow batch run execution using the DSMClipboardPages, which weren't able to differentiate if a property was present or not and led to null being mapped to 0 in a numeric property. To correct this, the NativeSQLAPI will return null values as empty values when querying a DB and will not use them populate a DSM page or propagate them in the data flow.
SR-B85544 · Issue 337433
Fixed RD fail for Japanese characters
Resolved in Pega Version 7.4
Report definition was failing when the Class name contained Japanese characters. This was an issue with the use of default encoding (now deprecated) and an update has been made to ensure the use of 'UTF-8' encoding for URLs.
SR-B94324 · Issue 340952
URL accepts qualifier #comment
Resolved in Pega Version 7.4
The URL was not accepting the # comment when using the pxValidateURL validation rule. This has been fixed.
SR-B89155 · Issue 337930
Case stages correctly displayed in Microsoft Internet Explorer
Resolved in Pega Version 7.4
Case stages were not being properly displayed when using Microsoft Internet Explorer. This was due to the UI kit version of the "pxDisplayStages" rule using the Dynamic Layout with inline format, causing the parent div to not be used for width in Microsoft Internet Explorer. This has been fixed.
SR-A5821 · Issue 214777
Included sections now added as referenced rules
Resolved in Pega Version 7.2
When including one section in another section with the page context as "Use clipboard page", the included section was not being correctly added to the pxRuleReferences page list when the embedded Page property of the section class was set as the using page. RUF pzValidateSectionIncludes has now been modified to consider the embedded Page property of the section class while adding the section in referencing rules.