SR-A9615 · Issue 218861
Resolved NPE in batch processing Decision data flows
Resolved in Pega Version 7.2
A null pointer exception was being thrown when accessing the batch processing function for Decision data flows if the 'initservices/dnode' dynamic system was set to false. This was traced to a failure of the Flow Action pre-processing activity attempting to call DNodeServiceListener to initialize it, and a check has been added so the Data flow run manager will now try to initialize each time it is asked for an instance if it was not initialized already.
SR-A9147 · Issue 220746
Documentation updated for command-line BIX extractions
Resolved in Pega Version 7.2
The documentation for "Using a stand-alone command-line BIX extract process" has been updated to refer to the BIX 7.1 User's Guide regarding configuring the necessary database connection properties set (prbootstrap, prconfig, etc.).
SR-A5258 · Issue 213386
Documentation updated to reflect change to read-only getProperty pages
Resolved in Pega Version 7.2
In recent versions of the system, getProperty() was modified to support the creation of a property on a read-only page. However, even though the property has been created, it is not possible to set its value. This was not clearly indicated in the documentation, and read-only exceptions were being generated when putString() or setValue() attempted to give a value for the property on a read-only page. The documentation has been updated to clarify this use case.
SR-A6768 · Issue 215093
JDBC connection URL documentation updated for JBOSS installation
Resolved in Pega Version 7.2
An error was found in the JBOSS installation document: the JDBC connection URL defined inside the standalone-full.xml should not have forward slash (/) before the database name, i.e. the format below is incorrect: jdbc:oracle:thin:@//localhost:1521/dbName Instead, the forward slash before data name should be changed to a colon (:), for example: jdbc:oracle:thin:@//localhost:1521:dbName This documentation issue has been resolved by adding a section clarifying the necessary connection information and the method for creating a connection string, along with updating all connection-url steps to either include this information or a pointer to the new section.
SR-A5730 · Issue 213019
Namecase check added to DB2/ZOS split schema installation
Resolved in Pega Version 7.2
An omission in the documentation for the installation wizard guiding the creation of a split schema on DB2/ZOS failed to specify that the database username on the UI screen or in the setupDatabase.properties file as well as the properties in the DB2SiteDependentProperties file are required to be in all upper case. As a result, some installations experienced a runtime exception and an unexpected process termination due to name mismatch. The documentation has been updated. and a check has been added which will take a supplied mixed/lower-case user name and uppercase the value used to set the currentSQLID parameter.
SR-A8556 · Issue 218132
Removed unexpected 'History-' DB instances
Resolved in Pega Version 7.2
Due to an error, 61 additional Data-Admin-DB-Table instances that should not have been part of the media were packaged in the software distribution. The impact was low as all started with 'History-' and contained the name 'Engineering', but their presence and lack of matching associated Class Definitions caused them to be reported on the Database Landing page as "Invalid Class Mappings". We apologize for this confusion.
SR-A8387 · Issue 217780
Added prevention for inappropriate Google Chrome autofill
Resolved in Pega Version 7.2
When login userid and password were stored in the Google Chrome browse and autofill was enabled, Google Chrome was using those values to populate the RuleSet rule form's input field (hidden on UI on Versions tab) and password field (on the Security tab). Those invalid values caused a save failure. To fix the issue, the system will pre-populate the hidden input field so that Google Chrome does not auto fill this field on the client side.
SR-A3950 · Issue 209476
Corrected order of tabbing focus in Activity rules
Resolved in Pega Version 7.2
After opening an Activity rule, the Description text field did not receive focus at the expected point when tabbing through the steps. The activity steps have been rebuilt to correct the tabbing order.
SR-A5453 · Issue 215368
Fixed Edit in Excel with load balancing enabled
Resolved in Pega Version 7.2
Edit in Excel was not working for decision tables if a load balancing was enabled. This was traced to the load balancer port number being added to the RequestHomeURL, causing a malformed strURL for opening the decision table in Excel. A check has been added to evaluate whether the strURL starts with a proper protocol and host instead of checking for RequestHomeURL.
SR-133163 · Issue 203273
Refined property-set expansion to support complex activities
Resolved in Pega Version 7.2
Attempting to expand a property-set in an activity with many steps (20+) caused a failure and the activity locked up. Tin order to support complex activities, the activity call and clipboard functions in this call have been refined for efficiency.