SR-124473 · Issue 186179
Added handling for unauthenticated asynchronous SOAP service
Resolved in Pega Version 7.1.8
After implementing changes to work around an error with SOAP authentication, the unauthenticated asynchronous SOAP service generated an error and failed to complete. This was due to the changes to the authentication process omitting the asynchronous mode case when a SOAP service that intended to not use authentication ends up calling a sub-activity that requires authentication. This use case is now covered.
SR-124763 · Issue 188692
UpgradeOnOpen style sheet handling corrected
Resolved in Pega Version 7.1.8
The UpgradeOnOpen activity was run each time a harness was opened on the Developer Portal. This was inefficient, but also caused some manual UI changes to revert on the refresh due to the style sheet being incorrectly reset by the UpgradeOnOpen activity. This has been corrected.
SR-124938 · Issue 189679
Resolved NPE during Agent execution
Resolved in Pega Version 7.1.8
If the connection pool size for eis/PRAdapter (default 10) was too low for the work environment, all agents in few application nodes saw a NPE and were unable to process any messages un until the node was restarted. As part of resolving this issue, it is recommended to increase the pool as necessary and monitor. The system has been updated such that if an agent is unable to startup due to any reason, that agent will be skipped by MasterForNewAgents and the process will continue. Previously, if any agent failed during startup with an exception, all other agents were skipped as well. The exception will be logged.
SR-124944 · Issue 186362
Handling added for 'agentinfoupdate' map exceptions
Resolved in Pega Version 7.1.8
The function 'agentinfoupdate' updates a distributed map (provided by Hazelcast) for the purpose of an agent landing page. This distributed map was throwing exceptions which did not have proper handling, resulting in the agent scheduler being terminated and thereby stopping agent functionality. The required handling has been added to prevent this situation.
SR-124989 · Issue 188104
Added error handling for passivated dashboard tab
Resolved in Pega Version 7.1.8
If the dashboard tab has been ide for 30 minutes or more, clicking on links on the tab generated 'not found' errors and NPE exceptions . This failure was traced to the passivation process, which does not save read-only pages and has been resolved by modifying change tracker logic to not send null values when read-only data page is not present.
SR-125192 · Issue 189446
Thread Name displayed in RemoveInactiveThread API
Resolved in Pega Version 7.1.8
An enhancement has been added to display the thread name when throwing an exception during thread deletion: "You may not remove the "+aThreadName+" thread currently processing".
SR-125520 · Issue 194874
Open Authoring OCX and other certificates renewed
Resolved in Pega Version 7.1.8
In order to ensure ActiveX and other helper programs continue to work properly, the components have been re-signed with a digital certificate expiring 12-Mar-2018.
SR-125610 · Issue 189352
Added handling for property-defined declare value list indexing
Resolved in Pega Version 7.1.8
When adding or updating entries in a value list, the corresponding index entries were not getting created in the database. This was caused by handling that was missing from the minimum feature string clipboard properties that were recently introduced for better performance. These strings get created when it's not a reference property and has no declaratives defined etc. In this case, a declare index that is defined on the value list property should not have those elements be minimum feature properties. To correct this, the code has been changed to pass the featureID of the parent property.
SR-126011 · Issue 195418
RUF 'hasMessages' working with Declarative Pages
Resolved in Pega Version 7.1.8
Attempting to execute a Declarative Page with the RUF 'hasMessages' as a precondition caused a NPE. The error was caused by a null page call, and has been corrected by adding a null check for pageVarName and adding a find page call.
SR-126011 · Issue 195591
RUF 'hasMessages' working with Declarative Pages
Resolved in Pega Version 7.1.8
Attempting to execute a Declarative Page with the RUF 'hasMessages' as a precondition caused a NPE. The error was caused by a null page call, and has been corrected by adding a null check for pageVarName and adding a find page call.