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.
SR-C21787 · Issue 364620
Check added for setting Owner Party in Case API
Resolved in Pega Version 8.1
A problem getting the details of a given case from the case API was traced to the owner party being set in pzGetCaseDetails without checking whether the Owner party exists or not. a check has now been added so the Owner information is added only if the Owner party is present, otherwise the step is skipped.
SR-C21876 · Issue 369542
Enhanced error messages logged for startup exceptions
Resolved in Pega Version 8.1
To support better troubleshooting, enhancements have been made to the logging for the following Exceptions during startup: DatabaseException TransactionFailure RuntimeException Error If one of the above Exceptions is thrown, the associated following message will now appear in the log: "DatabaseException Exception forcing rollback: " (followed by Exception text) "TransactionFailure Exception forcing rollback: " (followed by Exception text) "RuntimeException Exception forcing rollback: " (followed by Exception text) "Error Exception forcing rollback: " (followed by Exception text)
SR-C21996 · Issue 364597
Error message clarified for unauthorized record deletion
Resolved in Pega Version 8.1
When there was an unauthorized attempt to delete records from a delegated data type, the error message appeared stating “A commit cannot be performed” instead of displaying an authorization error. This has been corrected.