SR-D33003 · Issue 511229
Queue Batch activity correctly passes chlld process access group
Resolved in Pega Version 8.3.2
Attempting to create an index using the schema tools landing page was throwing an error in the table history stating "Create index failed". Investigation showed that this happened when a user was authenticated without the PegeRULES:DatabaseAdministrator role and then switched to an Access Group with the PegeRULES:DatabaseAdministrator role. The issue was traced to the activity that launched the batch requestor missing the parameter pzUseCurrentAccessGroupForChild due to the Queue Batch activity only passing the default access group authorization. This has been resolved by adding code to pass the additional authorization which will allow users to create an index in this scenario.
SR-D37779 · Issue 514410
DSS setting added to Invalidation query to tune performance
Resolved in Pega Version 8.3.2
Running a RuleInvalidation query on an SQLServer database with a large amount of data was causing performance issues. To improve performance, a force order hint has been added which can be enabled with the DSS setting racache/useForceOrderHintForInvalidationQuery.
SR-D41228 · Issue 512106
DSS added to Request Only Connect SOAP for Robust
Resolved in Pega Version 8.3.2
After upgrade, creating a new SOAP integration set to "Request only" in the Service tab and then running the activity showed requests coming with no response, then failure after three tries. This was traced to previous changes made to support Robust behavior and log failed asynchronous calls, and has been resolved by modifying the Robust support and moving it to a DSS. If “EnableRequestOnlyFaultMapping” is set to “true”, then the ANON_ROBUST_OUT_ONLY_OP option will be used; otherwise, the default behavior will be ANON_OUT_ONLY_OP.
SR-D41229 · Issue 513588
Enhancements added for using AWS file repositories
Resolved in Pega Version 8.3.2
Enhancements have been added to improve the use of AWS file storage: Logging for AWS SDK connection metrics can be activated on a per-repository basis, either through the ruleform or through the DSS storage/class/:/enableMetrics. INFO logging can be enabled on PegaAWSSDKMetricReporter to periodically output averages of recorded metrics for all registered S3 repositories with metric collection enabled, or INFO logging can be enabled on PegaAWSRequestMetricCollector to output recorded metrics on every client call for all registered S3 repositories with metric collection enabled. The interval at which PegaAWSSDKMetricReporter logs metrics at can be configured with the DASS storage/AWSSDK/metricReportingInterval. This DASS is a system-wide setting, and not a per-repository setting. The default reporting interval is 90 seconds, and metric collection is disabled on all repositories by default.
SR-D41580 · Issue 512482
Check added for match of tenant ID class and thread
Resolved in Pega Version 8.3.2
Many bad class exceptions were logged on a multi-tenant system when accessing a worklist or refreshing the browser. This was traced to classDefinitonImpl.getDescendantIter() returning all classes (tenant + shared) because the classDefinition.getTable() API failed to resolve the table for a specific tenant. To resolve this, a condition has been added that will check that the tenant ID of the class matches the tenant ID of the current thread and skip the unmatched classes.
SR-D42241 · Issue 518638
CyberArk support has been added for this release
Resolved in Pega Version 8.3.2
CyberArk support has been added for this release.
SR-D47752 · Issue 513750
Resolved Assembly time error for findPage signatures with two arguments
Resolved in Pega Version 8.3.2
Due to the introduction of IL assembly, an Assembly time error was generated after upgrade when saving a 'when' rule that had a page with the same name defined in both Parameters and Pages & Classes. To resolve this, if the system is generating PegaAPI#findPage or PegaAPI#findPageWithException and passing a null as the second argument, then it will be cast as a String. This will ensure the compiler will not become confused as to the type of null when there are multiple findPage signatures with two arguments.
SR-D48369 · Issue 514304
Reinitializing Full Text Search will shut down Elastic Search regardless of search initialization status
Resolved in Pega Version 8.3.2
Pega search was only sporadically working after converting from standard sandbox-marketing to largesandbox-marketing. This was traced to the Full-Text Search initialization having failed on the app-tier node during re-initialization. As part of re-initialization, the existing node is shut down and the Elastic Search node is started. The shutdown process relied on a boolean flag which indicated if the current status of full-text search initialization was successful. In this case, ES was trying to validate all the cluster level settings, for every save of one of the cluster level settings, but could not due to topology changes in the Util Tier node. The boolean flag indicated initialization had failed so the shutdown process was not invoked, yet the system was attempting to start the second instance of an ES node on the same machine. To resolve this, the shutdown FTS code has been modified to shutdown ES regardless of the search initialization status.
SR-D48392 · Issue 525130
Conditions added for RuleSet names in private edits
Resolved in Pega Version 8.3.2
When a data type data page was referenced by a rule in a different RuleSet to that of data type itself, the data page disappeared from the list of data pages displayed in the data type. A private checkout of report definition Rule-Declare-Pages.pzGetDataPagesForExplorer and the removal of the filter criteria 'IRR.The_version_of_the_RuleSet_of_the_referencing_rule' Less Than or Equal To ' RS.pzRulesetVersion' allowed the data page to reappear. The root cause was traced to the Index-Reference sub report join in the report definition Rule-Declare-Pages.pzGetDataPagesForExplorer incorrectly matching the Index-Reference for the section and thus failing the selection criteria when the referencing rule was in a private edit. To resolve this, an other condition has been added for situations when the RuleSet name of the referencing rule contains "@" (which means the referencing rule is in private edit) to the two RDs. The other change is not to show private edits in the referencing rules, which is done by adding the condition .pxReferencingRuleSetName does not contain "@" in the RD pzGetReferencesInfo. This will not show the number of references and the referencing rules until it is checked in.
SR-D48960 · Issue 517878
Exception stack trace will be included as comments in generated assembly code
Resolved in Pega Version 8.3.2
When there is an exception during assembly time, that original exception message is assembled in the generated code. To improve the process of finding the the root cause by examining the original exception stack, the system has been updated to insert the original exception stack trace into the generated code as comments.