SR-D43627 · Issue 509801
Keyboard tab support added added for Focus on Date control
Resolved in Pega Version 8.4
It was not possible to use the Tab key to move to a section with date control to launch it, and hitting enter when on a calendar did not open it. To resolve these, tabindex has been added for date/time focus and the calendar will open on enter.
SR-D44215 · Issue 512192
Navigation Breadcrumb honors pyDisplay in navigation link subflows
Resolved in Pega Version 8.4
After configuring a sub process (screen flow) inside a screen flow connected by a decision shape having a fork condition, the Navigation breadcrumb for this subprocess was always visible irrespective of the connector when condition. This was traced to pyDisplay not being considered for subflows while building navigation links, and has been resolved.
SR-D50350 · Issue 519077
Added keydown event handler for JAWS use
Resolved in Pega Version 8.4
Clicking the "Select file(s)" button worked for mouse and keyboard users but did not work when a screen reader was used. Investigation showed that Keydown events were not firing while the JAWS screen reader was running. Since the screen reader was prompting a space key press to activate, an event keycode for space has been added in the pzMultiFilePath control for Select file button to resolve this issue. In addition, a role application has been added for a button to fire keydown events while running the JAWS screen reader.
SR-D53543 · Issue 515178
Correction to JPY decimal precision
Resolved in Pega Version 8.4
Decimal precision has been adjusted to zero for JPY in non-template.
SR-D54068 · Issue 518161
Calendar edit properly disabled when set to no text entry
Resolved in Pega Version 8.4
Clicking the input box of a date control used as Date+calendar popped up the calendar even when the calendar control was disabled and "Allow text entry" was set to No. If "Allow text entry" was set to yes, the entire calendar was disabled. To resolve this, the system has been updated to disable calendar control when 'Allow text entry' is selected to No in the presentation tab.
SR-D55841 · Issue 522696
isAvailable calendar instance will include time zones
Resolved in Pega Version 8.4
When using a custom configuration to route assignments, if today was configured as unavailablefrom date, assignments were still routed to the current operator even though they were not available. Analysis showed that the same Calendar was not used to compare date objStartDate, opUnavailableFrom and opUnavailableTo in the function, isAvailable. The isAvailable FUA calculates objStartDate by getting the calendar instance and setting the time by calculating it from the next business day. However, the calendar instance was created from Calendar.getInstance(), which does not use a time zone, and this resulted in a mis-match of time. To resolve this, instead of creating a calendar instance objStartDate will be formatted to YYYYMMDD format and then converted to the requestor time zone timings using Data Time Utils parseDateTimeString.
SR-D66007 · Issue 526861
Resolved ruleset save issue for Google Chrome/IE
Resolved in Pega Version 8.4
When using particular versions of Google Chrome or Microsoft Internet Explorer, the intermittent error "pyComponentInterfaceClass: <user> does not exist or is not a valid entry for this ruleset and its prerequisites" appeared when attempting to validate an application, and the ruleset could not be saved. This was traced to changes made in the browser around password handling, and has been resolved by explicitly clearing out the pyComponentInterfaceClass if that value is not in use.
SR-D69914 · Issue 531739
Cookie logging restored
Resolved in Pega Version 8.4
As part of security updates, Cookies were restricted from being logged. However, this caused some business use cases such as a custom function call to obtain the list of cookies that are present in the application to stop working. To resolve this, the cookie logging restriction has been reverted.
SR-D16427 · Issue 497222
Multi-nodes rebuild LibraryMetadata to ensure all Rule-Utility-Functions are present on change
Resolved in Pega Version 8.4
When performing a complete Application import into a clean installation, references to certain Rule-Utility-Functions went unresolved during the initial assembly. Investigation showed that after introducing a new Rule-Utility-Library or Rule-Utility-Function on one node in a cluster and then generating that, the other nodes in the cluster did not have the correct LibraryMetaDataCache for that Rule-Utility-Library.Therefore assemblies on those other nodes could be bad and throw a runtime UnresolvedAssemblyError. This has been resolved by modifying the way the Library subsystem processes the node changes events for Library Generation to ensure that each node completely rebuilds the LibraryMetadata for that Rule-Utility-Library so it contains all the Rule-Utility-Functions.
SR-D18036 · Issue 495399
Holdability flag set on connection for using MS SQL in Designer Studio
Resolved in Pega Version 8.4
Static assembler was not working from Designer Studio, displaying the error "com.microsoft.sqlserver.jdbc.SQLServerException: SQL Server supports holdability at the connection level only. Use the connection.setHoldability() method." Investigation showed that ApplicationAssembly.getResultSetForQuery explicitly sets the holdability flag on the prepared statement, and this issue has been resolved by updating the system to set the holdability flag on connection as well.