SR-C71520 · Issue 415399
Robot Manager portal re-launch correctly renders the last active screen
Resolved in Pega Version 8.1.3
Two problems were seen with Robot Manager:1) Opening Robot Manager and then navigating to Workgroup drill-in screen worked as expected, but when the portal was closed and re-launched from Designer Studio, the last active screen (workgroup drill-in) was rendered but with no valid data in it. 2) Opening Robot Manager from email notification worked the first time, but when the same button from the same mail was clicked, the last active screen was rendered with blank or no valid data. This was caused by preActivity and preActivityParams not being sent in the doUIAction call during re-launch of the portal, and has been fixed.
SR-C72252 · Issue 415224
isAncestorOf function now checks whether a child class is defined in the tenant layer
Resolved in Pega Version 8.1.3
After upgrade, the isAncestorOf function was not returning the correct result. Checking the inheritance path for the tenant work class showed the shared layer work class, but after upgrade of the tenant layer, the IsAncestorOf function returned false and the functionality that uses isAncestorOf function failed if the parent class was in the shared layer and the child was in the tenant layer. To correct this, the logic has been updated so that rather than always checking in the shared layer, the system will check whether the Descendant class is defined in the tenant first.
SR-C72385 · Issue 414868
Resolved ClassCast email exception caused by duplicate javamail class loading
Resolved in Pega Version 8.1.3
A ClassCastException was occurring when attempting to configure an email account in conjunction with JBOSS , WebLogic, or WebSphere Liberty. Analysis traced the issue to Class Loading: the WAS application server was providing a default com.ibm.ws.prereq.javamail.jar which conflicted with Pega's out of the box mail-1.5.5.jar, and at run time the JAR provided by WAS was getting picked due to JBoss, Weblogic, and WAS loading architectures from Tomcat. To resolve this, the delegation in PRAppLoader has been expanded to include the "javax.mail." package. This will ensure that Pega delegates to the web-app classloader unconditionally for the email classes. This prevents the ClassCastException caused by the interface javax.mail.Transport and com.sun.smtp.(Implementation Class) being loaded by two different class loaders.
SR-C73425 · Issue 413723
Fixed error when trying to discard a circumstanced Report Definition rule
Resolved in Pega Version 8.1.3
Attempting to discard and delete a circumstanced Report Definition rule resulted in an error on screen, in the tracer, and in the log file. This was caused by the system being unable to identify a reserved property when circumstanced on an embedded page or primary page. To correct this, the saveCircumstanceIndex rule of Rule- activity's first step has been modified to get the circumstanced property for this use.
SR-C74047 · Issue 416353
Automatic Cloud Terminations updated with retry logic and exception handling for nodes being disconnected while in use
Resolved in Pega Version 8.1.3
Agents were being disabled when a node was about to be shut down and the lock operation timed out. This was traced to an issue where the Hazelcast operation timed out trying to communicate with a node that had not yet dropped out of the cluster but did shortly after, and was due to the refactored code around delegating to a cluster component missing a lock method. In order to ensure the cluster component handles such exceptions gracefully, the lock operation now contains retry logic along with exception handling that will return 'false' instead of raising an exception.
SR-C74151 · Issue 412493
Made mobile file attachment sync more robust for low bandwidth situation
Resolved in Pega Version 8.1.3
When using the iOS Mobile Offline application with 'make attachments available offline' checked, low bandwidth on the network could cause the attachment sync to fail and cause the queue to get stuck. To prevent that, rather than return a Socket Timeout the system will return an error code that will cause the file upload to continue instead of rejecting it.
SR-C74176 · Issue 419497
AdminUser login corrected for WebLogic
Resolved in Pega Version 8.1.3
After a successful deployment of Pega on WebLogic 12c Application Server, the server started up without problem and the login page appeared as expected. When attempting to login to the application using the administrator account, the login failed and displayed the error "java.lang.IllegalArgumentException: Header:Location Cannot contain CRLF Charcter" in the browser. This as traced to the URL not being generated correctly due to the padding in the encoding rejecting any CRLF character in the URL, and has been corrected.
SR-C74967 · Issue 419160
Delete and change comparisons updated to support multi-tenant environments with shared classes
Resolved in Pega Version 8.1.3
When creating tenants in paex49, many of the rules did not actually complete importing into the tenant, and when creating new cases, some pages were getting instantiated as classless. This issue was seen only in multi-tenant environments when the same class was present in multiple tenants. Given a Pega class present in multiple tenants, making changes to that class for one tenant triggered invalidation of the dictionary cache that maintains a map with class name + tenant id as key and ClassInfo object as value because of the comparison method used. As a result, dictionary invalidation from one tenant could clear the entry of other tenant and cause the current tenant cache entry to become stale. To address this issue, the system has been updated to remove an entry for a class in tenant context based on key.
SR-C75205 · Issue 418809
Invalid text entry in Date control field now returns current timestamp
Resolved in Pega Version 8.1.3
Inconsistent behavior was seen between entering an invalid date in numeric vs text format. Entering an invalid date in number format resulted in the system replacing the entered value with the text “Invalid date”. Entering an invalid date in text format caused the system to retain the value and not show a validation error. This has been corrected by modifying the date/time formatting to return the timestamp in case the entered text value is incorrect.
SR-C75278 · Issue 415762
Extension added to wrapper activity to allow skipping completed assignments
Resolved in Pega Version 8.1.3
The withdrawal of the pyPopulateCaseContentsWrapper activity rule from the PegaCardSd ruleset caused the wrapper activity in Pega-EndUserUI to be utilized instead, but that activity included a different behavior which resulted in the Completed Assignments checkbox being set as 'true' during processing instead of staying 'false' unless checked by user. This resulted in additional assignments showing when previously only open assignments would show as default. In order to correct this, a new extension "DT(pyPopulateCaseContentsWrapperExtension)" has been provided to set the required fields in order to skip fetching the completed assignments. To utilize this, set the pyShowCompletedAssignments property to true in the extension DT to hide the assignments.