SR-126468 · Issue 192170
CheckInCandidates rule issue resolved
Resolved in Pega Version 7.1.8
When checking in a rule via the rule Check-in Approval process, it was not possible to add rows. The problem was traced to the approved request being returned from the workbasket with the "Allowed to update row layout" checkbox unchecked. When check-ins are done via the Rule Approval process, the checked-in rule's copy is read from the database: however, due to the property 'pyAllowedToChangeRowsStr' incorrectly being left marked as transient for the Check-in Approval process, the property was not retrieved from database if that process was used. To correct this, 'pyAllowedToChangeRowsStr' property has been unmarked as transient.
SR-126513 · Issue 192544
Edit in Excel now handles 'HTTPOnly'
Resolved in Pega Version 7.1.8
After implementing 'HTTPOnly', Decision Table Edit in Excel was not working. Attempting to use it caused the system to stall for a few seconds while the label color was orange, and then the text color on the button went back to black but no Excel file popped up. This was found to be caused by the lack of a null check in case of HTTPOnly cookies in the edit_in_excel js function, and this has now been added.
SR-126552 · Issue 190069
Exception handling added for link updates in Upgrade Wizard
Resolved in Pega Version 7.1.8
The error 'Unable to save because null' appeared when the activity linkupdateutility was called during post upgrade. This was an exception caused by a missing '#' sign being sought from the pxLinkedRefFrom property of an element in the page list UseCaseFlowShapeLinks, and the handling for that exception has been added.
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-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-128829 · Issue 180467
Added multi-class localization for DisplayRFHarnessErrors
Resolved in Pega Version 7.1.8
When Rule DisplayRFHarnessErrors was in two different classes, @baseclass and Rule-Obj-Flow, the localization check box was previously only available under @baseclass and not for Rule-Obj-Flow. This has been updated so the marked rule in rule-obj-flow is also localized when checked under @baseclass.
SR-128829 · Issue 193680
Added multi-class localization for DisplayRFHarnessErrors
Resolved in Pega Version 7.1.8
When Rule DisplayRFHarnessErrors was in two different classes, @baseclass and Rule-Obj-Flow, the localization check box was previously only available under @baseclass and not for Rule-Obj-Flow. This has been updated so the marked rule in rule-obj-flow is also localized when checked under @baseclass.
SR-130695 · Issue 200024
Added handling for "(" and ")" in parameter value
Resolved in Pega Version 7.1.8
A backwards compatibility issue was found in the declare expression ruleform where if a parameter passed to a function alias contained ")" or "(", the data was not shown in the UI. This has been fixed by modifying the parsing logic to handle cases where parameters passed to the function alias might have an unexpected format such as "(" inside a parameter's value.
SR-130695 · Issue 200339
Added handling for "(" and ")" in parameter value
Resolved in Pega Version 7.1.8
A backwards compatibility issue was found in the declare expression ruleform where if a parameter passed to a function alias contained ")" or "(", the data was not shown in the UI. This has been fixed by modifying the parsing logic to handle cases where parameters passed to the function alias might have an unexpected format such as "(" inside a parameter's value.