SR-A7518 · Issue 219402
EJB Connector wizard fetches fully qualified class names for compile
Resolved in Pega Version 7.2
When using a JNDI Server referencing remote EJBs, configuring Connect EJB through the wizard resulted in compilation errors. This was due to incorrect wrapper class generation, and the generation has been updated to use fully qualified class names.
INC-172521 · Issue 651553
Email template content visible in user application
Resolved in Pega Version 8.7
An issue was seen with email templates functionality where the body content given during the email template creation was not visible when the template was used in the application by an end user. This was a missed use case for recent security updates, and has been resolved.
SR-A8506 · Issue 217725
Data types pagination limit removed from Application Wizard
Resolved in Pega Version 7.2
When building a new FW application using the Application Wizard, the wizard only displayed the first 50 data types when there were more available. This was due to the source report definition used to obtain the list of Data types having a page limit of 50, and has been resolved by disabling pagination and setting "Maximum number of rows to retrieve" to "0" so all available data types will be retrieved at once.
INC-178116 · Issue 660565
Article on configuring display options for a harness updated
Resolved in Pega Version 8.7
The documentation around the load behavior of a harness has been updated to reflect that the initialization settings only apply when using the harness as a landing page from the channel config. Applications that use Cosmos React do not use harnesses for landing pages. You can modify Cosmos React landing pages only in App Studio.
INC-176158 · Issue 664348
Max number of rows setting properly honored
Resolved in Pega Version 8.7
The setting for the maximum number of rows to retrieve was still used in a report definition even when it was disabled. This was traced to the report definition being sourced from a data page and having pagination enabled, and has been resolved by updating the handling for this use case.
SR-D32972 · Issue 513488
HTML entity handling added to URLObfuscation
Resolved in Pega Version 8.2.5
When URLObfuscation was enabled through the configuration settings, clicking on Operator -> Profile page generated an ArrayIndexOutOfBoundException. When obfuscation is used the decrypted string is parsed and the request map is populated, but HTML entities were not considered during this process. To resolve this, handling has been added for HTML entities and characters during obfuscation. Please note: URL Obfuscation is a legacy feature with many known limitations and it is no longer recommended that these settings be used.
INC-170514 · Issue 653762
Lock conflict resolved for AssignmentCheck
Resolved in Pega Version 8.7
The error "Unable to unlock this work object" sporadically appeared in both the runtime log and Pega RULES log when the robot was trying to create a case in Pega using an API call. Investigation showed that as the case was created, it was pulled by another robot (another requestor) which was using the GetAssignments API. This caused the perform assignment check to fail. To resolve this, a 'when' rule has been added to the performAssignmentCheck Activity.
SR-A11696 · Issue 224612
Namespaces considered while constructing WSDL type maps
Resolved in Pega Version 7.2
Previous versions that had repeating complex elements used as references ended up with "type2" appended to those elements when the WSDL was generated after upgrade. This format was put in place to avoid namespace collisions when duplicate names are used for the same complex types in a schema with different targetnamespace. However, even though the WSDL was semantically correct, it caused backward compatibility when generating stubs out of WSDL and created the need to regenerate the stubs. To resolve this, changes have been made to XMLTreeViewUtils.addDocElementDeclaration() to consider namespaces while constructing the type definition map.
INC-146429 · Issue 602292
Disabled control status made accessible to JAWS
Resolved in Pega Version 8.4.4
When using the Security Event Configuration page (tab) within Pega Dev Studio, the link elements used for 'Select All', 'Clear', 'ON' and 'OFF' were not providing the current State of the element to JAWS. In template rendering of Link control with a 'disable when' condition (server-side evaluation), when the control is disabled it was still accessible and screen readers were not reading the link as disabled. This has been resolved by adding tabindex="-1" and aria-disabled="true" for disabled Link control.
INC-193561 · Issue 680427
Client secret made optional for JWT Bearer Grant type
Resolved in Pega Version 8.7
After update, trying to connect a REST API using OpenAM as the provider for OAuth and using JWT Bearer as Grant type was resulting in an error indicating the request was not reaching the destination. This was traced to the client secret being designated a mandatory field when it should be optional in this case as the required key store was already configured with a JWT token profile. To resolve this, an update has been made which will make the client secret optional when the authentication scheme is JWT Bearer. In addition, the blank value caused a null pointer error when the client secret was not passed. This has been handled with a check.