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-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.
INC-175533 · Issue 678908
Improved Page compare for page groups
Resolved in Pega Version 8.5.6
Field level auditing on embedded properties sporadically did not report the "old" value when a property was modified even though the page was listed as "Modified". This has been resolved by adding logic to the pxComparePages algorithm to treat Lists and Groups differently. Now Page and Value Groups will use pxSubscript as the primary way to detect add and deletes.
INC-182576 · Issue 677526
Improved Page compare for page groups
Resolved in Pega Version 8.5.6
Field level auditing on embedded properties sporadically did not report the "old" value when a property was modified even though the page was listed as "Modified". This has been resolved by adding logic to the pxComparePages algorithm to treat Lists and Groups differently. Now Page and Value Groups will use pxSubscript as the primary way to detect add and deletes.
INC-192092 · Issue 678449
Info messages added to merge and errors on merge failure
Resolved in Pega Version 8.5.6
Logging used in the Merge Wizard process has been updated to provide feedback as the branches merge. In addition, the merge logic has been modified to use StepStatusFail as opposed to StepStatusGood.
INC-195793 · Issue 697919
Enhanced ruleset validation for portal creation
Resolved in Pega Version 8.5.6
Attempting to create a new portal (web channel) from the app studio using the Creation Wizard with "Branch development preferences" enabled resulted in the error message "No valid rulesets in application preferences". Investigation showed this occurred due to CPM-Portal being specified in the application as the UI class: when attempting to create the portal, the system was evaluating the class against ruleset candidates. The class was not visible to the rulesets in the stack and thus the portal could not be created. This has been resolved by adding validation on UI pages, Int and Data classes in the application to ensure that they exist in user rulesets, and by adding an allowance for classes to exist only in branched rulesets and not the base ruleset during check if the ruleset is present in application stack.