SR-B77745 · Issue 327019
pyCaseBreadCrumb control localized
Resolved in Pega Version 7.3.1
When viewing a case, the pyCaseBreadCrumb control was not localizing the value, instead always displaying the value of pyLabel. This has been corrected.
SR-B50434 · Issue 317985
Struts mapping updated to compensate for behavior change
Resolved in Pega Version 7.3.1
The expectation was that after system startup in a zOS multi-servant environment where each servant has two JVMs which are running at any given point of time, launching SMA after adding a primary node should cause the servant node to show up in the edit page and upon submit the servant nodes should be listed under the primary node under left navigation links. However, after upgrade new nodes added to the cluster in the SMA were not visible due to behavior change between struts releases. This has been addressed by modifying the mapping in struts.xml and tuning some JSP syntax issues in AddNodeIDs.jsp.
SR-B56125 · Issue 317516
WebLogic deployment guides updated for dual user setup
Resolved in Pega Version 7.3.1
The WebLogic deployment guides have been updated to specify that dual user setup requires the addition of the jdbc/AdminPegaRULES datasource with entries added to prconfig.xml. This is similar to the method used for the Tomcat app server.
SR-B56437 · Issue 317515
Schema handling enhancement added for Alternate database option in list view
Resolved in Pega Version 7.3.1
A List view configured to use the Alternate Database setting generated an error when the report was run, due to the schema used by the Reporting Database (defined in the Sandbox-Work database table rule) having a different name than the default Pega database. The main Pega database schema is PEGA721, and the Reporting Database in this case was a schema called PEGA721REP in the same database, causing the table to not be found. As support for the reporting database being located on an alternate database with user specified schema is not available, an enhancement has been added to provide a prconfig that takes the schema for an alternate database and provides the support for ReportDefinition to use it.
SR-B77148 · Issue 325930
Handling added for importing PostgreSQL database Application Bundles
Resolved in Pega Version 7.3.1
Application Bundle imports were failing on db2/MSSQL systems due to syntax differences, generating the message "FATAL ERROR: Encountered an issue applying DDL". Postgres database view definitions include ":: and character varying", but other databases do not require those characters. To ensure compatibility when importing the archives to non-Postgres databases from the Postgres instance, "character varying" will be removed through removeTypeCastingFromPostgreSQL in databaseschemaUtils. It will not be removed for import to another Postgres system.
SR-B77536 · Issue 326544
Check added to keep "::" in imports between PostgreSQL systems
Resolved in Pega Version 7.3.1
Application Bundle imports were failing on db2/MSSQL systems due to syntax differences, generating the message "FATAL ERROR: Encountered an issue applying DDL". Postgres database view definitions include ":: and character varying", but other databases do not require those characters. To ensure compatibility when importing the archives to non-Postgres databases from the Postgres instance, "character varying" will be removed through removeTypeCastingFromPostgreSQL in databaseschemaUtils. It will not be removed for import to another Postgres system.
SR-B64309 · Issue 315889
PDN help properly reflects FlowAnalysis implementation in the Diagram tab
Resolved in Pega Version 7.3.1
The documentation has been updated in the PDN to reflect that the ruleform "Flow Analysis" option is no longer available. The references to this were mistakenly left visible due to a build issue and the help files have now been republished so they match the current implementation of the Flow Analysis option, which is available on the Diagram tab.
INC-128571 · Issue 584752
Auto-process assignments cleanup improved
Resolved in Pega Version 8.6
After configuring auto process with an assignment at the flow end, the perform harness was being presented at the end of the assignment during runtime. This was the result of the newAssign page not being removed as part of the cleanup after auto-processing was done, causing the performB2BAssignmentCheck activity to believe the next assignment existed. This has been resolved by ensuring that auto-process assignments have the newAssignPage removed after the assignment is deleted.
INC-134113 · Issue 591542
Child case locking error message has correct parameter
Resolved in Pega Version 8.6
A locking error message was appearing without the case parameter, showing "Error Message : Could not lock the cover ; has it. Please wait and try again later." This was traced to the cover already being present, causing the step to open the Cover Object to fail. To resolve this, and update has been added to pass the Cover case ID to the field value.
INC-135335 · Issue 588511
Parent flow next step will take precedence over sub-process
Resolved in Pega Version 8.6
ABreadcrumb configured in the screen flow was not displaying at the last assignment when there were multiple embedded sub processes and the last assignment was called in a sub process. This was traced to the parent flow next step information not being passed due to the next step in the sub process being marked as an end shape. To resolve this, the pzFlowSteps7 html control has been updated to pass the parent flow's next step information in this situation.