SR-127237 · Issue 190840
Time-related RUFs now use operator's time zone
Resolved in Pega Version 7.1.8
Date properties and Time properties were taking their reference from the server's default time zone, which created unexpected behaviors for operators in other time zones using start and end date functions. This has been resolved by updating the time-related RUFs to use the operator's defined time zone
SR-127237 · Issue 189891
Time-related RUFs now use operator's time zone
Resolved in Pega Version 7.1.8
Date properties and Time properties were taking their reference from the server's default time zone, which created unexpected behaviors for operators in other time zones using start and end date functions. This has been resolved by updating the time-related RUFs to use the operator's defined time zone
SR-127256 · Issue 193682
Added trace to ensure system pulse syncs nodes after schemas added
Resolved in Pega Version 7.1.8
After editing a decision table on Node A, the Pulse/vtable on Node B was not invalidating the pulse entry, resulting in wrong rule getting picked up. This was caused by having two data schemas implemented, where the second one was put in place after the initial migration scripts were run. Therefore any rule change events were sent to the wrong schema. This has been corrected with an added vtable global trace.
SR-127306 · Issue 193879
Added special character handling for Tooltips labels and icons
Resolved in Pega Version 7.1.8
Tooltips on labels and error icon were displaying the corresponding escape characters instead of the special characters intended. HTML screens did display these characters correctly. There was a workaround overriding the function in UserWorkForm, but this has been resolved by ensuring the value is html encoded and tooltip is using this value.
SR-127319 · Issue 197788
Updated cache searching for Obj-Browse on a class mapped to external table
Resolved in Pega Version 7.1.8
Unnecessary queries were being fired while using Obj-Browse on a class mapped to external table. This was caused by a class mapped to an external table and using Obj-Browse on that class fired queries to the metadata to get the columns instead of searching in the caches. The system has been updated so that the caches are read instead of firing querying the metadata every time to get the list of columns.
SR-127336 · Issue 190764
Corrected tagging in DCO process documents
Resolved in Pega Version 7.1.8
After migration, DCO document - Application profile - specifications were not tagged to the proper steps. For steps where connector had a blank value, chapter headings were not listed in the document. Assignment shapes can be linked to specifications in Pega 7 which was not possible earlier, and shape information for assignments was not carried in the case of Application Profile document. To correct this, the method "flowShapes()" of "PegaAccel-Task-DocumentApp.WorkTypes" has been updated, and the defaults for the Chapter Headers are now fetched by the method "shapeHeader()" in the "PegaAccel-Task-DocumentApp.WorkTypes" section.
SR-127372 · Issue 194363
Fixed ColorPicker control event firing
Resolved in Pega Version 7.1.8
ColorPicker controls associated with a Property which has a default value and configured with an OnChange refresh were not updating when a new color was chosen and instead required an explicit refresh. This was found to be two problems: If there is a value for the property, the background color was set on the inner div and not being replaced when update occurred. Since the color was also being set in the outer div, the inner div setting was unnecessary and has been removed. For the update itself, the processDialog API was not firing the change event upon submit of the modal dialog, but if the event was fired then it implicitly had a refresh added in the markup and was refreshing the section twice. To correct this, the change event is fired from the processDialog API instead.
SR-127380 · Issue 192186
Resolved problem importing work objects into tenant layer
Resolved in Pega Version 7.1.8
Trying to import a RAP containing several work objects into the tenant layer of a multitenant system generated errors including "Import cannot proceed due to conflicting rule instances." This was caused by certain import restrictions regarding work objects belonging to a shared content class that were set during the initial development of multitenancy which are no longer required; these have now been removed.
SR-127388 · Issue 193584
Corrected handling of radio buttons in repeat grids with page groups
Resolved in Pega Version 7.1.8
In the generate radio group, when the radiobuttons control was placed in a repeat grid bounded with page group, the ID attribute of the radio input tag was not in the group and was being generating uniquely, causing the buttons to not hold their value when one was updated. To correct this, the regular expression pattern in pzgenerateradiogroup has been modified to include the page group as well as the page list.
SR-127470 · Issue 192220
Autogenerated CSS for harness skin fixed
Resolved in Pega Version 7.1.8
When using the autogenerated CSS of a skin in a harness, the tags generated for input types were not applied. This was due to the CSS being incorrectly formed, which has been corrected