SR-131612 · Issue 200253
Handling added for accent characters in DataTable editing
Resolved in Pega Version 7.1.8
When a DataTable had a key value with an accented character like "é", clicking on the "Open this item" icon to edit the row displayed a blank page in the editor. This was caused by the escape method of native JavaScript being deprecated, and the system has been updated to use encodeURIComponent method instead.
SR-128332 · Issue 199072
Added detection for WSDL import failure
Resolved in Pega Version 7.1.8
Issues were encountered while importing WSDL in the ML6 environment while SoapUI was successful using the same SOAP service. This error happened when the WSDLParser.parse(Reader) was trying to read a closed java.io.Reader instance and silently generating an exception. Error handling has been added to report the failure and give an informative message.
SR-118615 · Issue 172704
Addressed XML handling for "Expand Java Pages"
Resolved in Pega Version 7.1.8
After upgrading, an IOException occurred while updating a work object if "Expand Java Pages" was unchecked in General options -> Tracer Settings. When the checkbox is enabled, the Javaobject wrapper uses its custom read/write methods to serialize the page. When unchecked, default serialization invoked the ParseXMLSAXRulWrapper.java which contained some properties which are not Serializable. In order to ensure proper XML handling, changes were made to XMLStream.java so the code flow is independent of the expand java pages option in tracer and always takes the custom serialization path.
INC-147654 · Issue 642189
Updates to displaying embedded images in cases
Resolved in Pega Version 8.7
Sending an email with an embedded image to the email ID associated with the email listener successfully created the interaction case, but the embedded image was not displayed when the case was opened from the work-basket. A rule-not found exception was seen in the tracer for pyGetImageDisplay, the rule responsible for displaying the images in the ET pane. Investigation showed that when URLObfuscation was turned on, the decryption of the URL was not successful because "&" had been encoded to '& amp;'. This has been resolved by calling the activity pyGetImageForDisplay using URLMapping instead. An additional issue was seen with displaying images in the email interaction pane where the additional empty new lines moved the image outside the intended place. This was traced to a customization for the reply area which used the pyHighlightedMessage property and converted newlines to br tags even in HTML mode. To resolve this, pyHighlightedMessage has ben modified to convert newlines to br tags only if the mode is plain text.
INC-175595 · Issue 652831
Java Bean import updated to handling differences in Java 7 and Java 8
Resolved in Pega Version 8.7
The behavior of the java bean Introspector class is inconsistent across different versions of the JDK when detecting indexed properties built off of java.util.List objects, causing Java Bean import to generate differently in Java 7 and Java 8. This has been resolved by updating PRIndexedPropertyDescriptor to better handle this JDK difference by resolving indexed read and write methods manually using simple reflection.
SR-129387 · Issue 200153
Logic updated to correctly tally requests that bypass authentication
Resolved in Pega Version 7.1.8
The logic used by the usage summary report to capture service invocation was not updated when the code was changed to bypass authentication for some service requests: if authentication was disabled, the request was treated as authenticated and was not correctly reported in the service invocation total of the SOAP usage summary report. To correct this and report accurate transactions, the system now resets the authentication flag for stateless unauthenticated requestors at the end of service invocation so that usage tracking is correctly recorded.
INC-174716 · Issue 656441
Updated handling for validating/saving circumstanced rule on branch
Resolved in Pega Version 8.7
Using 'save as' for an already circumstanced rule with a new property/template caused the Rule-.DictionaryValidation activity to register the error "StandardValidate-CircumPropAlreadyDefined". The same activity Step did not throw an error when saving into Branch. This was traced to the ruleset name not being the same for the branch ruleset due to having _BRANCH_Branch-Name appended to its name, and has been resolved by adding a condition to check for circumstanced rule in a branch.
INC-166844 · Issue 651407
Email bot updated to handle negative and positive feedback on the same text
Resolved in Pega Version 8.7
When positive and negative training was done on the same piece of text, text extraction by Email Bot failed. For example, when using the sentence. “John Smith plays cricket”, the bot detects “John” as person name. If user wants to train the bot to detect “John Smith” as the entity, the user needs to first remove “John” and build the model, and then select “John Smith” and build the model again. In this case, the email bot never again detects “John Smith” as person name due to the negative feedback given for “John”. This was traced to the entities having same the startIndex/endIndex, and has been resolved by removing entities of the same modelName which have the pyIsRemoved property as true so that multiple entity models are detected on the same word.
SR-120730 · Issue 178759
Fixed FCM access for remote work item attachments
Resolved in Pega Version 7.1.8
When using FCM to access remote work item via find by ID, attempting to open the history / attachments popup generated a green tick (success but no content) on the first attempt and the error "Failed to find a 'RULE-OBJ-ACTIVITY' with the name 'HISTORYANDATTACHMENTS' that applies to '@baseclass'" on subsequent attempts. "the operation completed successfully, but returned no content". The issue only happened when first logging on and searching for a work item and did not occur if the tab was closed and the same work item reopened. This was caused by the prgateway sending an HTTP request where the Pega thread name in the URL was stripped of a slash, triggering the creation of a brand new Pega thread where expected pages were missing. To resolve this, the code has been updated to correctly maintain slashes and add them if necessary.
SR-132123 · Issue 202411
Auto-resize parameters added to Pega Image Viewer
Resolved in Pega Version 7.1.8
When a large TIFF image (over 2,000 x2,000 pixels in size) was loaded into the Pega Image Viewer control embedded into any section, both horizontal and vertical scroll bars appeared and the Fit-To-Width button of the control needed to be clicked to scale down the image enough to eliminate the scroll bars. In order to smooth image display, the system now provides image size initialization during startup using a parameter 'ImageSize' in the HTML which accepts three strings: Normal, BestFit, or FitWidth.