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.
SR-129062 · Issue 194086
App Explorer enhancement sets number of properties displayed
Resolved in Pega Version 7.1.8
If there were a large number of properties in a navigation panel of App Explorer, only a few properties were shown and a link displayed 'Show all results'. It was then not possible to optimize a property inside a page list in Work Class as it was displayed under new tab when 'Show all results' was clicked. This was found to be an issue with the behavior of Property Optimization wizard being different when it is launched from App Explorer menu than from when it is launched from RuleForm-->Actions menu. The system now provides an extension point for clients to increase the number of properties that appear in the App explorer. The default is 100, with a max cap of 10000.
SR-129062 · Issue 195029
App Explorer enhancement sets number of properties displayed
Resolved in Pega Version 7.1.8
If there were a large number of properties in a navigation panel of App Explorer, only a few properties were shown and a link displayed 'Show all results'. It was then not possible to optimize a property inside a page list in Work Class as it was displayed under new tab when 'Show all results' was clicked. This was found to be an issue with the behavior of Property Optimization wizard being different when it is launched from App Explorer menu than from when it is launched from RuleForm-->Actions menu. The system now provides an extension point for clients to increase the number of properties that appear in the App explorer. The default is 100, with a max cap of 10000.