Notify External System for Personal Data work queue
|
Code |
|
|
Categories |
|
|
Implementation |
Work queue |
|
Schedule |
Not scheduled |
|
Class |
PersonalDataDestructionNotifyExternalSystemsWorkQueue.gs |
PersonalDataDestructionRequest objects for which both of the following
are true:- The object has a status that matches a typecode in the
DestructionStatusFinishedcategory. - The object
RequestersNotifiedfield is set tofalse.
The work queue processes any found requests by sending a notification to all associated
requesters. It then marks the RequestersNotified field as
true. If the notification fails, the work queue throws an exception and
the RequestersNotified field remains false.
A method on the PersonalDataDestruction plugin,
notifyExternalSystemsRequestProcessed, is called by
PersonalDataDestructionNotifyExternalSystemsWorkQueue to notify external
systems when a personal data destruction request is completed. The original
RequestID is passed to the method, which does nothing by default. You are
expected to implement this method to notify systems of interest. The
RequestID is received when the destruction request is originally created
through the PersonalDataDestructionAPI web service.
By default, Guidewire does not add an entry for this work queue to file scheduler-config.xml in the base configuration. To schedule this work queue, add an entry for it to scheduler-config.xml.
Notes
- The implementation class for Notify External System for Personal Data work queue is
PersonalDataDestructionNotifyExternalSystemsWorkQueue. In your implementation, you must verify that the notification was successful before markingRequestersNotifiedastrue. - In the base configuration, the implementation class for the PersonalDataDestruction plugin is PCPersonalDataDestructionPlugin.
See also
