SR-C5169 · Issue 349818
Tabs maintain state when new RDL item added
Resolved in Pega Version 8.1
Adding a new item to a repeating Dynamic layout switched all the currently selected tabs in an embedded Tab Layout Group to be the same as the last item. This was an issue with complex configuration RDL having another repeating layout (DLG) with an active 'when' based on repeating context property, and code has been added to handle the previous selected tab state and active when so tabs will retain integrity.
SR-C51948 · Issue 390951
ZipFileListOnServer activity modified to only create instances for zip files
Resolved in Pega Version 8.1
When the Hotfix Manager was run on the ServiceExport directory, the Next and Cancel buttons did not render. Analysis showed the system was creating the PRFile instance for all of the files from the directory, and an exception was being thrown when am instance was created for a file that had illegal characters in its name. To correct this, the pzZipFileListOnServer activity has been modified to only create the instances for files which start with "dl-" and end with ".zip".
SR-C5215 · Issue 357353
Added code to support Sybase DBs in report definition
Resolved in Pega Version 8.1
Running a report definition that is connected to a Sybase DB produced no results in the report browser. This was an issue with the column delimiter not working for Sybase; to resolve this, the code has been modified to rely on the database type rather than the getColumnDelimiter method.
SR-C5234 · Issue 360596
openIfStale() AP updated to ensure aUnlockOnCommit flag is honored
Resolved in Pega Version 8.1
Resolve- Pega-ProcessEngine:07-10-26 (Final out-of-the-box) was acquiring a lock on case but not releasing it later due to Opener not properly honoring the aUnlockOnCommit flag that was passed in via the openIfStale() API. This meant the the database value was always taking precedence over the passed-in flag. To correct this, the openIfStale API has been updated to remove a problematic "else" case. In addition, the system will check whether the lock is available in the map already: if it is, it will set unlockOnCommit to true, or otherwise, under all cases, honor the passed-in unlockOnCommit value.
SR-C53091 · Issue 391230
AddOnly bulk import correctly does not check for existing records
Resolved in Pega Version 8.1
When doing an extremely large bulk import using Addonly, the import API code was performing an existing record check when mapping pagelist properties. This was not the expected behavior, and has been corrected by updating the import java code.
SR-C5318 · Issue 388898
Silverlight digital signature updated
Resolved in Pega Version 8.1
Silverlight Prerequisites have been updated with the latest digital signature.
SR-C5347 · Issue 352087
Catch added for trailing backslash in case pyLabel
Resolved in Pega Version 8.1
Case pyLabel properties with a trailing backslash were failing to render in the UI. To correct this, a try catch and proper escaping have been added before the evaluation.
SR-C5347 · Issue 354157
Catch added for trailing backslash in case pyLabel
Resolved in Pega Version 8.1
Case pyLabel properties with a trailing backslash were failing to render in the UI. To correct this, a try catch and proper escaping have been added before the evaluation.
SR-C5569 · Issue 356377
Fallback method added to handle non-Java SQL timestamps
Resolved in Pega Version 8.1
After the pxCommitDateTime was added to a Business Intelligence Exchange (BIX) extract rule, the property was not extracted in the BIX output. This was traced to the getObject method returning a type of oracle.sql.timestamp when the system was expecting the getObject method to return a java.sql.timestamp. To handle Oracle or other databases that return a non-java SQL type, the resultset metadata will be used as a fallback method to return the java SQL datatype needed.
SR-C5608 · Issue 351744
Configuration for Decision Analytics Settings can be saved
Resolved in Pega Version 8.1
A change made to the default Database for analytics from "Decisioning > Infrastructure > Analytics Center Settings" was not getting saved due to the checkbox for posting the data being enabled which restricted the changes in the saved data. This has been resolved by unchecking the condition to refresh clipboard data on submit after editing the DB configuration.