Is there any means to set the return of a calljob or callprocess on a Trigger as an error so that the Event appears on MDM Event Manager as FAILED?
I'm getting further into my problem scenario so that you can better understand what I'm wanting to do.
After a recorde creation, which fires an UpdateReport, a trigger is called upon some conditions. The trigger calls a job (or a process that will call a job, it's the same) that will sync some data to other application. The Job tries to create some data on this 3rd party application related to the data inserted on the MDM Hub, via webservices. What if the host on which the webservice resides is down? Or someone changed the password for that webservice and the webservice fails? My job already has the capability to detect that it fail its main purpose, but there should be a way that the Job returns an error so that the Event Manager will store this Routing as FAILED. This way, after the host has came up (or the password changed to the proper value) it can be run again and the data correctly syncs on the 3rd party app. How can this be done?
Hope I've made myself clear.
Now, the ability to signal MDM that the trigger should fail for functional reasons is not a bad idea either. The event manager keeps all failed "routing order" (the document that results from matching an event to a trigger) in the failed queue, so you can retry them later. Dble click the event mgr in the studio, browse the failed queue, right click to retry a routing order.
There are no tMDM component to automate that by the way...
I am starting to find this idea interesting...
I'm taking a look on eXist and MDM webservices to see if there is a way to set the Event as FAILED. As the Event is just another entry on the eXist DB and there should be a reference of the UpdateReport identifier on the UpdateReport fired.
0=ok or 1=failed
Thanks very much for this comment. It help me to think about my ideals.
Tks again and pls keep posting.