SR-129291 · Issue 201471
Added ability to configure node cluster timeouts
Resolved in Pega Version 7.1.8
If a cluster has many nodes, all nodes starting at the same time ended up contending for lock and throwing an exception if they timed out. When the cluster starts, none of the nodes have yet registered their cluster address in pr_sys_statusnodes. There is code that guards against a race condition and includes locking with a timeout controlled by the waitTime (set to 2000ms) and the number of attempts (set to 30) for a total of 1 minute. However, a large number of nodes contending for this lock could exceed these limits. In order to avoid this, the timeout for the lock during check cluster consistency is now configurable using "cluster/consistency/lockattemptdelayms" and "cluster/consistency/maxlockattempts". Additional tuning on this locking is anticipated to be included in ML9.
SR-129291 · Issue 201670
Added ability to configure node cluster timeouts
Resolved in Pega Version 7.1.8
If a cluster has many nodes, all nodes starting at the same time ended up contending for lock and throwing an exception if they timed out. When the cluster starts, none of the nodes have yet registered their cluster address in pr_sys_statusnodes. There is code that guards against a race condition and includes locking with a timeout controlled by the waitTime (set to 2000ms) and the number of attempts (set to 30) for a total of 1 minute. However, a large number of nodes contending for this lock could exceed these limits. In order to avoid this, the timeout for the lock during check cluster consistency is now configurable using "cluster/consistency/lockattemptdelayms" and "cluster/consistency/maxlockattempts". Additional tuning on this locking is anticipated to be included in ML9.
SR-126986 · Issue 197102
Added class handling for creation of embedded pages with page-new method
Resolved in Pega Version 7.1.8
After upgrade, an error was generated while using page-new method to create a new page unless the default page class was present. This occurred when an embedded property was created using page-new with a class that is a child class of the defined embedded class and the parent property of that embedded property was auto-populate/special-java. This was caused by the class being different than the defined embedded class, meaning it was considered as a change to pxObjClass (which is not allowed) and it was not handled. To resolve this, a check has been added to set the right class when creating a embedded page by page-new, using the class of the input page when setting value of a embedded property instead of the defined class if present in input page.
SR-127039 · Issue 190388
Resolved error with Obj-Refresh-And-Lock Method for results browse
Resolved in Pega Version 7.1.8
If the useLightweight List checkbox was checked when trying to do an obj-browse, Obj-Refresh-And-Lock method was generating an error. This was an issue with the virtual clipboard, and has been resolved.
SR-127091 · Issue 193209
Forward chaining commit error resolved
Resolved in Pega Version 7.1.8
A sporadic pyCommitError was observed when performing 'Action' during a 'Phone call' interaction for a specific user. During forward chaining, a malformed variable change that occurs when a page copy happens on a embedded page of a work page is recreated in order to not corrupt the fragment collection cache. Previously, this was done only while evaluating the declare expressions. The system has now been updated to do the same during evaluation of other declarative flavors during forward chaining.
SR-128179 · Issue 197764
Pagination added for ruleset versions ruleform
Resolved in Pega Version 7.1.8
Opening the Developer ruleform to view a ruleset in an environment containing multiple rulesets with thousands of versions presented performance issues where rendering took multiple minutes and scrolling was impossible due to the very large file size. To improve performance, pagination has been enabled for the ruleset versions section.
SR-128192 · Issue 193639
Libraries updated to reflect ruleset versions
Resolved in Pega Version 7.1.8
New ruleset versions were not showing in the Library. This was caused by improper version population: when a version-resolved rule (such as property/section) was created, a a data page would hold the default ruleset version. When a library (which is non version-resolved) was created, the default ruleset version was not reset and it became associated to the library rule. A fix has been added to reset the value of pyRuleSetVersion.
SR-128228 · Issue 193947
Smoothed locking for cloud team logins
Resolved in Pega Version 7.1.8
In a large cloud team, a high number of simultaneous logins caused a requestor lock exception that required a system restart to resolve. This was caused by threads deadlocking while attempting to acquire a common resource during compilation. To resolve this, the locking has been modified to sync requests in order to ease congestion.
SR-128380 · Issue 194162
Refined Excel specifications import
Resolved in Pega Version 7.1.8
Importing specifications from Excel was registering unexpected characters. This was caused by the system mistakenly importing rPh tags from the "sharedStrings.xml" in the "xl" folder, and has been corrected.
SR-128397 · Issue 193116
reRunReport modified to use fully qualified RUF from Procomm ruleset
Resolved in Pega Version 7.1.8
In some cases, re-running a report would fail due to an inability to pick the correct instance of the Rule-Utility-Function getPropertyValue from two rulesets with the same parameters (in the KYC ruleset and the Procomm ruleset). This has been resolved by modifying the reRunreport activity to use the fully qualified RUF from the PegaProcom ruleset.