Hi All,
Just wondering if there is a standard/encouraged pattern for managing retries of BPM's within a process orchestration. For example, a bulk extract is sent async to PO which requires a couple of web services to be called in a row (say a synchronous lookup followed by a synchronous update). Maybe the second update fails due to missing data in the called system, or the system is unavailable. We want to be able to use the standard set of alerting tools (via Sol Man) to alert either a technical user who can then clear the alert so that the service can be executed again or alternatively cancelled and manually handled.
For reference, I wouldn't want to structure a BPMN and user task around this as a solution as that would complicate the scenario unecessarily in my mind (requiring additional tasks to be populated in our UWL (which is the ERP POWL and doesn't have connectivity to BPM), and I'm hoping interim or end events (which have a type of error) would be usable.
I've tried to find something but struggling to find anything in the community or help material and for reference, I'm one of those architects who doesn't necessarily get his hands too dirty, so forgive me for not trying out a few options and providing a candidate approach. If there's a good example in the sample patterns, just point me at that.
Thanks,
Matt