SR-119812 · Issue 178547
Added logic to more precisely determine class of referred properties within repeating grids
Resolved in Pega Version 7.1.8
In some work flow scenarios with referring properties within repeating grids, Work Class properties were being returned when Collateral Data Class properties were expected. This was caused by an incomplete reference call within the grid, and the logic has been updated to set the class of a grid on the server to call a new function that parses the property given as a source and determines what its class is.
SR-120701 · Issue 179702
Email listener error handling improved
Resolved in Pega Version 7.1.8
When an email arrived with a zero byte attachment, the email listener was failing to generate a work object. An error was seen in the log, and the listener marked the email as seen even though no WO was created. This has been fixed by suppressing the IOException that arises while processing a zero-size INLINE attachment, allowing the rest of the email message to be processed. An exception will be logged, but the attachment that caused the issue will not be added to the work object.
SR-124691 · Issue 186750
Resolved lost transaction ID while adding and deleting attachments
Resolved in Pega Version 7.1.8
When a file was attached and another one deleted at the same time from a work object, the session transaction was lost. Trying to approve the item generated the message "This action is not allowed as it is outside the current transaction". This was due to a stale transaction ID within the frame, and the FromFrame API has been updated to handle the delete attachment activity so the transaction session of parent frame does not get invalidated.
SR-126177 · Issue 189199
Major ruleset skim logic updated
Resolved in Pega Version 7.1.8
When skimming a ruleset to a new major version, property rules (Rule-Obj-Property) which were available in lower rulesets but withdrawn in a higher ruleset version were skimmed to the new ruleset with their status as Available. This was contrary to expected behavior, as these rules should be ignored and not added to new ruleset. This has been addressed by correcting the logic in the special handling for Rule-Obj-Property types during skimming.
SR-129015 · Issue 196408
Cleaned up section reload on change
Resolved in Pega Version 7.1.8
In a section with a drop down on which an onChange event was added and a refresh section is set as the action, the refresh section calls a data transform and no activity call. However upon execution, there was a pop up with the error message 'Illegal Argument Exception'. When the activity is cleared the section rule should remove the parameter, but the preactivity params were not cleared in the clipboard even after clearing the activity. This has been corrected.
SR-D96254 · Issue 555277
ViewID parameter passed as part of DX API response payload for all application levels
Resolved in Pega Version 8.4.2
When application level was set to '5' (Production), the DX API was configured to skip passing 'ViewID' parameter as part of response payload. This only applied to application level '5' and not to other levels. In order to support enhanced customization, the system has been modified to not consider production level and always pass 'viewID' parameter as part of DX API response payload.
INC-128385 · Issue 564522
Behavior made consistent between SSA and legacy engines
Resolved in Pega Version 8.4.2
There was a behavioral disparity between the legacy execution engine and the SSA engine where the latter was not creating a new page when the index was one above the size of the page list. This has now been corrected in order to make the SSA behavior fully backward compatible with the legacy engine, i.e. a new blank page will be added to the list if the index is one above the size of the list.
INC-126975 · Issue 574805
BrowserFingerprint generation timing updated
Resolved in Pega Version 8.4.2
When trying to 'Show Conflicts' on any Circumstance Template with CSRF enabled, there was an error on screen, the requestor was killed, and the PDC Client displayed a 'Browser fingerprint: undefined' error. Investigation showed that at the time the request was fired, the browserfingerprint had not yet been generated and hence was returned as undefined. This has been resolved by adding the code to generate the fingerprint before the request is invoked.
INC-131961 · Issue 571699
Mobile app correctly determines online status after sleep
Resolved in Pega Version 8.3.5
After not using the mobile device for some hours, the app was not recognizing that the device had become online again and continued to show the red 'offline' bar. Restoring network connectivity required logging off and relogging into the network. This was traced to a bug in Android webview which causes window.navigator.onLine to return as false after wakeup despite the connection being present. To resolve this, version 8.5.103 of PIMC (Pega Infinity Mobile Client) contains new native mechanisms which are exposed to the webview as plugins and that work completely independent of webview.
INC-140701 · Issue 602862
The Report Resource Limit is applied on Job Scheduler
Resolved in Pega Version 8.3.5
The Job Scheduler was ignoring the application-wide limit for maximum number of rows to retrieve that was set on the Report > Settings landing page. If the limit was set on the Data Access tab of the report, it was honored. If it was set on the Application settings rule Pega-RulesEngine.pyMaxRecords it was not honored. This behavior was due to pzUpdateSystemSettings being called by pxRetrieveReportData. In pzUpdateSystemSettings, .pyContent.pyMaxRecords was updated to match the value in px.Requestor.pyReportSettings.pyMaxRecords. In some cases, that was not available and the max amount of records was not limited in that case. This has been resolved by updating pzUpdateSystemSettings to pull pyMaxRecords using @getRuleSystemSetting().