Advice on alerting error on failed business rule / rest call

DLHill
Giga Guru

Hi

 

We currently have the situation:

    record created in table -> business rule -> script include -> rest api push

and due to the need to meet a deadline the error handling (esp if the push fails) is to log loads of good info on gs.info and we manually search the log regularly. Obviously we want to change asap that but can't decide best practice short term.

Medium/long term I believe that Flow Designer can replace the business rule, make the rest call and handle the response but I need to investigate how to do that. In the meantime we want to be notified if the rest call gets a error code returned to it somehow, ideally with an incident being logged.

I think we should add code to the business rule to create an incident but is there a better way? I also want to apply this to the job that runs weekly making rest calls .

Thanks in advance for your thoughts

Debbie

1 ACCEPTED SOLUTION

DLHill
Giga Guru

Update! I went with code to create the incident as it should be infrequently used and obvs it passed test env testing.

 

I also realised that I was focused on errors. Noted success is better than only noting errors as nothing could mean success or failure and no incident created. Therefore we are now talking about adding an a update to the req or task to show that the API was successful, and the support staff can see that so there should be less questions to us!

View solution in original post

1 REPLY 1

DLHill
Giga Guru

Update! I went with code to create the incident as it should be infrequently used and obvs it passed test env testing.

 

I also realised that I was focused on errors. Noted success is better than only noting errors as nothing could mean success or failure and no incident created. Therefore we are now talking about adding an a update to the req or task to show that the API was successful, and the support staff can see that so there should be less questions to us!