SR-D71522 · Issue 539322
Radio button error resolved for scenario testing
Resolved in Pega Version 8.1.8
When creating a scenario test case that selected a radio button and navigated the screen, it worked to complete a case and save the scenario test case in a rule set. However, attempting to then run the scenario test case stopped with the error message "Value cannot be blank" for the radio button even though the value "No" was captured for the button. This was traced to the firing of the change event, and the system has been updated so 'pega.u.d.setProperty' will only fire a click event on a selected radio button option.
INC-174652 · Issue 654140
Case Archive updated to better prune email and attachment metadata
Resolved in Pega Version 8.7
After configuring pyPegaArchiver, pyPegaIndexer and pyPegaPurger to remove old cases, there were no records present in the pr_metadata table but the records related to Data-Corr-Email, Data-WorkAttach-File and Link-Attachment remained. As there is no harm in removing these entries because the system has already copied the reference to these attachments, the entry in pr_metadata can be removed without any issue. With this update, external and shared entries now get removed from pr_metadata table when a purge is performed, however they do not get removed from the target table.
SR-B37115 · Issue 293959
PegaUnits bulk testing updated
Resolved in Pega Version 7.3
AUT test cases were failing while running in bulk, though running a single unit worked as expected. This was found to be a conflict with the way a test case uses a current parameter page from the start of execution to end of execution and then passes it to the next test; if there are two data page test cases where one is configured to have a non-blank value for a given parameter while the second one has a blank value for same parameter, the second test unexpectedly encounters the non-blank value. To resolve this, the code has been modified to reset the value of only RUT params before set up is called, so that every test case behaves truly independently.
SR-B37115 · Issue 286705
PegaUnits bulk testing updated
Resolved in Pega Version 7.3
AUT test cases were failing while running in bulk, though running a single unit worked as expected. This was found to be a conflict with the way a test case uses a current parameter page from the start of execution to end of execution and then passes it to the next test; if there are two data page test cases where one is configured to have a non-blank value for a given parameter while the second one has a blank value for same parameter, the second test unexpectedly encounters the non-blank value. To resolve this, the code has been modified to reset the value of only RUT params before set up is called, so that every test case behaves truly independently.
SR-C95840 · Issue 434789
Independent query logic inserted for non-resolved rules to avoid non-applicable columns
Resolved in Pega Version 8.3
Nothing was displayed under "Revalidate and save" for Rule-Ruleset-Name and Rule-Ruleset-Version. In Tracer there was an error message saying that "There was a problem getting a list: code: 207 SQLState: S0001 Message: Invalid column name 'pyRuleAvailable'. " Investigation showed that because the system was using the same logic for resolved and non-resolved rules, Rule-Ruleset-Name and Rule-Ruleset-Version were looking for the column pyRuleAvailable which was not applicable because non-resolved rules don't have this column. To resolve this issue, a separate query executor has been added for non-resolved rules as there are a few columns related to resolved rules that are not applicable for those that are not resolved.
SR-C96001 · Issue 436367
Independent query logic inserted for non-resolved rules to avoid non-applicable columns
Resolved in Pega Version 8.3
Nothing was displayed under "Revalidate and save" for Rule-Ruleset-Name and Rule-Ruleset-Version. In Tracer there was an error message saying that "There was a problem getting a list: code: 207 SQLState: S0001 Message: Invalid column name 'pyRuleAvailable'. " Investigation showed that because the system was using the same logic for resolved and non-resolved rules, Rule-Ruleset-Name and Rule-Ruleset-Version were looking for the column pyRuleAvailable which was not applicable because non-resolved rules don't have this column. To resolve this issue, a separate query executor has been added for non-resolved rules as there are a few columns related to resolved rules that are not applicable for those that are not resolved.
SR-D4027 · Issue 439897
Explicit property evaluation added to correct visibility in Proposition Management sorting
Resolved in Pega Version 8.3
After navigating to the Decisioning: Proposition Management landing page (Configure->Decisioning->Decisions-> Proposition management -> Hierarchy), opening any Decision data and then switching to the Form tab to perform any sorting on the Form fields grid caused the UI to become unresponsive and generate the error "Uncaught SyntaxError: Unexpected end of input at pega.ui.Doc.evaluateVisibleWhens". This issue was traced to a 'when' condition which demanded explicit mention of whether the property value had been evaluated as true or false, and that result has now been added.
INC-173436 · Issue 648819
Performance improvement for Application Save: Node Level Data Pages
Resolved in Pega Version 8.6.1
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-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.