SR-D76492 · Issue 549970
Added check for test case creation when Cross-site scripting security enabled
Resolved in Pega Version 8.4.2
Test case creation was failing. Investigation showed that when the "Cross-Site Request Forgery" security setting was enabled, the CSRF token and Browser fingerprint were not included in AJAX calls, and the Ruleinskey was not getting passed. This has been resolved by adding a check to evaluate whether security measures are included or not when making a server call from AJAX, and including the tokens required when appropriate.
SR-D76492 · Issue 549968
Added check for test case creation when cross-site scripting security enabled
Resolved in Pega Version 8.3.3
Test case creation was failing. Investigation showed that when the "Cross-Site Request Forgery" security setting was enabled, the CSRF token and Browser fingerprint were not included in AJAX calls, and the Ruleinskey was not getting passed. This has been resolved by adding a check to evaluate whether security measures are included or not when making a server call from AJAX, and including the tokens required when appropriate.
SR-D76492 · Issue 549969
Added check for test case creation when Cross-site scripting security enabled
Resolved in Pega Version 8.5
Test case creation was failing. Investigation showed that when the "Cross-Site Request Forgery" security setting was enabled, the CSRF token and Browser fingerprint were not included in AJAX calls, and the Ruleinskey was not getting passed. This has been resolved by adding a check to evaluate whether security measures are included or not when making a server call from AJAX, and including the tokens required when appropriate.
SR-B51112 · Issue 307512
Silverlight MSI file rebuilt without registry keys for bulk installation use
Resolved in Pega Version 7.3.1
MS Word Compatibility for 2016 Office 365 was generating messages like "Error in updating the Registry Key of (AllowLaunchOfElevatedTrustApps): Object reference not set to an instance of an object." This was due to a newly-added registry keys inclusion feature on Silverlight prerequisites that not supported for installing multiple systems. To address this, the Silverlight prerequisites MSI file has been re-built without the inclusion of registry keys
SR-B69935 · Issue 317991
Pega fetch assignments API updated to call py functions for Robot Manager use
Resolved in Pega Version 7.3.1
The Pega API assignment activity pzGetAssignmentDetailsInternal in ruleset Pega-API:07-10-31 makes a call on line 16 to pzNotifyRobotWorkBasketContainer. This is a platform defect that should have been replaced with pyNotifyRobotWorkBasketContainer. pyNotifyRobotWorkBasketContainer is an extension point activity that is blank in the core platform, but overridden when the Robot Manager app layer is added to the stack. The correct py calls are now present.
SR-B68812 · Issue 317695
Activities updated to use class name to access out-of-the-box templates
Resolved in Pega Version 7.3.1
The out-of-the-box templates were not visible in the implementation layer due to the shipped templates having been created in a horizontal layer tied to a horizontal class. To correct this, the pzGetAllMappedFieldsFromTemplate and pzSetInitialSourceInfo activities have been updated to allow for loading mapping data by getting a selected template class name before calling the load template data page.
SR-B68812 · Issue 310862
Activities updated to use class name to access out-of-the-box templates
Resolved in Pega Version 7.3.1
The out-of-the-box templates were not visible in the implementation layer due to the shipped templates having been created in a horizontal layer tied to a horizontal class. To correct this, the pzGetAllMappedFieldsFromTemplate and pzSetInitialSourceInfo activities have been updated to allow for loading mapping data by getting a selected template class name before calling the load template data page.
SR-131726 · Issue 202769
Fail-over updated to cover server crash scenarios
Resolved in Pega Version 7.1.9
In a testing event, the user session did not properly fail over to another server if the original server was shut down; an error was thrown instead. This was found to be an authentication issue where on node crash, a new requestor was created on the second node and then immediately authenticated as it is SSO. As part of authentication, the mRequiresSpecialProcessingForNodeCrash flag was cleared, meaning the node crash activity was not executed and entire portal was not refreshed. This has been corrected by updating the system to execute crash node activity for SSO cases.
SR-B3591 · Issue 277488
Unit Test Case for DataPage localized for comma decimal indicators
Resolved in Pega Version 7.3
When using Dutch language localization, the use of a comma in a decimal number caused a parsing error when creating a Unit Test Case for a DataPage. Proper handling has been added to handle this localization format.
SR-B3591 · Issue 278006
Unit Test Case for DataPage localized for comma decimal indicators
Resolved in Pega Version 7.3
When using Dutch language localization, the use of a comma in a decimal number caused a parsing error when creating a Unit Test Case for a DataPage. Proper handling has been added to handle this localization format.