SR-122387 · Issue 183319
Expanded BIX error codes
Resolved in Pega Version 7.1.8
When BIX is executed through the command line, it may not return an error code even if BIX has stopped processing because of a failure (for instance when the -f flag has been used). That is, the $? system call may return 0 when an extract has failed. The system has been updated to offer more information thorough error code returns, but when trying to programmatically capture whether a particular run of BIX was successful or not, it would still be advisable to check $? in the script, as this may be returned due to other reasons (such as a java/network/database related problem). This may be augmented by performing a parse on the PEGABIX log file and specifically checking for the text: 'Instances not extracted due to errors: 0'. At the end of each BIX this line will appear with a summary of how many extracts failed. After the BIX portion of the script has completed, it's possible to check how many occurrences of this error appear in the file. If it is one, then this meant none of the extracts produced errors. And if there are none, then either some exports did contain errors, or it didn't reach the part of the code that produces this line (hence an earlier error). This can be incorporated into a script using something like: errorfree='grep "Instances not extracted due to errors: 0" PEGABIX.log | wc -l'
SR-122440 · Issue 183753
Corrected text wrap for cases
Resolved in Pega Version 7.1.8
Text wrapping was not happening automatically in long history descriptions in a case. This was due to a missing function and has been corrected.
SR-122493 · Issue 190767
Support added for conditional page list properties
Resolved in Pega Version 7.1.8
After upgrading, validate rules on aggregate properties had unexpected behaviors. This rule formation was inadvertently allowed in some earlier versions despite guardrails, so support for these conditional page list properties has been added in order to enhance backwards compatibility.
SR-122504 · Issue 189293
Made operator identification consistent across flows
Resolved in Pega Version 7.1.8
A naming difference was seen in work flows depending on whether Visio or modular functions were used: Visio picks the "Task_Assignment2" function to generate java for assignment, giving the operator ID, but modular flows use "Task_Assignment" and show the operator name. In order to show consistent behavior, the code has been modified such that it first gets the operator name from the assign page if it exists, and it does not exist it will fall back to sending the operator ID as parameter.
SR-122559 · Issue 181629
Removed pagination from GetBinaryFiles RD to ensure all records are reported
Resolved in Pega Version 7.1.8
When attaching content smart shapes in Standard flow, not all results were shown if pagination was enabled. This was caused by the pagination limiting the returned information to 50 records, and manifested as Binary File path autocomplete not showing all the results, the open rule icon not working even if the binary file rule existed, FileKey only being generated if the file was selected from the autocomplete list, and an Invalid file attachment error if an existing binary file was accessed. In order to resolve this work flow issue, pagination has been disabled in the GetBinaryFiles report definition.
SR-122559 · Issue 179977
Removed pagination from GetBinaryFiles RD to ensure all records are reported
Resolved in Pega Version 7.1.8
When attaching content smart shapes in Standard flow, not all results were shown if pagination was enabled. This was caused by the pagination limiting the returned information to 50 records, and manifested as Binary File path autocomplete not showing all the results, the open rule icon not working even if the binary file rule existed, FileKey only being generated if the file was selected from the autocomplete list, and an Invalid file attachment error if an existing binary file was accessed. In order to resolve this work flow issue, pagination has been disabled in the GetBinaryFiles report definition.
SR-122637 · Issue 183016
MaxFileLength property added to avoid truncating attachment names
Resolved in Pega Version 7.1.8
While adding the attachments to the case using drag and drop functionality, the file name and file description were being truncated. However, a new property named "pyMaxFileLength" is now available as an override in pyDefault Model to set a different name limit. If this property is not set, it will take the default value of 60 and proceed. Also for UI error messages, pyNote property in Data-WorkAttach-File and Embed-DragDropFile in the application ruleset must have the max length limitation removed from there or the MaxFileLength will be overridden by that setting.
SR-122732 · Issue 182663
Cleaned up error logging for Oracle split schema multi-tenant upgrade
Resolved in Pega Version 7.1.8
When upgrading a multi-tenant environment with an Oracle split schema database, the log file was filling with warning messages on all tenant IDs during Rules upgrade. While errors are expected if there are tenants in the database that are no longer valid, the failure to resolve the tenant ID was being reported twice. In order to smooth the upgrade process, the log messages in this environment have been changed from warnForced to info, and each error will only be logged once.
SR-122738 · Issue 184536
Resolved extraneous error from Case Viewer imports
Resolved in Pega Version 7.1.8
Attempting to import specifications from Excel in Case Viewer to update specifications that were checked in was showing the error 'Update Fail'. The updated specification was successfully imported, but the new change is checked out to the user. This was an error generated by the final step of the Import Specification wizard and has been resolved.
SR-122757 · Issue 185151
Chinese filename issue with Microsoft Internet Explorer resolved
Resolved in Pega Version 7.1.8
When using the Chinese version of the Microsoft Internet Explorer browser and the out-of-the-box attachment gadget to attach files, dragging and dropping a file with Chinese characters in the file name caused the name to become corrupted. This issue was due to the encoding method, and has been resolved by removed the encoding for the filename.