Recently I have a requirement where in we have a mechanism where Trigger gets disabled and doesnt enable back until , I purge the event manually from Universal Messaging. I do not want to manually do it, instead want a service to purge the event and then enable back the trigger for me.
Question is:
how to i purge the event from designer.(Is there any built -in service available)
First of all I’m unsure why your trigger is getting disabled automatically?
Is 'deleting a single (multiple?) event(s) ’ a workaround to enable back trigger which you are following?
If there is genuine reason and your approach is very much required, then below are some answers to your questions as per my knowledge.
If all events need to be purged, better to delete and create trigger. I don’t know any IS service available for this, probably you need to rely on UM APIs for purging.
For JMS based triggers, there are services available to enable/disable triggers pub.trigger:disableJMSTriggers and pub.trigger:enableJMSTriggers
For webM triggers, we can’t enable/disable trigger rather we can enable/disable document/event retrieval/processing using services avaialble in pub.triggers directory
The mechanism is built in such a way where in any failure happens, can be validation/business error, the trigger gets disabled to stop further impact over the others.
Well, I guess I need to look into some UM API’s. Any idea where can i find them?