SR-B82203 · Issue 342014
Empty hidden elements stripped when AAR proxy in use
Resolved in Pega Version 7.4
When using IIS WebServer and AAR proxy configuration with high security settings, submitting a form through Microsoft Internet Explorer with hidden input fields that did not have a name attribute resulted in a blank parameter name and value being added. This formed an invalid request that returned a HTTP 200 with no error message. Because Microsoft Internet Explorer does not ignore elements which have empty names, the code has been updated to remove name attributes on pycustomerrorsection hidden elements.
SR-C757 · Issue 343486
Empty hidden elements stripped when AAR proxy in use
Resolved in Pega Version 7.4
When using IIS WebServer and AAR proxy configuration with high security settings, submitting a form through Microsoft Internet Explorer with hidden input fields that did not have a name attribute resulted in a blank parameter name and value being added. This formed an invalid request that returned a HTTP 200 with no error message. Because Microsoft Internet Explorer does not ignore elements which have empty names, the code has been updated to remove name attributes on pycustomerrorsection hidden elements.
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.
SR-B80945 · Issue 336458
Added field for additional domain used for document source
Resolved in Pega Version 7.4
When attaching a file to the work object in an IAC setup, the file was attached but the busy indicator continued to run. This was caused by cross domain name errors , and has been fixed by creating a new HTML rule "pyDomainOverride" where a domain name can be added. E.g.: document.domain = "abc.com".
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-C4390 · Issue 351249
Clipboard page fixed for evaluating Rule-Access-When condition
Resolved in Pega Version 7.4
After logging into the application and accessing the work objects from the worklist, a sporadic error would appear when evaluating Rule-Access-When conditions even though the required page being evaluated against has the data populated. Evaluation showed the execution of the Rule-Access-When condition was failing because the incoming primary page was null, and this was traced to an incorrect clipboard page name in AccessEvaluatior.java. This has been fixed.
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.