SR-C95250 · Issue 487995
Null check added to resolve non-impacting InvalidParameter exception
Resolved in Pega Version 8.3
Creating a child case from the SLA goal activity using the 'AddCovered' activity generated the message "Exception in queue item: cannot be null or blank". The error "com.pega.pegarules.pub.clipboard.InvalidParameterException: cannot be null or blank" was also seen. However, no functionality impact was observed. This has been resolved by adding a null check to the getPortalName method, and modifying the HarnessUIBuilder.java file to add safe checks for whether 'portalName' is empty or not.
SR-D8390 · Issue 488002
Handling added for runtime exception on upgrade due to inaccessible external schema mapping
Resolved in Pega Version 8.3
If a system used external schema mapping, attempts to upgrade were failing with the error "Caused by: com.pega.pegarules.pub.database.ConfigurationException: Unable to obtain data source "java:comp/env/jdbc/PegaRULES", as it is undefined". This was traced to configuring external DADNs which were not accessible from the server where the upgrade was being run: an upgrade will fail if it cannot connect to an external datasource even if no changes need to be made to that datasource. However, because a PRRuntimeException was unexpectedly being thrown instead of a Database Exception, the exception was not properly caught and handled. This has been corrected.
SR-D15154 · Issue 488068
CaseType picks up stage name correctly
Resolved in Pega Version 8.3
When adding a new stage in the Stages tab of a case type (pyDefault rule), the stages were shown as rule name instead label after saving and at runtime. Directly adding the Stages in the 'Workflow' tab of the case type showed the stage label as expected. This was traced to an issue with the current row of the table not being properly refreshed, leading to old data being submitted while saving. This has been resolved by adding an explicit "refresh current row" configuration on pyStageName under primary and alternate stage table layouts.
SR-D17056 · Issue 488085
Error messaging updated for using Float parameter in RUF
Resolved in Pega Version 8.3
After upgrade, using an RUF that had a float as an input parameter as part of its signature resulted in any callers providing a double type as an input generating an exception. This has been resolved by forcing a NumberFormatException to be thrown within the IL model when encountering a float value ('1.2f' or '1.2F') as the Double.valueOf() API used in IL correctly parses these values to double.
SR-D13450 · Issue 488138
Corrected Query logging level for Populate_UsepxRequiredSkillsCount
Resolved in Pega Version 8.3
A Query was being logged with Logging level of Error in pzPopulate_UsepxRequiredSkillsCount. This has been corrected.
SR-D18814 · Issue 488259
Enhancement added to fetch HTML attachment from CMS
Resolved in Pega Version 8.3
When email containing HTML was sent to the Listener, some of the characters were not getting decoded properly when viewing. In this case, HTML email content was saved as an attachment in CMS , and this error was traced to the system being unable to fetch the attachment. To resolve this, an enhancement has been added to fetch non-Pega database attachments using pxGetFileAttachmentContent.
SR-D1270 · Issue 488261
database table mapping will check for existing properties before creating them
Resolved in Pega Version 8.3
Using the Database table class mapping tool to map an external database table to a class and create properties according to columns in the table was resulting in the property being created as 'not available' and not case sensitive if the property to be created while mapping was already present in the inheritance hierarchy. This led to an error caused by the property validation failing in the validateReportDesignTab activity. Previously the database table mapping tool did not check to see whether the properties to be created existed already in the parent class hierarchy. With this update, the system will check before allowing the mapping, and if the properties exist in the hierarchy already they will not be populated.
SR-D14601 · Issue 488290
Unique ID generation added for simultaneous multiple text area boxes
Resolved in Pega Version 8.3
In the Interaction portal, adding a task for a interaction using a form with a character-count enabled text area worked as expected when the interaction first opened a task with the character counter text area. However, if a second version of the same task was opened before the first task was completed, the second text area was not responsive or working as expected. This was traced to the system generating the same ID attribute for both instances of the text area character counter span, and has been resolved.
SR-D19944 · Issue 488359
Search initialization logic updated to ensure consistent node member information
Resolved in Pega Version 8.3
The search function was intermittently failing across nodes after restart. Investigation showed that this was due to inconsistent results from search initialization cluster logic using Hazelcast APIs to tell whether or not a given node was part of a Pega cluster. To resolve this, the logic has been updated to rely on ES APIs instead of Hazelcast cluster membership to determine offline nodes.
SR-D19945 · Issue 488360
Search initialization logic updated to ensure consistent node member information
Resolved in Pega Version 8.3
The search function was intermittently failing across nodes after restart. Investigation showed that this was due to inconsistent results from search initialization cluster logic using Hazelcast APIs to tell whether or not a given node was part of a Pega cluster. To resolve this, the logic has been updated to rely on ES APIs instead of Hazelcast cluster membership to determine offline nodes.