SR-C24834 · Issue 367704
Multiple Universal SMA fixes made
Resolved in Pega Version 8.1
The following issues in Universal SMA have been fixed:1) “STOP” button not working in Sys Queue Mgmt 2) ClassCastException appearing in Requestor Mgmt 3) Mbean Exception being generated for “Rebuild Classmap" 4) Agent Mgmt Runnable icon always shows X, and Agents were not starting 5) "Get Rule detail" was not working 6) API not found, java.lang.NoSuchMethodException
SR-C24834 · Issue 367706
Multiple Universal SMA fixes made
Resolved in Pega Version 8.1
The following issues in Universal SMA have been fixed:1) “STOP” button not working in Sys Queue Mgmt 2) ClassCastException appearing in Requestor Mgmt 3) Mbean Exception being generated for “Rebuild Classmap" 4) Agent Mgmt Runnable icon always shows X, and Agents were not starting 5) "Get Rule detail" was not working 6) API not found, java.lang.NoSuchMethodException
SR-C25043 · Issue 367314
Corrected displayed records for DT show complete
Resolved in Pega Version 8.1
When @equalsIgnoreCase(, somepropvalue) was used in a column header, clicking on the the Decision table's option "Show Completeness" was displaying all the combinations of each cell value with "<" and ">" appended. This was due to a code fragment left from a logic revision and has been removed.
SR-C25043 · Issue 367544
Corrected displayed records for DT show complete
Resolved in Pega Version 8.1
When @equalsIgnoreCase(, somepropvalue) was used in a column header, clicking on the the Decision table's option "Show Completeness" was displaying all the combinations of each cell value with "<" and ">" appended. This was due to a code fragment left from a logic revision and has been removed.
SR-C25092 · Issue 366511
Fixed proposition status calculation by removing stale calendar object
Resolved in Pega Version 8.1
The status of a proposition was not getting calculated correctly due to the class Calendar object being static. Once it was cached it was being used for all the propositions for the entire server session until next server restart. To correct this, the calendar object has been removed as static final and the time zone object has been made static final.
SR-C25167 · Issue 367695
Search box in Data Designer works for Identifier
Resolved in Pega Version 8.1
The search box in the records tab of the Data designer did not give any result for columns of Identifier type. This was caused by pzMapFilterLogic not containing an entry for Identifier, and the the identifier data type has been added to the pzMapFilterLogic decision table to correct this.
SR-C25178 · Issue 368242
Help updated to clarify valid BIX extraction filter parameters
Resolved in Pega Version 8.1
The help files have been updated to clarify that data pages cannot be used in BIX extraction filters.
SR-C25199 · Issue 366252
Corrected FTP logic for finding files
Resolved in Pega Version 8.1
The file listener is processing all the files, but the FTP client is throwing an error after disconnecting from the port and the file does not arrive on the remote ftp site. This issue was caused by a change in the implementation of the logic, and has been fixed.
SR-C25202 · Issue 365395
Fixed offline sync flow processing corruption
Resolved in Pega Version 8.1
In offline sync, only differences are sent from the device to the server for each action. The server-based sync service merges the differences onto the full work object read from the database. In some cases, data with blank values in the received different JSON was not replacing existing values in the workpage, causing corrupted flow processing and completed cases being returned to the application inactive queue. This was traced to a missed use case for pxObjClass while sending data from client to server, and has been resolved.
SR-C25312 · Issue 377871
New APIs added to get more precise broken process information
Resolved in Pega Version 8.1
Queue items related to a Service requester were going to broken status with a "Database rollback caused queue item rollback" exception instead of displaying the actual exception in the broken process queue. This has been resolved by adding new APIs to get errorMessage and stackTrace.