SR-A940 · Issue 205402
Locking issue resolved for importing PUI jars
Resolved in Pega Version 7.1.9
Errors were being generated when importing PUI framework jars. This was an issue where the savepoints created in Saver.executeUpdate needed to be explicitly released on PostgreSQL to avoid locks from accumulating for each of the nested transactions, and the problem has been resolved.
SR-A990 · Issue 205075
Post-upgrade deferred list mapping reference inserted for new classes
Resolved in Pega Version 7.1.9
After migrating, the processing of the deferredlist while performing an updatestatus operation generated an exception from pzMapCases. This was caused by a class mapping issue where the new classes (InsertRuleSummary, UpdateRuleSummary, DeleteRuleSummary) added in DeferredOperationsImpl did not have interfaces in DeferredOperation. This has been corrected.
SR-A6740 · Issue 214445
Bulk delete activity added for ADM models
Resolved in Pega Version 7.2
In order to support the deletion of ADM models in bulk, an enhancement has been added to remove the unwanted models from the database provided a list of them is given as input. The activity pxDeleteModelsByCriteria has been created; "Used to delete ADM models in bulk. Models to be deleted are determined by the criteria selected by this Activity's parameters; a model is deleted if it matches all selected criteria."
SR-A8236 · Issue 217334
Data flow respects vertical scalability settings
Resolved in Pega Version 7.2
The number of threads per node specified in Decision->Simulation Settings->Topology landing page was not taken into account by data flow execution, leading to the inability to configure vertical scalability per PRPC node and/or exclude certain nodes from data flow execution. This was an error where the configuration was being ignored and a default value was always used, and has been corrected.
SR-A5666 · Issue 215313
Flow Image available in "WhereAmI" option of iframe
Resolved in Pega Version 7.2
In some cases, it was not possible to see a flow canvas when the request was made from external system (e.g.. calling Pega URL from iframe). The framework was not taking into account the case where the frame was embedded in a document from a different domain. The cause of this issue is that the iframe and the parent frame have different origins, which prevents Viewer Data registering correctly. The system has been updated to detect whether the parent frame has the same origin as iframe, then choose correct the parent context to register Viewer Data. The object used to contain viewer data should be created in the right context in order to avoid cross origin exceptions.
SR-A7256 · Issue 218467
Flow image resolution now set by default
Resolved in Pega Version 7.2
In some flows with widely spaced shapes, the resolution of the flow image was insufficient- i.e., the text inside the flow shapes is not legible. The flow image is captured at a user defined zoom level, causing the captured flow images to have non-uniform resolution. The image capture now is done at a default origin and zoom level. The image capture will then restore the user selected zoom level after the capture happens.
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.