INC-121435 · Issue 563876
Handling added for null requiredskillcount on assignment
Resolved in Pega Version 8.5
If the property pxRequiredSkillCount was blank on an assignment when moved to a workbasket, it was never presented for Get Next Work. To resolve this, handling has been added which will change the null to 0 so the assignment is properly queued.
SR-D65513 · Issue 533277
URL encryption modified for ShowAllOperators
Resolved in Pega Version 8.5
In the control ShowAllOperators the call to pzEncryptURLActionString was introduced to encrypt URLs to avoid hijacking. The content of the URL relied on the pxRequestor.pxWorkGroup property which was resolved using pega:reference tags. This approach worked in versions below 8.x, but in higher versions the tags were not resolved at runtime and results were not displayed. To resolve this, the requestorWorkGroup will be treated as string and passed as parameter instead of using pega:reference tags.
SR-D73536 · Issue 538402
FetchApplicationLogo modified to Filter by rule resolution
Resolved in Pega Version 8.5
It was observed that the Report Definition rule "pzFetchApplicationLogo", referenced by Activity rule "pzLoadApplicationLogo", always returned the older version of the Binary File "webwb • pyapp-logo • svg" because it had been set to retrieve a maximum of one record and in this case the results were sorted in an order where the oldest record was at the top. As the Report Definition did not indicate any sorting, most DBMS were returning the results in no particular or predictable order. To resolve this, "Filter by rule resolution" has now been enabled for RD pzFetchApplicationLogo.
SR-D68235 · Issue 534782
Stale WorkSearchPreference data cleared when switching apps
Resolved in Pega Version 8.5
The D_pyWorkSearchPreferences data page data was not refreshing while switching between apps, causing stale data to be populated under the case search dropdown for all the applications after switching the application from one to another. This has been resolved by removing the D_pyWorkSearchPreferences data page as part of pzProcessApplicationSwitch.
SR-D88141 · Issue 550009
TemplateButton field correctly set read-only
Resolved in Pega Version 8.5
When a control was added to a section using the DX API, a pyTemplateButton field was added to the XML definition of the section with read-only set to 'false'. This has been corrected so the pyTemplate Button field does not allow input.
SR-D92352 · Issue 553617
Completed onChange will reset FileInput value to null
Resolved in Pega Version 8.5
When attaching a file using the "Select File" button, it was not possible to attach the same file after deleting it. Re-attaching the file worked as expected when using Drag and Drop. Investigation showed that the onchange event occurred only when the value of an element was changed, so in this case trying to attach the same file did not change the value of the element and did not fire the onchange. To resolve this, the value of FileInput in pzMultiFilePath Control will be set to null at the end of the onChange event so that an onChange event will be triggered next time even if the same file is added.
SR-111928 · Issue 183474
Assignment locking smoothed for slow network async requests
Resolved in Pega Version 7.1.8
In situations with slow network async Ajax requests, locking was not being properly released between requests. This caused an issue with sub-flows that had a Spinoff Flow configured to route the assignments in the sub-process and the main process to separate operators. In order to resolve this, the close tab process has been updated to remove the corresponding thread and release the lock.
SR-114875 · Issue 171313
Enhanced error handling for WebSphere class conflicts
Resolved in Pega Version 7.1.8
An error caused by a class conflict issue in WebSphere was being generated when exporting Process Flow as XPDL. In order to clarify the limitations in this use, changes have been made to the XSLTRANSLATE Activity to add an extra catch that handles any style sheet errors explicitly and provides an informative error message.
SR-115208 · Issue 178808
Assignment locking smoothed for slow network async requests
Resolved in Pega Version 7.1.8
In situations with slow network async Ajax requests, locking was not being properly released between requests. This caused an issue with sub-flows that had a Spinoff Flow configured to route the assignments in the sub-process and the main process to separate operators. In order to resolve this, the close tab process has been updated to remove the corresponding thread and release the lock.
SR-115208 · Issue 183474
Assignment locking smoothed for slow network async requests
Resolved in Pega Version 7.1.8
In situations with slow network async Ajax requests, locking was not being properly released between requests. This caused an issue with sub-flows that had a Spinoff Flow configured to route the assignments in the sub-process and the main process to separate operators. In order to resolve this, the close tab process has been updated to remove the corresponding thread and release the lock.