SR-C21036 · Issue 369503
Report definitions with 'Include descendant classes' repaired
Resolved in Pega Version 8.1
The behavior for report definitions was unexpectedly changed as a result of work done to address another issue; if the checkbox for "include descendant classes" was set to true on a report definition, descendant classes with directed inheritance were not included. This regression has been fixed.
SR-C21040 · Issue 362393
rule-ruleset-version correctly cataloged to hotfix
Resolved in Pega Version 8.1
While importing DL for the PCS application, rule-ruleset-version was not getting cataloged to the hotfix manager. This was traced to the failure of the pre-installation initial scan. As recent system changes now support non-versioned rules by looking at the save time, the Rule-RuleSet-Name and Rule-RuleSet-Version will both be treated as valid for scanning and cataloging to avoid this error.
SR-C21054 · Issue 360762
WS-Fed implementation/Support added
Resolved in Pega Version 8.1
Enhancements have been made to support WS-Fed, including the addition of an API to validate SAML assertion signature.
SR-C21190 · Issue 363214
StringIndexOutOfBoundsException fixed for getAccessToken()
Resolved in Pega Version 8.1
A StringIndexOutOfBoundsException appeared while calling getAccessToken(). This was traced to a code error and has been corrected.
SR-C2141 · Issue 371046
Added null value handling for rowPage parameter
Resolved in Pega Version 8.1
Depending on how an application is configured, the value of rowPage parameter sent from client in pzPerformGridAction Activity may not exist on the Clipboard. Null value handling has been added along with a more informative log message.
SR-C21418 · Issue 362714
Stale data clearing improved for WO flow on Mobile
Resolved in Pega Version 8.1
On Mobile, the error "The flow this assignment corresponds to has been removed" appeared after sharing a WO to a desktop user who then sent it back to the Mobile user. This was traced to lingering stale data in a OSCO breakout call for an Online case in the Offline-Enabled app. To correct this, the current thread will be used as context to clear the stale data.
SR-C21469 · Issue 363692
Customization added for removing ET- ID from email subject
Resolved in Pega Version 8.1
The out-of-the-box email channel was exposing the ET-XYZ ID to end-users when it was not desired. To allow for greater customization, a customer-overridable activity 'pyMapEmailToEmailTriage' is now called from pxCreateAndManageTriageWork, and sample code has been included for reference.
SR-C21550 · Issue 362245
Currency control updated for iOS decimal access
Resolved in Pega Version 8.1
Currency control did not allow iPhone users to enter decimals: 'Pattern [0-9]*' was added on markup for mobiles to display number keypad, but the number keypad for iOS does not have the decimal operator. This has been fixed.
SR-C2169 · Issue 356256
Prconfig added to customize retryDelayForAgentQueue
Resolved in Pega Version 8.1
After configuring a http service and trying to process a work object using the service activity, contentious locking and queuing issues were seen when a Queuewhen condition was configured on a service rule and the item was requested using a Request processor rule. This timing issue has been addressed with the addition of a prconfig to customize the delay between two failed attempts of processing a queue item. Sample prconfig:<env name="initialization/agents/retryDelayForAgentQueue" value ="RS1:agent1,1000,RS2:agent2,2000"> Here if there is a failed item for the agent, agent1 in ruleset RS1, t will be queued to run after 1000 milli seconds. for agent2 in RS2, it will be 2000 milli seconds. prconfig value is a comma separated value of the below structure. (<rulesetname>:<agentname>,<delay in milliseconds>,)+ "<rulesetname>:<agentname>" this can be found in queue item XML as "pyAgentName" The same can be declared as DASS as "prconfig/initialization/agents/retryDelayForAgentQueue/default" in "PEGA-ENGINE" ruleset.
SR-C21735 · Issue 362929
Custom modules support repositories
Resolved in Pega Version 8.1
An enhancement has been added to to allow Android Archives (.aar) files to be placed in the libs folder of a custom module, allowing repositories to be added.