SR-117921 · Issue 174204
Warning message displays for ruleset save in lower version
Resolved in Pega Version 7.1.7
If a developer tried to save a rule in lower ruleset version while the same rule is already in a higher ruleset version, this was allowed with no warning. This behavior has been corrected.
SR-117923 · Issue 171578
Remedied spurious size alert from the attachments viewer
Resolved in Pega Version 7.1.7
When listing attachments from History & Attachment display, the work object was re-read for each attachment. If the work object had many attachments, the alert "PEGA0004 alert (50MB DB threshold)" would appear regardless of the actual attachments' size. This has been adjusted so the RUF attachment access makes use of the existing WorkPage instead of re-reading it from the database.
SR-117961 · Issue 174233
Datetime conversion smoothed for SQL queries
Resolved in Pega Version 7.1.7
If the date time format on an SQL Server 2008 instance is set to ydm, a datetime conversion error was created due to the PRPC query using ymd format. In order to support all date formats for SQLServer, Timestamp is now formatted as "yyyyMMdd HH:mm:ss:SSS".
SR-118029 · Issue 173069
BIX filtering corrected
Resolved in Pega Version 7.1.7
Bix filters were not working consistently due to a missing call in the logic handling the ruleset references, and are now working correctly.
SR-118036 · Issue 171165
Corrected column width auto expand issues in decision table
Resolved in Pega Version 7.1.7
Decision tables which have many columns (8+) will expand the width very wide automatically by just clicking on the resize cursor (no dragging is necessary). However, trying to resize it back to a more reasonable width caused it to keep getting wider and wider due to an error with the dynamic display logic. This has been fixed.
SR-118061 · Issue 175102
CorrNew activity can send email in sync or batch
Resolved in Pega Version 7.1.7
When attempting to send email correspondence in synchronous mode i.e. not via the agent processing, the activity always queued it to the agent even when the Activity CorrNew SendNow param was set to true. To correct this, the system will pass the value of a BatchSend param based on the value of the SendNow param: email will be sent immediately If SendNow is set to 'yes', or will be queued for batch processing if SendNow is set to 'no'.
SR-118125 · Issue 171188
Circumstance property value carried into dropdown options
Resolved in Pega Version 7.1.7
If a property of mode single value and type text was created with a defined local list of property values for the property, the value field was not automatically included in the dropdown options when attempting to use this property for circumstance/specialized flows. This was caused by an incorrect refresh section strategy used to determine when to reload the section for the circumstance by property, and has been corrected.
SR-118170 · Issue 171859
Property History TaskName field expanded
Resolved in Pega Version 7.1.7
Previously, the TaskName field was limited to 32 characters. This has been expanded to 128 characters.
SR-118190 · Issue 172520
Drag and drop work reassignment corrected
Resolved in Pega Version 7.1.7
An error was found that prevented the ability to drag and drop a request from workbasket to worklist or from worklist to workbasket in the Case Manager portal. This has been corrected.
SR-118259 · Issue 173287
LookupList opened to unauthenticated requests
Resolved in Pega Version 7.1.7
When a list lookup was called from an unauthenticated service, it failed due to the lack of required authentication. The activity RULE-CIRCUMSTANCE-DEFINITION LOOKUPLIST has been modified to allow its execution by an unauthenticated requestor.