How to customize the success and exception windows |
Optionally, your application can override the processing and user presentation of activity success and failure messages.
By default, when a top-level PRPC activity completes execution but does not send HTML code to a browser display, it presents a success form, defined by the standard harness @baseclass.ActivityStatusSuccess, containing a green checkmark:
Similarly, by default when an activity (at any level) encounters an uncaught Java exception or other failure condition, a red-X window appears with the text "Please contact your system administrator". This window is defined by the standard harness @baseclass.ActivityStatusError. The system also adds information about the failure or exception to the Pega log.
Your application can localize these standard harnesses, to present a different message or a message in a specific language.
Optionally, you can override either or both of these two standard harnesses to localize the text or change the wording or presentation:
IF you override the standard harnesses, keep your harnesses simple, as they may appear in a wide variety of situations. Don't assume that the entire clipboard environment of your application is present and correct.
You can override either or both of the standard activities that present the success window and exception windows. Familiarity with Java and Java exceptions is required.
Standard activity @baseclass.ActivityStatusNoContentHandler displays the success harness. This activity has no parameters.
Standard activity @baseclass.ActivityStatusExceptionHander displays the exception (failure) harness. This activity access a single Java Object parameter that is an instance of the java.util.Map interface. It copies the error information on a page and then uses the @baseclass. ActivityStatusHarness to display the information.
To override the default activities:
If you override the standard activities, keep your activities simple, as they may execute in a wide variety of situations. Exceptions that occur during exception processing may mask the original cause. Don't assume that the entire clipboard environment of your application is present and correct.
About Activity rules
How to prevent display of traceback details |