SR-B7620 · Issue 289885
PopulateCaseContents activity updated
Resolved in Pega Version 7.3
The PopulateCaseContents activity has been updated to better handle missing or empty properties to ensure the flow name and RefObjectClass values are populated properly.
SR-B7621 · Issue 278634
Activity created cases open correctly
Resolved in Pega Version 7.3
When a case was created through an activity, an error was generated when opening the case and clicking to open assignment. This was traced to an incorrect page name being passed if the primary page was different, and has been resolved by modifying the CompleteAssignment activity Step 19 to check the precondition of Page name.
SR-B7942 · Issue 284735
PDF barcode generation from eForm given configurable parameter checkbox
Resolved in Pega Version 7.3
When generating a PDF file based on an eForm that contains barcodes displayed via base64 encoded images, making the file read-only by using ConcatenateEForm's PerformFieldFlattening option prevented the barcodes from displaying. This was due to an "append" flag being passed to the 3rd party iText Library API "PdfStamper", and has been resolved with the addition of a flag (EnableNewVersion) in the "GenerateEForm" activity. The parameter will be by default true and may be unchecked for false, and is accompanied by a tool tip on hover of the checkbox as well as iText help.
SR-B7942 · Issue 285735
PDF barcode generation from eForm given configurable parameter checkbox
Resolved in Pega Version 7.3
When generating a PDF file based on an eForm that contains barcodes displayed via base64 encoded images, making the file read-only by using ConcatenateEForm's PerformFieldFlattening option prevented the barcodes from displaying. This was due to an "append" flag being passed to the 3rd party iText Library API "PdfStamper", and has been resolved with the addition of a flag (EnableNewVersion) in the "GenerateEForm" activity. The parameter will be by default true and may be unchecked for false, and is accompanied by a tool tip on hover of the checkbox as well as iText help.
SR-B8478 · Issue 278805
ExtractSection data transform optimized
Resolved in Pega Version 7.3
The code in pzExtractSectionPostDT and pzExtractSectionPostActivity has been optimized to improve data transform processing time.
SR-B8696 · Issue 279855
Support added for FCM GetNextWork
Resolved in Pega Version 7.3
When using Federated case management (FCM) to get next work, the work object pulled was not assigned to the operator. This was due to the implementation of FCMR not supporting the moving of workbasket assignments to worklist through get next work. To support this use, the following functions now accept extra parameters as last param: FCMRGetNextWork FCMRGetNextWorkItem FCMRProbeNextWorkItem This will enable distinguishing between normal GNW and federated GNW, and it is possible to override any py rule call MoveToWorklist.
SR-B9998 · Issue 279141
Improved handling for apostrophe in email addresses
Resolved in Pega Version 7.3
In order to improve mail handling, the system will now only remove the the starting and ending apostrophe in an Email address and will not strip apostrophes in the middle of an address.
SR-B7729 · Issue 277669
Resolved file upload error for locales with special language characters
Resolved in Pega Version 7.3
Uploads to Pulse were failing when the file names or file paths contained special Turkish characters. This was an issue with the conversion to lower case changing the length of the string for some locale packages and has been resolved by swapping the call to string.toLowerCase for a call to StringUtils.indexOfIgnoreCase.
INC-121435 · Issue 563875
Handling added for null requiredskillcount on assignment
Resolved in Pega Version 8.2.7
If the property pxRequiredSkillCount was blank on an assignment when moved to a workbasket, it was never presented for Get Next Work. To resolve this, handling has been added which will change the null to 0 so the assignment is properly queued.
INC-122149 · Issue 562783
Corrected approval step task message
Resolved in Pega Version 8.2.7
When a case progressed to the approval step, the task name did not properly appear as part of the "Please approve or reject this" message. In another scenario, a portal which supported locale switching was not translating "Please approve or reject this" when the locale was switched, but instead displayed the message in the original language. Investigation traced this to the pzInstructionsForApproval data transform storing the localized field value, causing it to persist inappropriately. This has been resolved.