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.
SR-C25312 · Issue 373512
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.
SR-C25312 · Issue 379465
Failed service requestors return status along with error message
Resolved in Pega Version 8.1
Queue items related Service requesters were going to broken status with a "Database rollback caused queue item rollback" exception. Investigation showed BatchRequestorTask was not returning error messages in case of failure on a service activity, but rather displayed a generic error message in all error scenarios. This has been fixed by modifying ProcessServiceRequestMethod to return the status of a service activity along with an error message in cases of queue process failure.
SR-C25321 · Issue 372748
Cleared checkbox param to ensure correct exported date/time
Resolved in Pega Version 8.1
When a report definition was configured to display a datetime property with column format as DateTime and DateTime format as "01-Jan-2011 1:00:00 AM EDT" is displayed in report viewer as "09-Apr-2018 02:20:00 PM EDT" (12hr format), the date showed as "09-Apr-2018 14:20:00 EDT" (24hr format) when it was exported to a PDF. In this situation, the report viewer has a querytimestamp field which uses Data time as the control and has the display 24 hours format checkbox checked. This value was added to the parameter page and later was not cleared, causing the other data time fields also display in 24 hours format. To correct this, pzGenerateFormat RUF has been modified to clear this param at the end.
SR-C25564 · Issue 366809
Updated locales to properly use Other Currency option
Resolved in Pega Version 8.1
When the Currency control was configured to display "Other currency" symbol value and the property was populated with USD, the property is displayed as 100.00 / USD in the es_CR, es_GT and es_HN locale, but in local format only for the es_PA, es_NI and es_SV locales. This was an issue with the default Currency Symbol values for es_PA, es_NI, es_SV pointing to old ICU2 formats, and has been fixed by changing the currencysymbol attribute in es_PA.xml, es_CR.xml, and es_SV.xml.
SR-C25702 · Issue 370594
REST POST method sets Content-Type and Boundary
Resolved in Pega Version 8.1
When the REST Connector was set to use the JSON mapping mode for request data and a request attachment page was present, the resulting Multipart message contained the mapped JSON in the "PostData" Part, with the Content-Type header of the Part incorrectly set to "text/plain" rather than the correct value of "application/json." This meant that services consuming the request did not know to handle it as JSON. To fix this, the REST Connector engine module and HTTPClientUtils module have been retooled to match the details and also to handle binary content mapped in as base64-encoded string. This can be overridden via a parameter. The "fat channel" now accepts Part objects so that the Connector implementation can craft a Part with all aspects of the Part, rather than providing only a value. The feature has also been enhanced to better handle Multipart request/response cases.