SR-A9699 · Issue 221149
Added handling for CR/LF in imported CSV file
Resolved in Pega Version 7.2
Importing a file failed with a java.lang.StringIndexOutOfBoundsException. On the end user side, the dialog box read 'Uploading...' and then clears the input file name. This was a problem with new line characters within the CSV fields: while importing the file, these new line characters were treated incorrectly and parsed as the end of a row in CSV To correct this, the fields containing new line characters will be enclosed in double quotes while exporting. The import parsing logic was also changed to handle new line characters within the fields.
SR-A8242 · Issue 218454
Check added for double encoded quotes in imported CSV
Resolved in Pega Version 7.2
When the content in a CSV file contained double quotes, it was parsed incorrectly during import if it had been previously edited and saved in Excel. This was due to a double encoding of the quotes, and a check has been added to handle such doubling if it is present in the file.
SR-A6467 · Issue 216163
Check added for externally mapped DB tables during import
Resolved in Pega Version 7.2
While using import/export functionality in the Records tab of Data Designer, the import of the CSV file failed with a DB error due to additional create/update properties being added which did not have corresponding columns for externally mapped tables. To resolve this, the system will check whether the current data type is externally mapped and the create/update properties will not be added to the record in cases where it is an externally mapped table.
SR-A6399 · Issue 219922
Data type local store enhanced to work with multiple opened ruleset
Resolved in Pega Version 7.2
It is a common practice in many complex delivery environments to have two ruleset versions opened simultaneously. However, this can cause issues and errors when work is happening in two different major versions while running the local data storage and the RD is created in the highest open major version. In order to support this dual-ruleset use, the highest open rule set version will be fetched from the list of ruleset versions which are available to the application. RD and data pages will be created in this ruleset version. Following files are modified: pzGenerateDataPages pzGenerateListDataPage pzGenerateLookupDataPage pzGenerateRD pzSetDatatypeContextSettings
SR-A6399 · Issue 220402
Data type local store enhanced to work with multiple opened ruleset
Resolved in Pega Version 7.2
It is a common practice in many complex delivery environments to have two ruleset versions opened simultaneously. However, this can cause issues and errors when work is happening in two different major versions while running the local data storage and the RD is created in the highest open major version. In order to support this dual-ruleset use, the highest open rule set version will be fetched from the list of ruleset versions which are available to the application. RD and data pages will be created in this ruleset version. Following files are modified: pzGenerateDataPages pzGenerateListDataPage pzGenerateLookupDataPage pzGenerateRD pzSetDatatypeContextSettings
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.