SR-D5904 · Issue 511600
Discard changes dialog now showing for local actions
Resolved in Pega Version 8.2.5
After having modified case data without saving and clicking on a menu entry (left menu, search, ...), the system shows a dialog box to ask the user to confirm it is ok to discard changes. However, this confirmation dialog did not work with local actions, leading users to lose their work without any warning nor any way to step back. This was traced to a difference in the dirty form check, which was not present when launching a local action from a case. An enhancement has now been added to the handleMenuAction js function in pypega_ui_harnessactions.js which will perform a dirty form check with a prompt.
SR-D5904 · Issue 488562
Discard changes dialog now showing for local actions
Resolved in Pega Version 8.3.1
After having modified case data without saving and clicking on a menu entry (left menu, search, ...), the system shows a dialog box to ask the user to confirm it is ok to discard changes. However, this confirmation dialog did not work with local actions, leading users to lose their work without any warning nor any way to step back. This was traced to a difference in the dirty form check, which was not present when launching a local action from a case. An enhancement has now been added to the handleMenuAction js function in pypega_ui_harnessactions.js which will perform a dirty form check with a prompt.
SR-D5904 · Issue 490489
Discard changes dialog now showing for local actions
Resolved in Pega Version 8.1.7
After having modified case data without saving and clicking on a menu entry (left menu, search, ...), the system shows a dialog box to ask the user to confirm it is ok to discard changes. However, this confirmation dialog did not work with local actions, leading users to lose their work without any warning nor any way to step back. This was traced to a difference in the dirty form check, which was not present when launching a local action from a case. An enhancement has now been added to the handleMenuAction js function in pypega_ui_harnessactions.js which will perform a dirty form check with a prompt.
INC-182986 · Issue 668828
Property Rule Form refreshes after discarding changes
Resolved in Pega Version 8.6.2
After updating from Pega 8.2 to Pega 8.6 and migrating the properties, modifying any property rule and then discarding the change did not refresh the Property Rule Form. Investigation showed that the LOG-SYSTEM-PROPERTYOPTIMIZATION instance created during property optimization was not getting deleted when a property was deleted. As this was not getting deleted, the property was shown as optimized when adding the property back, causing confusion. This has been resolved by cleaning up the LOG-SYSTEM-PROPERTYOPTIMIZATION instance when the property is deleted and there is an optimization entry.
INC-182986 · Issue 668829
Property Rule Form refreshes after discarding changes
Resolved in Pega Version 8.7
After updating from Pega 8.2 to Pega 8.6 and migrating the properties, modifying any property rule and then discarding the change did not refresh the Property Rule Form. Investigation showed that the LOG-SYSTEM-PROPERTYOPTIMIZATION instance created during property optimization was not getting deleted when a property was deleted. As this was not getting deleted, the property was shown as optimized when adding the property back, causing confusion. This has been resolved by cleaning up the LOG-SYSTEM-PROPERTYOPTIMIZATION instance when the property is deleted and there is an optimization entry.
SR-116936 · Issue 167898
Discarded threads set to properly clear on refresh or tab close
Resolved in Pega Version 7.1.7
When the browser was refreshed or an inactive recent tab was closed on the client side, the discarded threads were not getting properly cleared at the server end. To remedy this, the JavaScript has been updated to cleanly remove the threads.
SR-C73425 · Issue 413722
Fixed error when trying to discard a circumstanced Report Definition rule
Resolved in Pega Version 8.2
Attempting to discard and delete a circumstanced Report Definition rule resulted in an error on screen, in the tracer, and in the log file. This was caused by the system being unable to identify a reserved property when circumstanced on an embedded page or primary page. To correct this, the saveCircumstanceIndex rule of Rule- activity's first step has been modified to get the circumstanced property for this use.
SR-C73425 · Issue 413723
Fixed error when trying to discard a circumstanced Report Definition rule
Resolved in Pega Version 8.1.3
Attempting to discard and delete a circumstanced Report Definition rule resulted in an error on screen, in the tracer, and in the log file. This was caused by the system being unable to identify a reserved property when circumstanced on an embedded page or primary page. To correct this, the saveCircumstanceIndex rule of Rule- activity's first step has been modified to get the circumstanced property for this use.
SR-D42566 · Issue 512873
ApplicationInventory function deleted
Resolved in Pega Version 8.4
It was possible to call the activity "ApplicationInventory of class Rule-" by appending the activity name in the URL. To improve security, the ApplicationInventory activity and HTML rule have been removed from the system.
SR-D42566 · Issue 512871
ApplicationInventory function deleted
Resolved in Pega Version 8.3.2
It was possible to call the activity "ApplicationInventory of class Rule-" by appending the activity name in the URL. To improve security, the ApplicationInventory activity and HTML rule have been removed from the system.