INC-157119 · Issue 621745
Rule-Message instances added for guardrail warnings
Resolved in Pega Version 8.5.3
Log errors were seen when saving a rule in Dev Studio that generated a guardrail warning from the pzValidateFieldValueReference function. This was related to work done when the function "addwarning" was deprecated in favor of pxAddGuardrailMessage, and has been resolved by adding Rule-Message instances for pxFieldValueMaxLength, pxFieldValueConsecutiveSpaces, and pxFieldValueQuotesNotAllowed.
INC-157119 · Issue 621746
Rule-Message instances added for guardrail warnings
Resolved in Pega Version 8.6
Log errors were seen when saving a rule in Dev Studio that generated a guardrail warning from the pzValidateFieldValueReference function. This was related to work done when the function "addwarning" was deprecated in favor of pxAddGuardrailMessage, and has been resolved by adding Rule-Message instances for pxFieldValueMaxLength, pxFieldValueConsecutiveSpaces, and pxFieldValueQuotesNotAllowed.
SR-124944 · Issue 186362
Handling added for 'agentinfoupdate' map exceptions
Resolved in Pega Version 7.1.8
The function 'agentinfoupdate' updates a distributed map (provided by Hazelcast) for the purpose of an agent landing page. This distributed map was throwing exceptions which did not have proper handling, resulting in the agent scheduler being terminated and thereby stopping agent functionality. The required handling has been added to prevent this situation.
SR-A22958 · Issue 247141
Mobile Client passivation fixed
Resolved in Pega Version 7.2.1
Data pages were not being properly passivated in the mobile client. This was traced to an exception generated by the isFromDictionaryFlag() function when navigating to or from PRE assignment to any other assignment in the flow after hitting unknown list and unknown group settings. As the isFromDictionary function is not necessary here, it has been removed.
SR-D74620 · Issue 537490
Dependent role check added to HaveRole
Resolved in Pega Version 8.3.2
The HaveRole function was not checking the dependent role. This has been corrected.
INC-169796 · Issue 649262
Null check added for pyModes setting
Resolved in Pega Version 8.5.4
The column filtering function was not working after upgrade from Pega 8.1 to Pega 8.5. This was traced to pyModes being set as null for page group properties, and has been resolved by adding a null check before adding the type to avoid getting an improper result from the Formatter Rule-Utility-Function.
INC-169796 · Issue 649261
Null check added for pyModes setting
Resolved in Pega Version 8.6.1
The column filtering function was not working after update from Pega 8.1 to Pega 8.5. This was traced to pyModes being set as null for page group properties, and has been resolved by adding a null check before adding the type to avoid getting an improper result from the Formatter Rule-Utility-Function.
SR-D61971 · Issue 529607
Search Landing Page handling added for email addresses containing hyphens
Resolved in Pega Version 8.2.6
When an e-mail addresse containing a hyphen was entered for the Automated Search Alert functionality, the validation error "Please Enter Valid Email Address(s)" appeared. For example, [email protected] was not accepted. To resolve this, the regexp function used for the email validator has been updated.
SR-D61971 · Issue 529606
Search Landing Page handling added for email addresses containing hyphens
Resolved in Pega Version 8.3.2
When an e-mail addresse containing a hyphen was entered for the Automated Search Alert functionality, the validation error "Please Enter Valid Email Address(s)" appeared. For example, [email protected] was not accepted. To resolve this, the regexp function used for the email validator has been updated.
INC-169796 · Issue 649263
Null check added for pyModes setting
Resolved in Pega Version 8.7
The column filtering function was not working after update from Pega 8.1 to Pega 8.5. This was traced to pyModes being set as null for page group properties, and has been resolved by adding a null check before adding the type to avoid getting an improper result from the Formatter Rule-Utility-Function.