SR-126732 · Issue 192781
Corrected button label for JAWS
Resolved in Pega Version 7.1.8
With JAWS accessibility active, when you navigate to a menu button labeled "Other Actions", JAWS says "Menu. To move through items press up or down arrow...O" instead of reading out the title of the button. This was caused by the button being used to show the menu, which added role="menu" to it, and this has been corrected in the button generation RUF.
SR-126746 · Issue 189633
Added schema qualification to BIX / DB2 extract rules
Resolved in Pega Version 7.1.8
When using a Business Intelligence Exchange (BIX) extract rule which included writing the manifest details to external database tables, running the extract rule generated errors for the insert into the pr_extract_summary and pr_extract_details tables. This issue existed both when running from the command line and from the User Interface (UI). This was traced to the extract code not schema qualifying the pr_extract_summary and pr_extract_details tables in the insert statements, so it is expecting those tables to be in the schema of the user who is defined in the Database rule. This has been corrected through code changes for DB2 external databases that includes currentSchema=YourSchemaName in the URL connection to the external database.
SR-126746 · Issue 185231
Added schema qualification to BIX / DB2 extract rules
Resolved in Pega Version 7.1.8
When using a Business Intelligence Exchange (BIX) extract rule which included writing the manifest details to external database tables, running the extract rule generated errors for the insert into the pr_extract_summary and pr_extract_details tables. This issue existed both when running from the command line and from the User Interface (UI). This was traced to the extract code not schema qualifying the pr_extract_summary and pr_extract_details tables in the insert statements, so it is expecting those tables to be in the schema of the user who is defined in the Database rule. This has been corrected through code changes for DB2 external databases that includes currentSchema=YourSchemaName in the URL connection to the external database.
SR-126775 · Issue 189860
Resolved HTMLtoPDF font load error
Resolved in Pega Version 7.1.8
When using a Fonts directory during HTMLToPDF conversion, the StaticContent folder resolved to an incorrect properties file and generated an error that appeared to indicate the fonts had not correctly loaded even when they had indeed loaded. The error was traced to the function used to open the Static Content folder with the direct file handle, and this has been updated to resolve correctly.
SR-127644 · Issue 192194
Refresh When' behavior fixed for portal tabs
Resolved in Pega Version 7.1.8
When a 'Refresh When' was active on a portal tab, the system would become unresponsive while trying to refresh it. This was caused by an incorrect element call resulting in a JavaScript error and has been corrected.
SR-127799 · Issue 192294
Included CMIS library updated
Resolved in Pega Version 7.1.8
Using Connect-CMIS Rule form, attempting to get a list of Repositories from a CMIS Server that allows Web service binding with Basic Authentication was failing with 401 - Unauthorized error. The getRepository operation succeeded when using SOAPUI or Apache Chemistry CMIS client Workbench. This was a defect with the particular CMIS library version included with Pega 7.1.7, and has been corrected by updating to a revised version.
SR-127838 · Issue 194007
Parse XML validation default set to "Never"
Resolved in Pega Version 7.1.8
In some cases, the parse XML rules function was not correctly mapping all of the input types. The root cause for the different failure modes seen was found to be that validation was set to "Always" by default, and the rule data did not reflect this until after a manual Save or Save-As. The default has now been set to "Never", and can be manually adjusted to "Always" or "When" as desired.
SR-127838 · Issue 194658
Parse XML validation default set to "Never"
Resolved in Pega Version 7.1.8
In some cases, the parse XML rules function was not correctly mapping all of the input types. The root cause for the different failure modes seen was found to be that validation was set to "Always" by default, and the rule data did not reflect this until after a manual Save or Save-As. The default has now been set to "Never", and can be manually adjusted to "Always" or "When" as desired.
SR-128063 · Issue 193580
Added schema qualification to BIX / DB2 extract rules
Resolved in Pega Version 7.1.8
When using a Business Intelligence Exchange (BIX) extract rule which included writing the manifest details to external database tables, running the extract rule generated errors for the insert into the pr_extract_summary and pr_extract_details tables. This issue existed both when running from the command line and from the User Interface (UI). This was traced to the extract code not schema qualifying the pr_extract_summary and pr_extract_details tables in the insert statements, so it is expecting those tables to be in the schema of the user who is defined in the Database rule. This has been corrected through code changes for DB2 external databases that includes currentSchema=YourSchemaName in the URL connection to the external database.
SR-128118 · Issue 191010
Workbasket name updated in Case Manager portal
Resolved in Pega Version 7.1.8
When CaseManager portal was launched and any particular WorkBasket selected, the text "WORK IN XXXXX WORKBASKET" was shown. XXXXX was the WorkBasket name, which was being picked from RuleName(Identifier) instead of ShortDescription. This was unexpected, and has been changed.