SR-A4279 · Issue 210830
Added handling for unknown UpdateDateType property
Resolved in Pega Version 7.1.9
Saving a Flow stream triggers the pzTrackChangesForFlow activity call, which then reads the pxUpdateDateTime property and converts it to Big Decimal for comparison. This conversion requires mode of the property (i.e. DateTime (?M?) in this case) to be known, which is specified in blob as encoded format. When using a PCI framework where the mode of the pxUpdateDateTime property is unknown(???), a NumberFormatException was generated. This has been fixed.
SR-A469 · Issue 210020
Reworked config file search to prevent WebSphere looping
Resolved in Pega Version 7.1.9
During server startup, the engine tries to populate the environment properties by reading the config files for the application server. A problem was found in some installations with WebSphere where trying to locate the XML file containing the information on the server port created an infinite loop that caused the engine startup to hang. To resolve this, the search function call now has been replaced by another method that tries to obtain the same information from config service without having to locate the XML file.
SR-A903 · Issue 204609
Removed primary page requirement for link-object activity
Resolved in Pega Version 7.1.9
When using the link-object activity method with the history checkmark and the specified step page without providing a primary page, the link-object activity method caused a null-pointer-exception when it attempted to fetch data from the pxRequestor page. This was caused by an unnecessary reference to the primary page, and the method to retrieve the value of pyUserIdentifier has been updated.
SR-A92 · Issue 203202
Removed extra slash character being appended in prconfig
Resolved in Pega Version 7.1.9
When configuring prconfig settings, an extra slash was getting appended when the sethtmlbasecontext had trailing slash in the URL. This has been corrected.
SR-A955 · Issue 204118
Fixed typo in error message
Resolved in Pega Version 7.1.9
A typo in an HA status message written to the log has been corrected.
INC-120450 · Issue 561743
Configure view finds existing calculations for properties
Resolved in Pega Version 8.4.2
Modifying a property to ‘calculated: Readonly’ by creating declare expression inside a fieldgroup list (which was created in the data model and refers to a datatype) while adding the fieldgroup list property by selecting from the field in the configure view of a step was not reflected when adding the same list type property inside another step of configure view. Declare expressions were created with page context for embedded fields by default in configure view, but Declare expressions have recently been enhanced and no longer expected to use page contexts. Because Configure view continued to use page contexts, this resulted in calculations that existed not being picked up. This has been resolved by configuring view handling for page list fields specifically to not create new calculations with a page context. Detection of calculations has also been updated to not check for page context to match the recent Declare expression enhancements.
INC-120472 · Issue 571437
Corrected date display on export to Excel
Resolved in Pega Version 8.4.2
Reports which have visible date and Date time properties or values displayed correctly when viewed in PEGA, but when the data was exported to Excel the values were converted to GMT time. Due to this the date fields (with no time stamp) were showing the date less by one day in Excel. This has been corrected.
INC-123033 · Issue 561388
Updated logic for delegating when the RARO exists
Resolved in Pega Version 8.4.2
When trying to delegate a Data Type, the validation error "Update Record Failed: This record is non-versioned and already exists and can not be moved to a different ruleset" appeared. Because data type delegation is dependent upon the existence of a RARO for the delegated data type, when delegating the ruleset of the RARO to accessgroups with the same roles the code was attempting to update the RARO. Updating the RARO determines if the Ruleset of the RARO is unlocked. If the ruleset is locked, then the logic attempts to select a new ruleset, but the RARO cannot be moved to a new ruleset. To resolve this, the logic has been updated so that if the RARO exists, the system will not try to create a new instance.
INC-125822 · Issue 566312
Agile Studio correctly embedding attachments
Resolved in Pega Version 8.4.2
Attachments were not being included in Agile Studio documents for backlogs and sprints as expected. This was traced to the third-party jar "jsoup", which was converting the parameter PegaDocumentObject to pegadocumentobject, causing a mismatch. This has been resolved by adding a check that will replace the converted name with the correct one.
INC-78420 · Issue 566792
Documentation clarified for pxGenerateExcelFile with template values
Resolved in Pega Version 8.4.2
Using Export to Excel created the document, but pxGenerateExcelFile was not replacing template values in the generated output file. To improve the clarity of the necessary configuration, the documentation for pxGenerateExcelFile has been updated to include an example of the usage:This can be used anywhere in platform to export excel file. E.g. - export stories, specifications, requirements etc. Example Usage of properties in template: {.pagelist().property input}\n{.property input}