INC-230576 · Issue 741541
Data transform works with encryption in Pega Mashup
Resolved in Pega Version 8.8
Data transform was not getting called in case of Mashup when "Use Encryption" was ON. This was traced to the data transform not being triggered correctly in this scenario, and has been resolved.
INC-191159 · Issue 682362
Validate topics based on all topics in channel instead of default language
Resolved in Pega Version 8.7
if a 'When Rule' was used in Email Receiver to provide some conditions, it was not possible to use topics from the dropdown which were trained with training data in prediction studio. This was a missed use case, and was traced to validation being based on the default language topics. To resolve this, the data page has been modified from getting default language topics to getting a union of topics. The datapage for default language topics has also been withdrawn.
INC-152084 · Issue 620951
Handling added for cross-origin DOM exceptions
Resolved in Pega Version 8.4.4
When an openURLWindow action was used to open any other domain, DOM exceptions were generated related to cross-origin iFrames communication and the UI became unresponsive. This has been resolved.
INC-230911 · Issue 740100
Apply filter option handles passed data page reference
Resolved in Pega Version 8.8
The GetGridColUniqueValues activity was failing on step 3 when the data page reference was passed as a parameter of source report definition in a grid. This was traced to missing filter parameters for this use case and has been resolved.
INC-224317 · Issue 723105
Corrected embedded page list render error
Resolved in Pega Version 8.8
Using a page list within a page list was rendering with overlapping field forms. This has been resolved by removing the negative margin from field group legends when presented in a list.
INC-196447 · Issue 684644
Enhancements added for external Kafka Stream Service
Resolved in Pega Version 8.7
To ensure data privacy when using multi-tenant Stream Service hosted on a single Kafka cluster, access will be authorized based on ACLs when a tenant sends direct requests to Kafka. In addition, all Kafka resources (topics and consumer groups) are now able to contain a prefix naming convention which can be used for tenants. This is handled through using a <env name="services/stream/name/pattern" value="{tenant.name}-{environment}-{stream.name}"/> prconfig setting to set the stream name pattern. For example, if the tenant.name is resolved into "companyname", environment into "prod1", and the stream dataset name is pyFTSIncrementalIndexer, then the Topic name created on the external Kafka will be companyname-prod1-pyFTSIncrementalIndexer.
SR-D70310 · Issue 537141
Window type check added for icon display logic
Resolved in Pega Version 8.4.1
When a Role had privileges to use Live UI, Agile WorkBench and Scenario Testing, the Scenario Testing tool icon intermittently did not show. This was traced to an incorrect condition used to check whether current window was of type desktop (portal) window, and has been resolved by adding a check that will also ensure consistency with Agile Studio icon display logic.
INC-169186 · Issue 655537
Disconnect button availability extended
Resolved in Pega Version 8.7
A case was not refreshing when the disconnect button was selected while using the standard section for authorization grant type authentication. This was traced to a query executed to find a div with attribute pzInsHandle, but that attribute was not applicable in the user portal. To support this use, the query has been extended to be applicable for user portal (attribute data-ui-meta) and Dev Studio landing page.
INC-219656 · Issue 717375
Null check added for Application/AccessGroup system pages
Resolved in Pega Version 8.8
In some scenarios the Application/AccessGroup system pages used by the Choose Best RuleSet API to group/cache the user's ruleset could be null, resulting in a null pointer exception when using the pxCreateRecord Activity for the data instance creation. A null check has been added to avoid the exception, and a complete resolution for the null pages will be available in a future release.
INC-144387 · Issue 605342
Support added for allow list for LaxRedirectStrategy
Resolved in Pega Version 8.4.4
When using Connect REST with POST to access a third-party service deployed on multiple nodes, the load balancer sometimes replied 302 with Location header. The ability to allow the REST connector to automatically follow these redirects even in the case of POST messages is supported by Apache http client via LaxRedirectStrategy, but REST Connectors need both rule and engine enhancements to allow for this. To support this use, an allow list has been implemted for hostnames. This will allow the connector to be configured to follow the LaxRedirectStrategy only when the hostname of the redirect location is in the allow list. The default will continue to block the redirect.