SR-130208 · Issue 198155
Handling added for step page call to DeleteAssignment
Resolved in Pega Version 7.1.8
After upgrade, the pxDeleteAssignment with step page Assign-Workbasket was not working as expected. The error was traced to the 'DETERMINELOCKSTRING' activity being available in Work- class while the local customization was passing the Assign- page as the steps page. Handling has been added for cases when the activity gets called on a page other than primary work page.
INC-136817 · Issue 596489
Added database query optimization and cache invalidation logging
Resolved in Pega Version 8.3.5
Web nodes were going down during deployment due to failed health checks. This was traced to queries firing even when there was no rule change, and was due to unnecessary cache invalidations. An update has been made which will optimize and analyze declarative database queries and capture diagnostic details on any invalidation of the declarative reference information cache.
INC-135065 · Issue 598718
Added database query optimization and cache invalidation logging
Resolved in Pega Version 8.3.5
Web nodes were going down during deployment due to failed health checks. This was traced to queries firing even when there was no rule change, and was due to unnecessary cache invalidations. An update has been made which will optimize and analyze declarative database queries and capture diagnostic details on any invalidation of the declarative reference information cache.
INC-126187 · Issue 564340
Report Definition replaced with a data set for training the data and build model
Resolved in Pega Version 8.4.2
An issue with training the data and build model via an email or chat channel was traced in an exception in logs indicating the inability to execute a Report Definition. This can happen when UDF are removed/disabled in the database or in environments where functions are not allowed to read the blob for performance reasons. To resolve this, the Report Definition has been replaced with a data set.
SR-D83630 · Issue 546144
IsQuestionHidden property added to skip validating hidden questions
Resolved in Pega Version 8.4.2
After configuring a simple question which had a validation rule defined on it and a display 'when' rule configured to show or hide it based on another question condition validation was still being fired on the hidden question and it was not possible to proceed. This has been resolved by adding code to skip validations for a question if it is hidden, based on the pzIsQuestionHidden property.
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-122637 · Issue 183016
MaxFileLength property added to avoid truncating attachment names
Resolved in Pega Version 7.1.8
While adding the attachments to the case using drag and drop functionality, the file name and file description were being truncated. However, a new property named "pyMaxFileLength" is now available as an override in pyDefault Model to set a different name limit. If this property is not set, it will take the default value of 60 and proceed. Also for UI error messages, pyNote property in Data-WorkAttach-File and Embed-DragDropFile in the application ruleset must have the max length limitation removed from there or the MaxFileLength will be overridden by that setting.
SR-124153 · Issue 187971
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-128463 · Issue 193907
Create KeyRing updated for split schema
Resolved in Pega Version 7.1.8
If a command line script is configured (viz. keyringGen.sh) to encrypt user passwords for prconfig.xml databases using Keyring utility, a prconfig.xml could have three database entries but the keyring tool only prompted for two databases and did not allow encrypting password for the user for the third database. The prconfig.xml file requires very specific location information to run: to resolve this, the variables to hold schema name in case of split schema configuration have been added.
INC-119725 · Issue 561752
WSDL consumption via XSD corrected
Resolved in Pega Version 8.4.2
When trying to consume a WSDL from a given URL with XSD, the error "Rule evaluation failed : Canceling rule evaluation, Unrecognized type name 'Name'" was generated. The same WSDL was easily consumed in SOAP UI. This was due to a case mismatch. When processing schema files, RuleGeneratorXSD calls XSDUtils.getStringType to retrieve and validate the type of incoming attributes. To do so, XSDUtils compares the type provided against a static list of attribute types, XSDConstants.java. Because XSDConstants.java is hardcoded to match against the lowercase "name" instead of the standard uppercase "Name", the type was not recognized and the error was thrown. While there was a workaround of replacing "xs:Name" with "xs:string" in the local schema files, this has been resolved by updating XSD_TYPE_NAME to equal "Name" in XSDConstants.java.