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-B8129 · Issue 280611
Resolved DATA-ADMIN-LOOKUPLIST authentication error
Resolved in Pega Version 7.3
After upgrade, the security access error "You lack access required to execute RULE-OBJ-ACTIVITY DATA-ADMIN-LOOKUPLIST was encountered while performing an obj-save during the creation of a Modal operator ID. This was traced to a difference in how an authentication activity was called, and has been fixed.
SR-B8133 · Issue 277199
Support added for cloning SLA agents
Resolved in Pega Version 7.3
The SLA worker agent was not working as expected based on a prior recommendation to clone agents. The cloned agents are not handling any requests. The original agent is still working, but all 3 clones do not perform any work. 6 nodes, for agents per node, and on each node only the original node is working. Cloned agents were not processing work in production if they were duplicated from SLA agents. In order to support this use, a new feature has been added to agent to allow dequeueing pages queued for another agent. This new configuration setting clones Pega-ProCom to multiple custom rulesets or creates a new agent rule in a custom ruleset with multiple rows for the ServiceLevelEvents agent in that rule. Example:
SR-B8793 · Issue 278410
Flow warnings show consistently
Resolved in Pega Version 7.3
Due to conflicting handling of temporary pages by two different processes within the Rule-Save function, warnings were only displaying intermittently as flow rules were saved, refreshed, or checked in. To ensure consistent handling, a single internal parameter has been added that will be used for creating/removing temporary pages
SR-B8793 · Issue 278405
Flow warnings show consistently
Resolved in Pega Version 7.3
Due to conflicting handling of temporary pages by two different processes within the Rule-Save function, warnings were only displaying intermittently as flow rules were saved, refreshed, or checked in. To ensure consistent handling, a single internal parameter has been added that will be used for creating/removing temporary pages
SR-B9662 · Issue 282622
Silverlight version upgraded and URL obfuscation error fixed
Resolved in Pega Version 7.3
The "Create Merge Document" functionality failed with error "Silverlight Control ERROR in 'ProcessHttpResponse'" when when the Pega node was accessed via load balancer. To correct this, the SL Pre-Reqs installer version has been upgraded to the MSI version which supports automated installations and a URL obfuscation error in section WordMergeSL has been corrected.