INC-192464 · Issue 681751
PackageComponent updated for use with repositories
Resolved in Pega Version 8.7
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.
SR-A2 · Issue 203635
Updated use and edit of the 'Search for work' rule
Resolved in Pega Version 7.1.9
After upgrade, an out-of-the-box functionality to search for work items by selecting the case status and selecting a particular field to add as filter on that search was not working correctly and the search icon (which gives the list of status window dynamically) was missing. An attempt to perform a private check out of of the rule generated an error and did not allow 'save as' because it was unable to identify a property pyStringType. This issue was traced to a missing property 'pyStringType' in @baseclass, and this has been added.
INC-164439 · Issue 657995
Setting added to customize using blank Map values
Resolved in Pega Version 8.7
After upgrade to from Pega 6 to Pega 8 some of the Map Value rules were not working. This was due to the handling for blank default values which was changed in Pega 7. In order to support backwards compatibility, a new 'when' rule has been added which allows customizing whether or not blank values are allowed for the Map value default columns. pyAllowBlankValues will default to "false".
SR-D24750 · Issue 507118
Resolved importing PublicFormat file using RuleFromFile Wizard
Resolved in Pega Version 8.2.4
When attempting to create a flow from a Public Format XML file using the Rule From File Wizard, the following error was seen: "Problem invoking function: pega_procom_harvest.performXSLT--(String,String,boolean,HashStringMap)". This was caused by a mapping failure related to the pyComments property in baseclass pega social functionality, and has been resolved with the addition of a new page group property pyComments of type "Data-MO-Annotation-Comment" which applies to "Embed-Rule-Obj-Flow-ProcessModel". In addition, a system property set has been added:'System.setProperty("javax.xml.transform.TransformerFactory","com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl");' to make the security flags work properly in java step of 'transformPublicFlow' activity
SR-A3841 · Issue 208792
Cleaned up 'clear pages after non-use' function
Resolved in Pega Version 7.1.9
When the 'clear pages after non-use' option is selected, all the referencing threads should be closed and the page should be removed automatically. Instead, the document and threads were closed but the data page was not removed. This was traced to the Thread context not being present in the ThreadContainer during thread clean up, and has been corrected.
SR-A3841 · Issue 207560
Cleaned up 'clear pages after non-use' function
Resolved in Pega Version 7.1.9
When the 'clear pages after non-use' option is selected, all the referencing threads should be closed and the page should be removed automatically. Instead, the document and threads were closed but the data page was not removed. This was traced to the Thread context not being present in the ThreadContainer during thread clean up, and has been corrected.
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.
INC-191902 · Issue 677412
Updated security for importing Excel to a decision table via a delegated rule
Resolved in Pega Version 8.7
An error was seen when attempting to import an Excel file into a delegated decision table when using the case manager portal. This has been resolved by correcting a BAC issue for decision table import in the pzRuleDeclareDecisionTableStandard.js file.
INC-171257 · Issue 651734
Expanded results for Proposition Filter Relevant Record Properties
Resolved in Pega Version 8.7
Previously, a maximum of 500 records were returned from pr_data_tag_relevantrecord when using Edit Parameters for the report definition proposition filter rule. In order to accommodate more complex needs, an update has been made to use the D_pxGetClassDataModel data page to fetch all the records and make them available in the dropdown.
SR-A325 · Issue 203740
Added Params to activity display before check-in
Resolved in Pega Version 7.1.9
When calling an activity from another activity, parameters were not being properly retrieved in the calling activity call step unless there was a check-in that called activity. This happened when a private ruleset was not in the user's context and therefore the checked out rule was not picked up. To correct this, the open activity method has been modified to use db.open() .