SR-121768 · Issue 182217
Improved locking for check-out-enabled rulesets
Resolved in Pega Version 7.1.8
If a specification with an attachment is defined to a work flow in a check-out-enabled ruleset, then the generated specification and binary file rules were set to the checked-out state and could not be checked in. This was caused by the previous method for lock checking not consistently being applied in custom environments, and the locking has been changed to use an added condition on the InstanceLockedByRuleSet property.
SR-121768 · Issue 182807
Improved locking for check-out-enabled rulesets
Resolved in Pega Version 7.1.8
If a specification with an attachment is defined to a work flow in a check-out-enabled ruleset, then the generated specification and binary file rules were set to the checked-out state and could not be checked in. This was caused by the previous method for lock checking not consistently being applied in custom environments, and the locking has been changed to use an added condition on the InstanceLockedByRuleSet property.
SR-122108 · Issue 182692
Fixed linking for work objects in CalendarViewGadget
Resolved in Pega Version 7.1.8
Using CalendarViewGadget to show calendar with work objects generated a Javascript popup with message "undefined" when clicking on the link of a work object. This "undefined" alert was added for situations where there is no handle passed to the openWorkByHandle desktop API, but there was an incorrect key in the hashtable of strings used to get the localized value. This has been fixed.
SR-122173 · Issue 184843
Expanded correspondence parameters for fax
Resolved in Pega Version 7.1.8
The parameters of Subject and AttachmentsToSend are passed to the CorrNew Activity to create correspondence for the actions Data-Corr-Email and Data-Corr-PhoneText. This has been expanded to also pass those parameters to Data-Corr-Fax.
SR-122191 · Issue 182679
Smoothed post-upgrade ApplicationSetup that uses previously generated LDAP configs
Resolved in Pega Version 7.1.8
An LDAP configuration created under a previous version of the software was generating an NPE after upgrading. This was traced to step2 of the ApplicationSetup activity where the system was expecting a page which was missing at that point due to the user not yet being fully identified. To avoid this, a step has been added to check if the page is available and avoid the NPE.
SR-122213 · Issue 184299
Cache clearing corrected for muti-tenant environments
Resolved in Pega Version 7.1.8
A problem with the caching system in a multi-tenant environment led to a situation where a change in a rule in the shared layer did not invalidate that rule's entry in the tenants' rule cache. This was caused by the clearing of the cache not being fully propagated to all tenants, and the system has been updated to ensure the SMA clear cache fully clears all shared and tenant instances.
SR-122268 · Issue 184969
Tuned handling for child requestors in unauthenticated listener services
Resolved in Pega Version 7.1.8
While executing Queue instruction through JMS listener service, the error "Rule Not Found" was logged. This exception was due to a child requestor invoking the queue activity using the PegaRULES application instead of the current application. This was a side effect of changes made to the Service API which set the requestor authentication to true when the service package is unauthenticated, a change made to run activities that have enabled 'require authentication'. However, the credentials were not passed; the requestor was authenticated and the child requestor created was still unauthenticated, causing this issue. To resolve this, the system will set the access group from Service layer.
SR-122301 · Issue 182078
Revised max datetime value for validation
Resolved in Pega Version 7.1.8
Previously, a date property could have a max set value of 31-Dec-9999. This max date was not working in some time zones due to the input date being converted to GMT for internal operations. This meant that 31-Dec-9999 in some locales was getting converted to 1-Jan-10000GMT, which then failed validation. To correct this, the datetime validity logic has been changed to use "1st Jan 00:00:00.000 10000 GMT" for validation.
SR-122313 · Issue 183428
Database Class Report properly populating Ancestors column
Resolved in Pega Version 7.1.8
When running the Advanced->Reports->Database Class Report, the "Ancestors" column was not populated for tenant level classes. The problem was with the method used to create the report querying the ClassMap using normal, tenantized APIs instead of Shared, so no data was returned. This has been corrected and the class ancestor values are now properly populated in the generated csv file.
SR-122313 · Issue 181185
Database Class Report properly populating Ancestors column
Resolved in Pega Version 7.1.8
When running the Advanced->Reports->Database Class Report, the "Ancestors" column was not populated for tenant level classes. The problem was with the method used to create the report querying the ClassMap using normal, tenantized APIs instead of Shared, so no data was returned. This has been corrected and the class ancestor values are now properly populated in the generated csv file.