SR-B7225 · Issue 277782
BIX documentation updated for Extract Rules
Resolved in Pega Version 7.3
The documentation outlining best practices for using BIX has been updated to reflect that when extractions are being run asynchronously there must be enough threads for each of the concurrently running extractions. The section "Running an Extract rule using a Pega 7 Platform agent" has been updated to read: "Number of concurrent extracts scheduled has to be limited based on the prconfig "agent/threadpoolsize." Set the prconfig setting agent/threadpoolsize to the max number of concurrent extractions you will be executing. The default value for this setting is 5 and the maximum value is 10.
SR-B7355 · Issue 277915
Actions visible in Perform harness for cases without active assignments
Resolved in Pega Version 7.3
When a stage configured with SLA did not have any active assignments, local actions could be launched from the Review harness but were not visible in the Perform harness. This was caused by the handling for cases without active assignments: virtual assignments are used to process the stage/case wide local actions, but the name of the virtual assignment page was not set and therefore not available later to fetch the local/flow actions. To resolve this, the assignment page name will be checked and set if it is empty.
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-B7620 · Issue 290018
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-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-B7739 · Issue 278003
Backward chaining updated to work with Load-DataPage
Resolved in Pega Version 7.3
A Read only Data Page configured with backward chained declare expressions worked in browser and batch contexts but not with the Load-DataPage method. This was traced to the backward chained expressions were not being triggered when the data page was loaded asynchronously, and that has been enabled.
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-B796 · Issue 283050
Report Definition updated to handle null value field grouping
Resolved in Pega Version 7.3
Report Definitions gave a blank count when grouped by a field with null values. An unnecessary check has been removed from the GenerateGridHTML RUF to correct this issue.