INC-192464 · Issue 681858
PackageComponent updated for use with repositories
Resolved in Pega Version 8.5.6
Exporting a zip file created by the Component wizard to a repository resulted in an error, however the same process worked as expected when the zip file was created by the Product wizard. Investigation showed that pxPackageComponent was not kept up to date with new metadata requirements for Artifactory export. This has been resolved by modifying pxPackageComponent step 7 to set Param.ArtifactType to "component" and Param.ArtifactName to [component name]_[component version]. A privilege check has also been added to zipMoveExport.
INC-123033 · Issue 561388
Updated logic for delegating when the RARO exists
Resolved in Pega Version 8.4.2
When trying to delegate a Data Type, the validation error "Update Record Failed: This record is non-versioned and already exists and can not be moved to a different ruleset" appeared. Because data type delegation is dependent upon the existence of a RARO for the delegated data type, when delegating the ruleset of the RARO to accessgroups with the same roles the code was attempting to update the RARO. Updating the RARO determines if the Ruleset of the RARO is unlocked. If the ruleset is locked, then the logic attempts to select a new ruleset, but the RARO cannot be moved to a new ruleset. To resolve this, the logic has been updated so that if the RARO exists, the system will not try to create a new instance.
SR-D93112 · Issue 554909
Added backwards compatibility for migrated when rules
Resolved in Pega Version 8.4.2
After upgrading from v6 to v8, the 'when' rules were replaced with "" in a custom decision tree. In 7.2 and earlier releases, the Rule-Obj-When function alias had its param name as "strName"; this was changed to "blockName" in later versions of Pega. To handle backwards compatibility, the pzEmbedUpgradeToHarnessBased activity has been modified to read the strWhen param value from pyCallParams and set it to blockName params correctly under pyFunctionData.pyParameters data model, conditionally only for Rule-Obj-When function alias.
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-D95797 · Issue 556765
Branch Preference now considered for TestCase rule
Resolved in Pega Version 8.4.2
Setting branch preference from top right worked for all rule types and new rule dialog rightly set the branch, but when attempting to use this configuration for a test case, it only displayed the first branch in the app and did not follow the branch preference. This was due to the system using a separate save modal dialog for test case creation which did not consider this use, and has been resolved by implementing the branch preferences use case to show the direct preferred branch if present.
INC-200416 · Issue 699861
Updated AttachmentPreview control for Account Manager Access Group
Resolved in Pega Version 8.5.6
When using the Account Manager Access group as the default and only access group on a profile, attempting to render a PDF on the click of a link did not work as expected. The render-on-click worked as expected when logged in as the Author and the application was switched to Account Manager. This has been resolved by registering the activity pzAppStorageOkToAttachFile in the pzAttachmentPreview control.
INC-187610 · Issue 672847
Logic made consistent for design time group condition
Resolved in Pega Version 8.5.6
An inconsistency was seen between the logic string that appears when switching from "Group ORs" mode to "Use advanced logic" mode at design time, though whichever mode was used at Action check-in was always properly reflected on the generated proposition filter so there was no runtime impact. This design time issue was traced to the property "pyGroupConditionsByOld " being empty: this property is transient so its value will not be saved into database. This property should be updated whenever user changes the Logic operator from the drop-down, and this has been resolved by adding an intermediate property to hold the old group condition value when it changes.
INC-192833 · Issue 678114
New Application Wizard will default to existing work groups if none are created
Resolved in Pega Version 8.5.6
When using the new application wizard to create a new application, the new app API replaces the old work pools with the newly generated ones. If the new application configuration was done in such a way that classes are not generated due to reusing existing classes, access groups were being generated with empty work pools. To resolve this, the system has been updated to use the existing work pools if the new app didn't generate new work pools.
INC-207309 · Issue 704300
Clipboard page handling updated for encrypted values
Resolved in Pega Version 8.5.6
When retrieving data that contained encrypted properties, the clipboard page either did not load, or if it did load the encrypted properties were not listed on the clipboard. This was traced to use of a read only data page, and has been resolved by updating pzRemovePWD with handling for read only pages.
INC-179769 · Issue 671021
Document generation new line formatting made consistent
Resolved in Pega Version 8.5.6
The GenerateWordDocument API and Generate Document shape were not adding new line to a Word document even when Text Area format was used. This was traced to a difference in document generation which varied between adding \n and adding \r\n for new line, causing inconsistent behavior, and has been resolved.