SR-128829 · Issue 180467
Added multi-class localization for DisplayRFHarnessErrors
Resolved in Pega Version 7.1.8
When Rule DisplayRFHarnessErrors was in two different classes, @baseclass and Rule-Obj-Flow, the localization check box was previously only available under @baseclass and not for Rule-Obj-Flow. This has been updated so the marked rule in rule-obj-flow is also localized when checked under @baseclass.
SR-128829 · Issue 193680
Added multi-class localization for DisplayRFHarnessErrors
Resolved in Pega Version 7.1.8
When Rule DisplayRFHarnessErrors was in two different classes, @baseclass and Rule-Obj-Flow, the localization check box was previously only available under @baseclass and not for Rule-Obj-Flow. This has been updated so the marked rule in rule-obj-flow is also localized when checked under @baseclass.
SR-130695 · Issue 200024
Added handling for "(" and ")" in parameter value
Resolved in Pega Version 7.1.8
A backwards compatibility issue was found in the declare expression ruleform where if a parameter passed to a function alias contained ")" or "(", the data was not shown in the UI. This has been fixed by modifying the parsing logic to handle cases where parameters passed to the function alias might have an unexpected format such as "(" inside a parameter's value.
SR-130695 · Issue 200339
Added handling for "(" and ")" in parameter value
Resolved in Pega Version 7.1.8
A backwards compatibility issue was found in the declare expression ruleform where if a parameter passed to a function alias contained ")" or "(", the data was not shown in the UI. This has been fixed by modifying the parsing logic to handle cases where parameters passed to the function alias might have an unexpected format such as "(" inside a parameter's value.
SR-129062 · Issue 194086
App Explorer enhancement sets number of properties displayed
Resolved in Pega Version 7.1.8
If there were a large number of properties in a navigation panel of App Explorer, only a few properties were shown and a link displayed 'Show all results'. It was then not possible to optimize a property inside a page list in Work Class as it was displayed under new tab when 'Show all results' was clicked. This was found to be an issue with the behavior of Property Optimization wizard being different when it is launched from App Explorer menu than from when it is launched from RuleForm-->Actions menu. The system now provides an extension point for clients to increase the number of properties that appear in the App explorer. The default is 100, with a max cap of 10000.
SR-129062 · Issue 195029
App Explorer enhancement sets number of properties displayed
Resolved in Pega Version 7.1.8
If there were a large number of properties in a navigation panel of App Explorer, only a few properties were shown and a link displayed 'Show all results'. It was then not possible to optimize a property inside a page list in Work Class as it was displayed under new tab when 'Show all results' was clicked. This was found to be an issue with the behavior of Property Optimization wizard being different when it is launched from App Explorer menu than from when it is launched from RuleForm-->Actions menu. The system now provides an extension point for clients to increase the number of properties that appear in the App explorer. The default is 100, with a max cap of 10000.
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.