SR-B79946 · Issue 329632
Removed unnecessary check for duplicate Question AnswerIDs
Resolved in Pega Version 7.4
It was not possible to add a Complex Question into a Question Page when the page already contained another Question with the same AnswerID(s) as the newly added one. This was traced to a call to ValidateAnswerIDofQuestionCollections in the Validate rule of Rule-PegaQ-QuestionGroup, used to check for duplicate answer IDs. Because this code was maintained for backward compatibility and is no longer needed, it has been removed.
SR-B87297 · Issue 339969
Decision tree error fixed
Resolved in Pega Version 7.4
When trying to open a "SetCorrSalutation" Decision tree object, a blank page appeared and the system became unresponsive. Investigation showed this was due to stack overflow errors related to the regex pattern used in the activity 'Embed-Rule-Declare-DecisionTree! pzFBPostActivity', and the rule Embed-Rule-Declare-DecisionTree ! pzFBPostActivity has been modified to optimize the regex.
SR-B80230 · Issue 339620
Fixed exception from AP embedded in read-only
Resolved in Pega Version 7.4
When a work page had two levels of embedded autopopulate properties inside it, ex parentAP and childAP (of list type), refreshing the childAP caused the existing values to be cleared on the parent AP and a ReadOnlyException was generated. This was traced to a missed use case for Autopopulate embedded inside a read-only page list, and has been fixed.
SR-B81636 · Issue 340932
Fixed exception from AP embedded in read-only
Resolved in Pega Version 7.4
When a work page had two levels of embedded autopopulate properties inside it, ex parentAP and childAP (of list type), refreshing the childAP caused the existing values to be cleared on the parent AP and a ReadOnlyException was generated. This was traced to a missed use case for Autopopulate embedded inside a read-only data page, and has been fixed.
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.
SR-B70432 · Issue 330094
AP correctly re-evaluates half-baked data page
Resolved in Pega Version 7.4
When there is a recursion between DP load and corresponding AP load, the half-baked data page is used for populating AP. However, if the autopopulate property content was empty, the complete list data from the data page was not returned even after completion of the loader activity. This was caused by the AP not re-valuating after completion due to the activity not being marked as stale/dirty. This has been fixed.
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.
SR-B88945 · Issue 338260
Fallback toggle added to getDistinctValuesForProperty API
Resolved in Pega Version 7.4
The getDistinctValuesForProperty API was developed to allow for using Distinct Values Indexes to pre-calculate distinct values for certain properties and speed up retrieval. However, it was found that if the distinct value query finds nothing matching the passed filter in the pre-aggregated table, it goes and directly queries the source table to calculate these results. This can cause system performance issues when run against an extremely large table. In order to resolve this, the new method 'disableFallback()' has been provided in Builder to toggle this behavior: when this is called , API = getDistinctValuesForProperty will only fetch records from Index table and will not fallback even if there are no records found in it.
INC-194981 · Issue 681369
Validation error message corrected for delegated SLA rule
Resolved in Pega Version 8.7
When delegating any SLA rule to a Business user like the Manager Access group, editing it from the Case Manager portal did not give an option to configure seconds in that available text field (label hh:mm) even though the validation error stated that the time needed to be in hh:mm:ss format. The pzDelegatedSLAGoal, pzDelegatedSLADeadline and pzDelegatedSLAPassedDeadline sections do not include seconds field, which is a difference from Designer Studio (hh:mm:ss). For this update, the validation error message has been corrected to indicate only hh:mm is used while delegating the SLA rule. An enhancement is planned in a future version to support the hh:mm:ss format for this use.