SR-C24537 · Issue 367642
Guardrail updated to redirect 'When filter' to 'listview filter' in product rules
Resolved in Pega Version 8.1
The 'When' rule is deprecated on product rules and can cause issues if used. To clarify this and create more helpful guardrail messages, the following warning message has been added to situation where the 'when filter' is used in the Class instances to include section:"Using when rule filter is deprecated. Instead use list view filter."
INC-197530 · Issue 686027
Value Finder updated for use with external Cassandra nodes
Resolved in Pega Version 8.7
Attempting to use the Value Finder feature resulted in the error "Running Simulation is not possible because the required services are not available. Contact your System Administrator to enable the data flow and decisioning data store services." Analysis traced this to a check which identifies whether there is more than one internal node available for CDH/ DSS node. Since there were only external nodes available in this scenario and no internal nodes, the method returned false and returned the error when the CDH / VF page was launched. To resolve this, the check has been modified to allow for external Cassandra.
INC-168254 · Issue 659297
Documentation updated for accents and special characters used in search
Resolved in Pega Version 8.7
The "Pega search API" article has been updated to reflect that the search functionality in Pega Platform does not match accented words with unaccented. For example, searching for santé and sante will retrieve different results. In addition, Domain Specific Language (DSL) includes special characters for use when searching, for example '-', '_', '!', '@'. However, the system retrieves various results depending on the way the special characters are used in the search query. If the query contains special characters that are not escaped, the system may retrieve incorrect results. For example, not escaping the slash mark in the 25/02 query may cause the system to ignore the special character.
SR-C22471 · Issue 370124
Handling added for long names when exporting DataType columns
Resolved in Pega Version 8.1
Values were not being displayed in an exported file for a column with a name exceeding 30 characters. This was traced to the values being mapped to a hashed value that truncated the name and caused the alias to not be found when expanding the data, and has been fixed.
SR-C5169 · Issue 349818
Tabs maintain state when new RDL item added
Resolved in Pega Version 8.1
Adding a new item to a repeating Dynamic layout switched all the currently selected tabs in an embedded Tab Layout Group to be the same as the last item. This was an issue with complex configuration RDL having another repeating layout (DLG) with an active 'when' based on repeating context property, and code has been added to handle the previous selected tab state and active when so tabs will retain integrity.
INC-164947 · Issue 639862
Handling added for missing div when opening work object
Resolved in Pega Version 8.7
In mobile offline app, opening a work object in a specific scenario for the second time resulted in an endless busy indicator. It was not possible to navigate away, and the app had to be closed and reopened to continue. Investigation showed that some app sections had an action that tried to load a harness section where one specific div was missing, and this has been resolved by updating reloadSectionOSCOHandler to handle the missing div in the failure callback. Additionally a console.error() will appear for the missing section.
INC-130011 · Issue 571833
Resolved stale reference error when swapping stages with drag and drop
Resolved in Pega Version 8.1.9
If user swapped stages (2nd stage to 1st stage) using drag and drop and then added a participant or role in the stage, a Pega blue screen appeared. This was traced to using a grid with reorder and an inner grid in the cell. On drag and drop, the grid reference object was stale and not in sync with the latest table. To resolve this, code has been added to reinitialize the inner grid on drag and drop.
SR-C3988 · Issue 358537
Launched portal remains open when navigating back to originating portal
Resolved in Pega Version 8.1
After logging into the 'Developer Portal' and then using the 'Launch' menu option to open the 'Manager' portal in a new tab, navigating to 'Manager' and changing the access role correctly caused the current tab to show the respective portal. However, after navigating back to the developer portal shown in first tab, the manager portal then closed and the developer portal was refreshed. This was a missed use case in the handling, and changes have been made in ApplicationSetup and RedirectAndRun activities to correct the issue.
INC-174625 · Issue 655242
Admin Studio will consider cluster protocol when returning listener status
Resolved in Pega Version 8.7
When using a few nodes in standalone mode for BIX extract combined with server nodes using Hazelcast, opening the admin studio pages with service discovery caused an error to be thrown. This was traced to the system writing an entry to pr_sys_statusnodes table as an embedded node whenever a BIX extract was triggered, causing those standalone nodes to be incorrectly considered by the listener landing page. This has been resolved by configuring the system to either return the local member when the cluster protocol is standalone or to return all Hazelcast members if the cluster protocol is Hazelcast.
SR-B78077 · Issue 364120
Documentation updated to assist in fixing UnresolvedAssemblyErrors when resolving RUF rules
Resolved in Pega Version 8.1
To address UnresolvedAssemblyErrors resolving RUF rules, the following help topics have been updated: Selecting-import-file-tsk Importing-cli-tsk Importing-cli-web-tsk To include the following cautions: * Review the archive contents to better understand which rule sets are capped and to determine the relatives risks and benefits of running uncapped rule sets. * Do not import an archive into an active runtime instance of Pega Platform because the archive can overwrite rules in use.