Support Article

Refresh option using RefreshOnConflicts activity throws exceptio

SA-36601

Summary



User has configured "refresh" option in actions menu in one of the scenarios.

On click of refresh button, they have used "Work-.RefreshOnConflicts" activity which refreshes the current assignment if it is valid or opens it in a review mode.

Whenever they run the scenario, below is the error reported instead of the assignment.

Status:Fail Message: There has been an issue; please consult your system administrator.


Error Messages



Status:Fail Message: There has been an issue; please consult your system administrator.


Steps to Reproduce



1. Configure the Refresh option in the Actions Menu of the tab which uses data instances details (say Data-Admin-Operator-ID).
2. Configure on click of refresh button with "RefreshOnConflicts" activity.


Root Cause



User was running the scenario in the context of "pyDisplayHarness" and the activity that was configured on click of Refresh uses "RefreshOnConflicts" that requires pyWorkPage to be present on the thread.

During runtime, the activity tries to find "pyWorkPage" and since the use case runs in the data context, there is no pyWorkPage.

Hence are the errors, as it is was unable to find the page.


Resolution



Perform the following local-change step:

Invoke an activity(TestActivity, prior to "RefreshOnConflicts") which does a page-copy of pyDisplayHarness.embeddedpage to pyWorkPage (which allows RefreshOnConflicts to find the required page during runtime)





Or an alternative approach would be to use another activity instead of "RefreshOnConflicts" that fits into use case which uses pyDisplayHarness as Primarypage during runtime.

Published April 17, 2017 - Updated May 3, 2017

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.