INC-145535 · Issue 600785
Corrected layout group overlapping content
Resolved in Pega Version 8.5.2
When an editable Table with Master Detail Edit has a section that contains a Layout group (Tab) inside the Master Detail Flow Action, if there are more layout group headings than that can be contained in the screen, a left and right arrow are displayed to toggle between headings in the layout group heading bar. However, timing issues sometimes caused the contents of the layout group to overlap on top of the content below the layout group and the screen was freezing with a loading icon. This was traced to console errors, and has been resolved by adding an 'undefined' check to prevent those errors.
SR-C57879 · Issue 406005
Updated parameter handling for SECU0001 alert for accuracy
Resolved in Pega Version 8.1.2
In the SECU0001 alert, some fields contained incorrect values pertaining to a previous HTTP request, not the one that caused the alert, causing misleading information to be logged and sent to PDC. This was found to be an issue where when unexpected properties were found, the alert was being thrown from an early stage of processing, i.e., during inputProcessing where the current activity had not yet been set to the requestor state and therefore the currentactivity was not there in the stack frame. This has been addressed by getting the activity name from the HTTP request parameters and updating the diagnostic information with it so the alerts will be accurate.
INC-138348 · Issue 599770
Added parameter skipPropertyEvaluation to handle CSS in email HTML
Resolved in Pega Version 8.5.2
While sending an email with custom HTML appended to the email body, a "+" sign in the body was causing the correspondence generation to fail. Investigation showed that if there were CSS classes with braces in the message body, the braces were being removed and replaced via "+" symbol in step 21 of CorrCreate activity. To resolve this, a new Boolean parameter skipPropertyEvaluation has been added in the CorrCreate activity to handle the decision to either evaluate the logic or not, and the pre-requisite will be to resolve all the property references before calling this activity so custom CSS braces { } will be honored when the message body is sent.
INC-132088 · Issue 603084
Updated Tracer for cluster events
Resolved in Pega Version 8.5.2
When running the tracer from the Admin Studio Listener management landing page, Tracer was always fetching data from one node only even though events were generated on another node. This was due to the specific node where the Listener was running being passed to the concern activity while launching the tracer; the Tracer Client node did not have data to check if the event was being populated on another node, and the result was to always fetch data from one node only even though events were generated on another node. To resolve this, the web node ID where the event is running will be passed.
INC-149728 · Issue 608105
Application wizard security updated
Resolved in Pega Version 8.5.2
A user having PegaRULES:User1 role only was able to run the Create Application wizard until an authorization block was reached, yet some rules were created. No operator records were created as part of this process. This was traced to code left in place after the creation of pxAppConfig and pzAppConfig portals, and has been resolved. The New Application wizard UI will display a message to a user when they lack access to build a new application, and an error will be displayed for any attempt to create a new application directly via pzCreateNewApplication to address a scenario where a user might be trying to call the activity without the front end.
SR-119055 · Issue 174515
Corrected drop-down onchange event firing for accessibility mode
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
If a select button was associated to a DynamicSelect control in a Cascading Dynamic Select configuration with WAI, at runtime, the child DynamicSelect list was auto loaded once the value on the parent DynamicSelect list was changed. In accessibility cases, the select button was introduced to be beside the drop down to set the value selected from the drop down. However, in cascading dynamic select, selecting the value from first drop down caused the values in the second drop down to load because an onchange event was fired. In order to handle this correctly, pega_ui_dynamicselect js has been updated to not fire upon change event when in accessibility mode, but instead fire upon click of the select button.
INC-139966 · Issue 606841
JAWS announces popup error message
Resolved in Pega Version 8.5.2
When a form is submitted without giving value to required field, a browser pop up appears. The expected behavior is that the screen reader (JAWS) should move the focus to the field that has error and read the error message However, JAWS was not announcing the error "Value cannot be blank". This was traced to a scenario where if pega.u.d.fieldErrorType === "ERRORTEXT" is true, the class on the span within the error div will be set to "inputSpans", and this resulted in the return of an empty array for document.querySelectorAll("span.iconError.dynamic-icon-error"). To resolve this, support has been added for the "inputSpans" class.
INC-150072 · Issue 621294
Section Include error handling updated
Resolved in Pega Version 8.5.3
When trying to add or include a section in the design template mode of a section rule or during run time of the application, the error "java.lang.StringIndexOutOfBoundsException: String index out of range: -1" was generated. Investigation showed this was originating from the SectionIncludeForm_Post activity of the class Rule-File-Form, and was traced to a system error related to the 'if' condition which verifies the circular reference of the section being newly added. Because this was a system error and not one generated by Pega, there was no handling for it. To resolve this, the sectionincludepost activity in rule-form class has been updated to determine the source and properly handle the error messages.
SR-C66114 · Issue 408082
Resolved pg empty error after db.open and improved error message
Resolved in Pega Version 8.1.2
When opening the data page D_RepositorySettings, the error "pg empty after db.open" appeared in the logs. This was due to the data page referring to the files webwb/zchecked.gif and webwb/zchecked.gif in many sections of the data page rule form despite these files having been removed as part of a recent cleanup meant to reduce storage requirements. In order to resolve this error, the zunchecked.gif and zchecked.gif images have been added back and the error message generated in the RUF pzGetbase64encodedImagehas been improved to add the target filename: "error occurred while opening the image:webwb/zunchecked.gif".
SR-C75689 · Issue 413136
restored to correct "pg empty after db.open" errors
Resolved in Pega Version 8.1.2
When opening the data page D_RepositorySettings, the error "pg empty after db.open" appeared in the logs. This was due to the data page referring to the files webwb/zchecked.gif and webwb/zchecked.gif in many sections of the data page rule form despite these files having been removed as part of a recent cleanup meant to reduce storage requirements. In order to resolve this error, the zunchecked.gif and zchecked.gif images have been added back and the error message generated in the RUF pzGetbase64encodedImagehas been improved to add the target filename: "error occurred while opening the image:webwb/zunchecked.gif"