SR-A19503 · Issue 240455
Added configuration field for SOAP response without credentials
Resolved in Pega Version 7.2.1
The system was having difficulty processing a SOAP response if the service did not return an authentication header in the SOAP envelope. This happened when connecting to a SOAP service configured with ws-security username policy which sends only the username but not the password in the SOAP envelope. To correct this, the setting options.setProperty(com.pega.apache.ws.security.handler.WSHandlerConstants.ALLOW_USERNAMETOKEN_NOPASSWORD, "true"); has been added; this option is specific to a connector and is available on the ws-security profile rule form to configure the setting based on the site's SOAP service username policy.
SR-A19539 · Issue 239366
Email listener updates related to DSS settings
Resolved in Pega Version 7.2.1
When sending email with .txt, .png, .docx, or other attachments, the file attachment name was not inlining with other attachment names in the body. This has been fixed. In addition, text attachment names were not listed in the attachments list if DSS was set. The code has now been modified to add the attachment name irrespective of the DSS setting.
SR-A19551 · Issue 240032
LightweightList disabled for dynamic ObjClass + blob
Resolved in Pega Version 7.2.1
If the ObjClass was a property, UseLightWeightList was checked, and the page property .ActivityStatus (data access = Manual) was put in the query to get the blob, Obj-Browse failed with "The property .ActivityStatus was of mode Page List while Read-Only Virtual List.initialize was expecting String mode". Prior to this fix, useLightWeightList was disabled only when the pxObjClass was constant. Since dynamic ObjClass cannot determine the property mode, LightWeightList will be disabled in this scenario to avoid this error.
SR-A19705 · Issue 246975
Hash table logic fixed for invokeMQConnector
Resolved in Pega Version 7.2.1
Logic issues were found and fixed related to hashtable usage for invokeMQConnector.
SR-A19814 · Issue 237605
Entropy pool explicitly coded for UNIX/Linux Oracle installations
Resolved in Pega Version 7.2.1
When running a new install on an Oracle database in a UNIX environment, install was failing repeatedly at the same point when attempting to import one of the application bundle components. This issue was traced to the way the newer versions of the Oracle JDBC driver gather entropy by defaulting to the use of /dev/random. When running in an environment where there this is not a lot of noise, the entropy pool will eventually be empty and the connection will be reset. Earlier versions of the Oracle JDBC driver did not see this issue. To resolve this, in the event that a deployment is being performed on a UNIX/Linux platform using an Oracle database, the -Djava.security.egd=file:///dev/urandom will be specified whenever a java utility is started.
SR-A19858 · Issue 236943
Dialogue handling updated for WS-Security Profile password
Resolved in Pega Version 7.2.1
The presentation format for the password field of the WS-Security Profile outflow page has been changed to no longer display the password in the clear in any resulting dialogue.
SR-A19865 · Issue 240029
Migration script checks for compressed data before inflating
Resolved in Pega Version 7.2.1
While upgrading, the migrate script was failing while trying to create the tables.txt file content. This was traced to data handling. During engine start-up, a check is performed to determine whether bytes are compressed or not, and inflate those that are compressed so they can be read. The migration utility did not have this check, and by default went ahead and inflated. This caused exceptions when encountering BLOBs, as a BLOB contains both CompressedBytes and UnCompressedBytes. A check has now been added to the migration script so inflation is only done as needed.
SR-A19871 · Issue 237975
MS Transport supports Global Resource Settings
Resolved in Pega Version 7.2.1
Documentation indicated that the JMS Transport data instance supported GRS syntax, but attempting to do so generated an error. That support is now available as indicated.
SR-A19972 · Issue 238961
Expanded search re-indexing submit methods
Resolved in Pega Version 7.2.1
When creating an index in the 7 series, the Search Landing Page for indexing did not indicate that the page needed to be submitted to enable the indexes before attempting to start the re-indexing process. An error was thrown in the tracer, but nothing was displayed on-screen to indicate why the system hadn't started indexing. To ensure the expected results, the indexing will begin after the "Submit" button is clicked or if the enable indexing check box has been checked to indicate the system has permission to start indexing without having an explicit submit.
SR-A19986 · Issue 242898
getAppHashForApplication API updated
Resolved in Pega Version 7.2.1
When logged in from an end user portal, editing a decision table and clicking on the gear icon to add a function would show the Function's headers (Example, Activity, string, etc.), but the functions list would not be loaded. This was traced to a timeout resulting from having numerous functions running on the portal combined with a configuration that returned an unowned AppHash when calling a ruleset from the production layer rather than the application layer, and has been resolved by adding logic to write out the AppHash when the appInfo is created from opening the application.