SR-D15895 · Issue 486592
Strict checking inserted to better handle DB keywords in string constant
Resolved in Pega Version 8.2.3
After upgrade, a report was failing with the message "Rule Alias Function cannot reference a SQL function that performs a subquery." This was traced to the report having a function alias used in the columns which compared two strings and returned another string (constant - static value) if the condition was met. However, in two of the returned string constants there was the word "select", which is a keyword in all database languages. Even though the word "select" was a referred part of a string constant, the system treated it as a keyword and tried to perform a subquery within the Function Alias because ABAC was enabled. The report only exhibited this behavior post-upgrade because while ABAC defaulted to disabled in previous versions, it was changed to default to being enabled beginning with v8.1. To resolve this and create more robust backwards compatibility, a more strict check for subquery validation will be performed when ABAC is enabled which will parse and check whether the RAF has the standard 'select from' clause syntax of SQL.
SR-D47414 · Issue 513077
"Use null if empty" checkbox honored for GetSelectValues
Resolved in Pega Version 8.2.5
When Report Definition rule uses parameters as a value for filter criteria, a moderate performance warning was generated: ''Some of your filters are using a parameter with the "Use null if empty" option NOT selected. Please ensure that you do pass the parameter. Otherwise, the filter will be dropped entirely and execution of the report will result in very poor performance. If you do not want this behavior, select the "Use null if empty" option.'' When the "Use null if empty" checkbox was selected as suggested, the "Select values" button gave an empty list of possible values. This was traced to refactoring work done on Select Values which changed it to be backed by a Report Definition and Grid instead of a List View: the option was intended to be only temporarily disabled, but was missed. To correct this, the activity pzGetSelectValues has been updated to honor the checkbox and appropriately disable the "Use null if empty" option on the selected filter on the temporary copy of the report definition before it is executed.
SR-D47414 · Issue 513076
"Use null if empty" checkbox honored for GetSelectValues
Resolved in Pega Version 8.3.1
When Report Definition rule uses parameters as a value for filter criteria, a moderate performance warning was generated: ''Some of your filters are using a parameter with the "Use null if empty" option NOT selected. Please ensure that you do pass the parameter. Otherwise, the filter will be dropped entirely and execution of the report will result in very poor performance. If you do not want this behavior, select the "Use null if empty" option.'' When the "Use null if empty" checkbox was selected as suggested, the "Select values" button gave an empty list of possible values. This was traced to refactoring work done on Select Values which changed it to be backed by a Report Definition and Grid instead of a List View: the option was intended to be only temporarily disabled, but was missed. To correct this, the activity pzGetSelectValues has been updated to honor the checkbox and appropriately disable the "Use null if empty" option on the selected filter on the temporary copy of the report definition before it is executed.
INC-218001 · Issue 719922
Error text revised for parameterized data page used for token generation
Resolved in Pega Version 8.6.5
While trying to add a claim in the header of a Token Generation Profile instance, selecting Map From as "Clipboard" and trying to give any DataPage(parameterized) as the source property failed to be saved and the error "JWS Alias— Please provide correct algorithm key with correct key length." appeared. Changing the "Map From" to a Constant and giving a dummy value worked as expected. Tracer showed the error "declare page parameters not supported by PropertyReference", indicating the actual issue: at this time, the Token profile does not support using a parameterized data page. This has been addressed by ensuring an appropriate error message is shown on save of the token profile rule form when a parameterized data page reference is configured. The error will now read "The reference D_pzPreferenceStore[PreferenceOperatorID:"[email protected]"].pxObjClass is not valid. Reason: Parameterized data page reference is not supported." Support for a parameterized data page used with Map From will be taken as an enhancement for a future release.
INC-218001 · Issue 719920
Error text revised for parameterized data page used for token generation
Resolved in Pega Version 8.8
While trying to add a claim in the header of a Token Generation Profile instance, selecting Map From as "Clipboard" and trying to give any DataPage(parameterized) as the source property failed to be saved and the error "JWS Alias— Please provide correct algorithm key with correct key length." appeared. Changing the "Map From" to a Constant and giving a dummy value worked as expected. Tracer showed the error "declare page parameters not supported by PropertyReference", indicating the actual issue: at this time, the Token profile does not support using a parameterized data page. This has been addressed by ensuring an appropriate error message is shown on save of the token profile rule form when a parameterized data page reference is configured. The error will now read "The reference D_pzPreferenceStore[PreferenceOperatorID:"[email protected]"].pxObjClass is not valid. Reason: Parameterized data page reference is not supported." Support for a parameterized data page used with Map From will be taken as an enhancement for a future release.
SR-C30808 · Issue 371553
REST Integration Wizard logic modified to resolve Null Pointer Exception
Resolved in Pega Version 8.1
When the sample request / response data for the REST Data Source Wizard contained a parameter that started with at least one character that was not valid for a Property name and the next two characters after the illegal character removal were "px" or "pz", then the system attempted to make a new Property record with a name that starts with one of the "reserved prefixes" (px, pz). That attempt was blocked. The illegal name was then also patterned over into rules related to the Property, causing them to be invalid due to their relationship with a nonexistent Property record. The Wizard was then forced to stop generating records and roll back the changes. To correct this issue, the "Property name cleaning" logic has been replaced with new logic that can handle the "illegal characters followed by px or pz" use-case.When RuleGeneratorCommon is creating a new MappingPropertyInfo, it will call the new 2-argument flavor of RuleGeneratorUtils.normalizePropertyName(...). This new normalization method performs the property-specific cleaning (removing prefixes) as the last step. RuleGeneratorCommon is also used to attempt to remove prefixes before all other formatting is performed.
SR-C50899 · Issue 397991
Improvements to Services Tracer
Resolved in Pega Version 8.2
When clicking on tracer to get details of a page, a pop-up window opened up with a highlighted link (in blue color) to open the parameter page or the primary page, but clicking on either of these page names opened a blank window without any properties mapping. This was due to the underlying object missing required data because the Services related tracer events did not always have PRThread objects associated with them. The Tracer infrastructure expected the proper PRThread to be in the "ThreadContainer" but offered no option for providing the thread, and the ThreadContainer was not always populated when Services ran. To resolve this, the Tracer Event infrastructure has been refactored to allow specifying a PRThread in RULE-HTML-FRAGMENT TRACERTRACEEVENTSSCRIPTS. The constructor logic in TraceEventBaseImpl has also been modified so child classes can pass a thread instead of relying on ThreadContainer. The Node ID for tracer events will be set based on PREngineProvider instead of ThreadContainer, and the ServiceEvent Interface's methods have been updated to take pointers to PRThreads so that the tracer knows who/what is being traced. In addition, NPE protection has been added to RemoteTracerStub so Tracing Services will not crash the Tracer UI when running from eclipse / prwebpacked.
INC-126640 · Issue 572264
Updated LDAP operator authentication handling
Resolved in Pega Version 8.4.2
After setting up LDAP authentication in an environment using Robotics which runs on Kerberos and configuring LDAP AD integration with a sAMAccountName [specific to Microsoft AD] attribute for the login, two operators were being created for a single user. Investigation showed this was caused by the operator's pyUserIdentifier being mapped in the LDAP service mapping attribute while the operator ID was using a different attribute (userPrincipalName) which was mapped to .pyUserIdentifier because the Kerberos authentication was done via userPrincipalName. For the first login, an operator was created as per the Search filter field. The next time the user logged in with the same ID, another operator was created using the userPrincipalName as per the mapping defined under the mapping tab. This has been resolved by updating LDAP handling. As part of the resolution, a precedence rule has been introduced which will give the highest precedence to a mapped pyUserIDentifier, then logged in operator name. If pyUserIdentifier is not mapped in authservice, the operator name will be the LDAP login operator name. If pyUserIdentifier is mapped in authservice, the operator name will be the LDAP attribute value which is mapped to pyUserIdentifier. If the mapped ldap attribute name is empty, login will fail. In addition, debugging logs have been added to aid in troubleshooting LDAP issues.
SR-C72225 · Issue 409998
Improvements to Services Tracer
Resolved in Pega Version 8.1.2
When clicking on tracer to get details of a page, a pop-up window opened up with a highlighted link (in blue color) to open the parameter page or the primary page, but clicking on either of these page names opened a blank window without any properties mapping. This was due to the underlying object missing required data because the Services related tracer events did not always have PRThread objects associated with them. The Tracer infrastructure expected the proper PRThread to be in the "ThreadContainer" but offered no option for providing the thread, and the ThreadContainer was not always populated when Services ran. To resolve this, the Tracer Event infrastructure has been refactored to allow specifying a PRThread in RULE-HTML-FRAGMENT TRACERTRACEEVENTSSCRIPTS. The constructor logic in TraceEventBaseImpl has also been modified so child classes can pass a thread instead of relying on ThreadContainer. The Node ID for tracer events will be set based on PREngineProvider instead of ThreadContainer, and the ServiceEvent Interface's methods have been updated to take pointers to PRThreads so that the tracer knows who/what is being traced. In addition, NPE protection has been added to RemoteTracerStub so Tracing Services will not crash the Tracer UI when running from eclipse / prwebpacked.
SR-A76847 · Issue 255143
Outbound Correspondence enhanced to handle Inline Content
Resolved in Pega Version 7.2.2
Pega's outbound email features previously only allowed for specifying "attachments" for inclusion for the email messages that are sent out from the Pega application and did not support "inline content". This led to all images in a Correspondence object being packaged as attachments when Pega sent Correspondence as email, and images might fail to appear in the body of outbound Correspondence when the recipient opens the message in their email client. Images intended to be part of the message body would appear as attachments to the email message. To enhance the mail services, a new PageList property "pyInlineContent" of type "Embed-EmailAttachment" has been added to the preexisting "Data-EmailAttachments" class. The "SendEmailMessage" Rule-Utility-Function has been enhanced to detect when the new "pyInlineContent" property is populated. If the email is HTML formatted, the content in the list will be given a disposition of "inline" and packaged with the HTML body in a message part of type "multipart/related" for proper consumption by email clients. If the email is not an HTML email, the "inline" content will NOT be branded as inline content, so that it appears as an attachment when the email message is opened. The "SendEmailNotification" in Pega-EventProcessing has been WITHDRAWN and replaced with a new version in SendEmailNotification which has an updated "prepare" step (#2) that puts the data for images in HTML (Corr) into the new "pyInlineContent" property of the Email Attachments page (if such a page exists), so that SendEmailMessage can process them correctly.