Smart services In process model

I strongly suggest to stay with the normal way this works, using process model alerts. Is there a specific reason you want to do this in a different way?

I strongly suggest to stay with the normal way this works, using process model alerts. Is there a specific reason you want to do this in a different way?

Thanks for your response Stefan, yes I want to do in different way . could you please suggest any way?

I understand. But why? Trying to customize Appian default behaviour just increases the effort to develop applications. The value added must be bigger than the effort by an order of magnitude.

But if you insist on ignoring the Appian way, Sanchit already provided an alternative.

Hi Stefan,

We have a similar use case but with some differences as we are using call integration smart service which have been configured to maximum timeout of 300sec in place of write2DSE, and in place of send email we have to call another integration which will create a ticket on third party system with the reason behind why integration call failed in first path. 
We have configured the retry mechanism that retries 3 times if integration result is not success which sometime takes more than 12-15mins to move to next node.

And another use case is we are purging data which have been created more than 7 years back with query database smart service and in the same way if the purging gets failed, inspite of triggering mail we want to call integration to create a case/ticket at reporting system.

Thanks,

Gaurav Singh