SR-C39747 · Issue 383893
Added call to pyconvertedvalue to preserve number format in BIX extract filtering
Resolved in Pega Version 8.1
When creating a BIX extract rule with a filter of integer property on LHS and a constant integer value of RHS which is of 8-9 digits such as "filter : salary = 100000000" , saving the extract rule converted this RHS value to 100,000,000 and the filter showed as : "salary = 100,000,000" .In this scenario, running the extract rule generated an error in the log. This was traced to the system converting the filter value ( <pyfiltervalue> whose value is "100,000,000" ) to a number and causing a numberformat exception. This was a coding error that missed a call to supply <pyconvertedvalue>, and has been fixed.
SR-C39791 · Issue 379314
Group processing and StartDate issues resolved for Timeline controls
Resolved in Pega Version 8.1
Two issues were seen in the Timeline control:Issue 1: When a technician was selected who had no events, the Technician was not shown in Y-Axis (Groups were not being displayed). A blank screen was shown instead. This was caused by the a condition where an empty datasource caused createDataset to return without processing groups. This has been corrected by adding handling so the system will initialize dsArray with an empty value if needed to ensure the group related processing takes place. Issue 2: The start range for Timeline was not respecting the StartDate given for the Events display. In this case, if either the start or end time was not available then neither was set. To resolve this, If an end date is not specified then it will be marked as the current date.
SR-C39796 · Issue 383047
Enhancement added to switch tab name localization when locale switches
Resolved in Pega Version 8.1
When launching a Harness in a tab onclick of a link/button from a section, passing tab name as a localized field value was not working properly when switching between different locales. This was caused by the Tab name not getting updated on click on Launch harness, and has been corrected with the addition of a new parameter "bLocalize" for pzActionAppendValue to invoke getLocalizedTextForString if the parameter is true. This value will be passed as true when called from pzActionShowHarness newDocument case.
SR-C39815 · Issue 381813
Font files updated to support Turkish characters in VBD
Resolved in Pega Version 8.1
It was possible to use Turkish special characters in the labels of Business Issue and Groups, but VBD did not show these Turkish characters as in the screenshot. To enable this, a new set of font files with larger character sets has been added which includes the Latin-1 Supplement and Latin Extended A blocks to which the Turkish characters belong.
SR-C39879 · Issue 384006
Automations work using property with JSON string
Resolved in Pega Version 8.1
When using JSON to send complex data structures to an automation via a property, a special character ( ' ) used in the JSON string caused an error when trying to execute the automation from a flow action: "Uncaught SyntaxError: Unexpected end of JSON input". Analysis showed that if any relevant record had a single quote, the generated HTML of java tried to break the html data-automation-propData attribute, resulting in an exception. To fix this, the code has been updated to replace the single quote with ASCII HTML entity which will make the data-automation-propData attribute friendly.
SR-C3988 · Issue 358537
Launched portal remains open when navigating back to originating portal
Resolved in Pega Version 8.1
After logging into the 'Developer Portal' and then using the 'Launch' menu option to open the 'Manager' portal in a new tab, navigating to 'Manager' and changing the access role correctly caused the current tab to show the respective portal. However, after navigating back to the developer portal shown in first tab, the manager portal then closed and the developer portal was refreshed. This was a missed use case in the handling, and changes have been made in ApplicationSetup and RedirectAndRun activities to correct the issue.
SR-C39998 · Issue 387496
Fixed incorrect report background color with Microsoft Internet Explorer 11
Resolved in Pega Version 8.1
The background color of a report was gray instead of white when scrolled horizontally while using Microsoft Internet Explorer 11. This is a known issue with Microsoft Internet Explorer 11 when a flex layout is used inside a table: the harness width in flexresize is checking for 3000 width, and when it is more than 3000 there is a resize issue. If work area-based screen layouts are used instead of containers this issue is not seen. In order to handle the Microsoft Internet Explorer 11 issue, a flag has been added to disable the flexresize with Microsoft Internet Explorer 11.
SR-C40003 · Issue 391481
Custom filter section submit button fixed
Resolved in Pega Version 8.1
The Submit button in a Custom Filter section was not showing correctly in out-of-the-box report browsers. To resolve this, the pzRRDisplayCustomFilterSection harness has been updated with a new button control.
SR-C40010 · Issue 382499
Corrected URL formation problem when using Tomcat
Resolved in Pega Version 8.1
A blank screen was seen when trying to open Decision Table headers, and the color picker pop-up was blank when trying to choose a color for the skin. This was traced to an incorrect URL formed when using Tomcat, caused by the prweb/hash being appended twice in the URL. The root cause was unnecessary decoding of extURL in 'pzDisplayModalDialog' , and this has been fixed by adding the proper urlCrossScriptingFilter.
SR-C40033 · Issue 379079
Import of revision package fixed
Resolved in Pega Version 8.1
The importing of a Revision package was not working as expected, and the site was not able to import new revisions in revision management. This was an issue with incorrect property initialization causing a failure in the update of the access group when doing a rollback of the revision, and has been corrected by removing the Property Initialization in Activity pyRollOutToAllAGs.