SR-129768 · Issue 200019
Resolved error saving to lower version unlocked ruleset
Resolved in Pega Version 7.1.8
An error was encountered when attempting to save a rule in an unlocked lower version if a higher level locked version existed. This has been corrected by removing a redundant post condition in the activity Rule-RuleSet -> pzGetOpenRulesetVersions.
SR-129892 · Issue 196786
Error handling improved for BIX extraction called by an agent
Resolved in Pega Version 7.1.8
Running BIX extract from an agent (which calls activity runExtract) caused the BIX logfile to grow to enormous size due to an infinite loop after encountering a JDBC 'connection reset' error. Handling for this error has now been added to ensure smooth extraction from an agent.
SR-128430 · Issue 194956
Pagination removed from OwnersList to facilitate large category lists
Resolved in Pega Version 7.1.8
After having created a large number of categories from the "Reporting" landing page, the list of available owners was not the expected one when creating a new shortcut. The owner drop down list is generated by the ListView called "Rule-Category.pzGetCategoryOwnersList." Unfortunately this ListView is a FINAL rule and paging was enabled with a default count of 50 entries. In order to allow for customizations like the above, OwnersList has been modified to disable paging.
SR-128696 · Issue 195043
Fixed alignment of columns and headers in RD scroll headers setting
Resolved in Pega Version 7.1.8
If "Do not scroll header" was checked in Report Definition, there was an alignment issue with the header and report Data. This has been fixed by updating "GenerateCellContent" to generate the CSS classes in the markup, and the CSS style was added to "pyReportEditorStyling" and is commented to make it available there if desired.
SR-129117 · Issue 196578
Resolved agent/tenant parent/child access for disabled agents
Resolved in Pega Version 7.1.8
When a shared system had an agent which was disabled, doing a "Save As" of the agent into the tenant env (to different application / RS) by logging into the tenant and enabling the agent failed with the error "No such Access group." This happened because the agent rule (created in the tenant) was running in the context of the shared system instead of the tenant system and could not find the access group. The issue was that the runActivityAsTenant function was not working as expected in the case of a child requestor trying to use the parent requestor's authorization, and this has been fixed.
SR-130224 · Issue 200002
Fixed class pickup when Ticket Urgency is used as reference
Resolved in Pega Version 7.1.8
It was not possible to convert a summary report to a list report if the report had Ticket.Urgency as a reference and Ticket was a single page pointing to data class type property in the work class. This was traced to the drill down picking up the Urgency property from the work class, and has been resolved.
SR-130345 · Issue 199748
Added qualification to validation queue page creation
Resolved in Pega Version 7.1.8
After migration, executing custom business logic validation generated the error "There was a problem getting a list". This was due to the JS code generating an unqualified QueuePage, and has been resolved.
SR-130401 · Issue 201418
Fixed listview filtering header shift
Resolved in Pega Version 7.1.8
When using a list view in a section with filtering enabled, applying any filter criteria caused the header to shift down vertically and create a gap. This was a display div error, and has been fixed.
SR-130401 · Issue 200029
Fixed listview filtering header shift
Resolved in Pega Version 7.1.8
When using a list view in a section with filtering enabled, applying any filter criteria caused the header to shift down vertically and create a gap. This was a display div error, and has been fixed.
SR-130421 · Issue 200325
Corrected double firing after copying trigger to superclass
Resolved in Pega Version 7.1.8
After copying a commit trigger from PegaSample-CustomerRequest to PegaSample and withdrawing the original, the new version fired twice on commit. This was caused by the RuntimeDeclarativeClassCore not properly handling the duplicate, and has been corrected.