INC-191645 · Issue 679536
Updated FieldLevelAuditing logic for page comparison
Resolved in Pega Version 8.7
Optimistic locking was resulting in orphan assignments and the error "Error: Flow Not At Task, Error: Flow Removed". In addition, Get Next Work was causing duplicate Field Level Auditing records. This was traced to a missed use case in the logic used in pxFieldLevelAuditing where previousPage and PrimaryPage are compared to see whether they are equal or not, and has been resolved by adding one more condition to mark previousPage as null when the update date time or commit date time are not updated as part of processing.
INC-194429 · Issue 682882
Updated FieldLevelAuditing logic for page comparison
Resolved in Pega Version 8.7
Optimistic locking was resulting in orphan assignments and the error "Error: Flow Not At Task, Error: Flow Removed". In addition, Get Next Work was causing duplicate Field Level Auditing records. This was traced to a missed use case in the logic used in pxFieldLevelAuditing where previousPage and PrimaryPage are compared to see whether they are equal or not, and has been resolved by adding one more condition to mark previousPage as null when the update date time or commit date time are not updated as part of processing.
INC-162168 · Issue 644731
Refresh works for nested lists
Resolved in Pega Version 8.7
After creating Pagelist A with another Pagelist within (B), a section was created with a repeating dynamic layout to display Pagelist A and a button was added with action set to refresh this section. In the embedded section of the repeating dynamic layout, a nested repeating dynamic layout was created for Pagelist B and a button was set to refresh this section. When using this configuration, the refresh was returning the actionID for Pagelist A regardless of which button was used. To resolve this, an update has been made which will iterate over the stack and append the individual indexes to the encoded value in the pzAPICreateJsonForField function.
INC-161948 · Issue 638963
Locking settings enabled for circumstanced case types
Resolved in Pega Version 8.7
Optimistic locking options were not present for a circumstanced case type, and the option to select the "Lock parent case when an action is performed on this case" check box was not available. However, when the parent case type was enabled with optimistic locking, a circumstanced child case could inherit a lock from its parent. Because "Lock parent case when an action is performed on this case" was not enabled on the circumstanced child case type, trying to update the parent case from the child case and save the parent case resulted in a "Lock not held on parent" error. This was a missed use case, and has been resolved by enabling locking settings in Case Designer for circumstanced case types.
INC-178489 · Issue 659914
Handling updated for custom attachment method
Resolved in Pega Version 8.7
When sending a correspondence using the standard SendSimpleEmail activity, choosing only one attachment from the multiple attachments in the work object by passing the pxLinkedRefTo property from the clipboard page to the AttachmentKeysToSend parameter instead of passing the value to the AttachmentCategoriesToSend parameter successfully sent the message and attached it to the work object. However, opening the correspondence attached to the work object showed the attached file as blank even though the attachment was present in the receiver’s email. Research showed that during the comparison of keys in place of pxLinkedRefTo, pzinskey was used. This caused the comparison to not register as true and the attachments display was skipped. Duplicate files were also being attached due to the previously attached files not being verified. Previous work updated the Data-Corr-Email.Show Html rule to use the pxLinkedRefTo field to find the right attachment. The URL encryption was also updated to ensure the links are functional and attachments can be downloaded. Additional work has been added to expand the use of the pxLinkedRefTo field to Show HTML called from @baseclass.
INC-175595 · Issue 652831
Java Bean import updated to handling differences in Java 7 and Java 8
Resolved in Pega Version 8.7
The behavior of the java bean Introspector class is inconsistent across different versions of the JDK when detecting indexed properties built off of java.util.List objects, causing Java Bean import to generate differently in Java 7 and Java 8. This has been resolved by updating PRIndexedPropertyDescriptor to better handle this JDK difference by resolving indexed read and write methods manually using simple reflection.
INC-136206 · Issue 584327
Handling added for Japanese characters in filename during Safari file upload
Resolved in Pega Version 8.5.1
When using the Safari browser, uploading a file containing Japanese characters resulted in an error message indicating the file was not found afterwards. This was caused by Safari not encoding the flename in the Form Data/Query String as part of the request for file upload, resulting in the filename not being decoded properly. To resolve this, a function named pzBrowserIsSafari has been added to check the browser, and if it is Safari, the system will normalize the filename.
INC-139611 · Issue 587599
Timezone.getDefault function replaced for performance improvement
Resolved in Pega Version 8.5.1
Blocking threads were seen around the GregorianCalendarFactory.clearObject(Object) function, leading to an adverse impact on the performance. TimeZone.getDefault() is a synchronized method call, and under high load this method caused contention when more date-related APIs were invoked. To resolve this, Timezone.getDefault() has been removed and the function has been assigned to a static variable used in the clearObject() API.
INC-135751 · Issue 587287
Null check added for embedded section pyInclude tag
Resolved in Pega Version 8.5.1
When attempting to implement a call to the Pega API casetypes endpoint, the end point /casetypes/{id} returned data for only some of the casetype IDs. For others there was no content in the response and in the logs the error "null at com.pegarules.generated.pzAPICreateJsonForGroup" was seen. This was traced to the use of an old section which did not generate the embedded section pyInclude tag. When the API was called on the same section, it tried to perform an equality check on the variable which gets the pyInclude value, and the null value caused the null-pointer exception. This has been resolved by adding a null check to cover pyInclude in an embedded section.
INC-129443 · Issue 582612
Reopen details correctly saved to pxResolveSummary
Resolved in Pega Version 8.5.1
When cases were reopened using a call to the out-of-the-box Work-.Reopen activity or the Re-open work item link in the Case Tools, the changes to track the reopen in pxResolveSummary were not saved and were lost after a refresh of the case. This has been resolved by updating the ticket handling and modifying the reopenworkobject activity to set the resolve-summary details before re-opening the WO.