SR-C80200 · Issue 494446
Resolved Sporadic ControlBuild error in sections
Resolved in Pega Version 8.3.1
After upgrade, a sporadic error was seen with sections of a VTable after a server restart where a portion would not load and the error "com.pegarules.generated.html_property.ra_stream_pxtextinput_1786000787_default incompatible with com.pega.pegarules.pub.runtime.ControlBuilder" was seen. This issue was traced to invalid generation of an assembly parameter map for random sections the first time the table was called after restart. To resolve this, the system will now allow assembly parameter generation for a second time when they are empty, and the assembly parameters preparation will be handled as a synchronous process.
INC-173436 · Issue 648821
Performance improvement for Application Save: Node Level Data Pages
Resolved in Pega Version 8.7
As part of new functionality introduced in 8.3, data types defined in the application record will be turned into data objects on Application save. As part of this process node level pages are invalidated and reloaded and there is an explicit commit that marks the Application record as dirty and sends any calls for the application record to the database for fresh records. In a multi-node environment, the number of queries to get the application record being saved became exponentially higher and performance impacts were seen. This has been resolved by updating the system to skip eager loading of the data page definition when an access rule or application definition is saved.
INC-192979 · Issue 678361
Performance improvement for Application Save: Node Level Data Pages
Resolved in Pega Version 8.7
As part of new functionality introduced in 8.3, data types defined in the application record will be turned into data objects on Application save. As part of this process node level pages are invalidated and reloaded and there is an explicit commit that marks the Application record as dirty and sends any calls for the application record to the database for fresh records. In a multi-node environment, the number of queries to get the application record being saved became exponentially higher and performance impacts were seen. This has been resolved by updating the system to skip eager loading of the data page definition when an access rule or application definition is saved.
SR-D28034 · Issue 497837
Asynchprocessor generation code deprecated from distribution
Resolved in Pega Version 8.3.1
During a Pega Rules Upgrade of the environment, the error "duplicate key value violates unique constraint "pr_data_admin_pk" was observed. This exception originated from the "Upgrade Context" target while executing a query to fetch the missing ASYNCPROCESSOR requestors for all available system names, and was caused by the system attempting to insert a single ASYNCPROCESSOR requestor more that once in the shared layer. The need to generate missing requestors only applied for installations where a custom system name was provided to the deployment properties (setupDatabase), so by default the asyncprocessor generation code has been removed from the distribution as it is no longer required for upgrades. Default system behavior now is to use system-runtime-context in place of async requestors.
INC-185266 · Issue 676581
Index table correctly populates after migration
Resolved in Pega Version 8.7
After creating a product file with work instances, only some records were populating in the index-workpartyuri class through index rule. Investigation showed that if the IDs specified for the Work Range started with the same digits as were seen after the case prefix (e.g. W-1, W-1000, or W-22, W-2201) then only the indexes for cases that start with W-1 or W-22 were included in the export. This was traced to a step in AddPartyIndexWhenCondition where the EstimatedWorkPrefix local variable was calculated: the java step extracted anything that was the same from the start of the To and From range without taking into account the possibility that some digit characters after the "-" could be the same. To improve the accuracy of the prefix estimation, "-\d" will be used to make an educated guess.
INC-138348 · Issue 599770
Added parameter skipPropertyEvaluation to handle CSS in email HTML
Resolved in Pega Version 8.5.2
While sending an email with custom HTML appended to the email body, a "+" sign in the body was causing the correspondence generation to fail. Investigation showed that if there were CSS classes with braces in the message body, the braces were being removed and replaced via "+" symbol in step 21 of CorrCreate activity. To resolve this, a new Boolean parameter skipPropertyEvaluation has been added in the CorrCreate activity to handle the decision to either evaluate the logic or not, and the pre-requisite will be to resolve all the property references before calling this activity so custom CSS braces { } will be honored when the message body is sent.
INC-132088 · Issue 603084
Updated Tracer for cluster events
Resolved in Pega Version 8.5.2
When running the tracer from the Admin Studio Listener management landing page, Tracer was always fetching data from one node only even though events were generated on another node. This was due to the specific node where the Listener was running being passed to the concern activity while launching the tracer; the Tracer Client node did not have data to check if the event was being populated on another node, and the result was to always fetch data from one node only even though events were generated on another node. To resolve this, the web node ID where the event is running will be passed.
INC-149728 · Issue 608105
Application wizard security updated
Resolved in Pega Version 8.5.2
A user having PegaRULES:User1 role only was able to run the Create Application wizard until an authorization block was reached, yet some rules were created. No operator records were created as part of this process. This was traced to code left in place after the creation of pxAppConfig and pzAppConfig portals, and has been resolved. The New Application wizard UI will display a message to a user when they lack access to build a new application, and an error will be displayed for any attempt to create a new application directly via pzCreateNewApplication to address a scenario where a user might be trying to call the activity without the front end.
SR-D5904 · Issue 488562
Discard changes dialog now showing for local actions
Resolved in Pega Version 8.3.1
After having modified case data without saving and clicking on a menu entry (left menu, search, ...), the system shows a dialog box to ask the user to confirm it is ok to discard changes. However, this confirmation dialog did not work with local actions, leading users to lose their work without any warning nor any way to step back. This was traced to a difference in the dirty form check, which was not present when launching a local action from a case. An enhancement has now been added to the handleMenuAction js function in pypega_ui_harnessactions.js which will perform a dirty form check with a prompt.
SR-D16934 · Issue 493702
External Cassandra nodes listed in DDS cluster
Resolved in Pega Version 8.3.1
Nodes of an external Cassandra cluster were not listed in the DDS cluster except for the first one in the host list, and when the “only” listed Cassandra node was restarted, the status on the DDS cluster LP did not become “NORMAL” afterwards. In addition, even though other C* nodes were up and running, the external Cassandra cluster was reported as unreachable. This was an unintended side effect of work done on the landing page to reflect the real state of the nodes after some were killed and restarted, and has been corrected by refining the equals() and hashCode() methods for DDS member info in order to better differentiate the external Cassandra nodes.