SR-A18600 · Issue 249163
ErrorShade class added to customize message border
Resolved in Pega Version 7.2.2
The pzGenerateTextInput function has been enhanced with the class "ErrorShade", which allows for customization of the border color of the message when displaying server side errors.
SR-A18600 · Issue 250181
ErrorShade class added to customize message border
Resolved in Pega Version 7.2.2
The pzGenerateTextInput function has been enhanced with the class "ErrorShade", which allows for customization of the border color of the message when displaying server side errors.
SR-A18600 · Issue 249161
ErrorShade class added to customize message border
Resolved in Pega Version 7.2.2
The pzGenerateTextInput function has been enhanced with the class "ErrorShade", which allows for customization of the border color of the message when displaying server side errors.
SR-A18600 · Issue 250180
ErrorShade class added to customize message border
Resolved in Pega Version 7.2.2
The pzGenerateTextInput function has been enhanced with the class "ErrorShade", which allows for customization of the border color of the message when displaying server side errors.
SR-A101626 · Issue 272644
Height properly set for opening report in Portal
Resolved in Pega Version 7.2.2
Height was not being properly set when opening a report in the harness due to the resize function incorrectly handling expanded items. This has been fixed.
SR-B65152 · Issue 315490
Fixed Drag and Drop in it_IT locale
Resolved in Pega Version 7.3.1
Drag and Drop functionality was not working in Data Explorer with Italian Localization (it_IT as operator locale). This was traced to a coding error, and has been fixed.
INC-225687 · Issue 739708
Handling added to avoid incorrect true value for DateTimeisPastOrFuture
Resolved in Pega Version 8.8
When the Function pxDateTimeisPastOrFuture() was called with the arguments "" (the empty String) and "false", it sometimes returned "true" instead of "false". This function internally calls the Function CompareDates() which takes two Strings as arguments. In this case, one is provided by the caller of pxDateTimeisPastOrFuture, the other one is generated at runtime, as the current date/time. As the second argument of pxDateTimeisPastOrFuture, the generated date/time will be the first parameter, while the second one is the date/time argument for pxDateTimeisPastOrFuture. If that argument is the empty String, is will be replaced by the current date/time. This means that the value for the second parameter is determined after the first parameter and that can result in a gap in time by a few milliseconds. This in turn results in "true" as the return value for pxDateTimeisPastOrFuture. This has been resolved by adding handling for a blank string so "false" is returned correctly.
SR-A1350 · Issue 205576
Added support for adding custom GuardrailWarning
Resolved in Pega Version 7.1.9
A customer-created custom activity "addGuardrailWarning" with incoming parameter (WarningMessage) of type Rule-Message with the intent that whenever the new activity was called from another activity, the SmartPrompt-enabled parameter would provide a list of Rule-Message instances starting with any defined on the class of the Step Page (or the class of the calling Activity when the Step Page is blank), and then working up the inheritance hierarchy, much like the behavior provided on other activity methods such as the Data Transform parameter of the Page-New method. However, the SmartPrompt for this custom function only showed rule-messages of pyCategory "Error", or "blank" due to lack of support for this custom Guardrail Warning. In order to support this customization, the function alias pxAddGuardrailMessage has been created and this FA can be accessed by a call-function method in activity as 'Add a message to a page using [Name of the Message Rule]'.
SR-D53622 · Issue 515545
Dataflow Batch performance improvement
Resolved in Pega Version 8.4
Performance issues were seen when running Dataflow Batch with Interaction History lookup. This has been resolved by refining the logic used in the pzIHExecuteSQL function.
SR-B2863 · Issue 275455
Improved offline decision shape handling for GoToPreviousTask
Resolved in Pega Version 7.3
The skipFlow condition in handleNotAFlowAndNotDisplayableShape function in the pzpega_process_engine rules has been updated to better handle offline use of customized GoToPreviousTask decision shapes.