Update on the retirement of Application Webhooks UI and QB Actions

I just want to applaud Jim's comment (everything is SPOT on) and add one more thing.

One thing he didn't mention with Pipelines is: Once you finally get it built, you refresh the page only to find out, 'Surprise! Half your work did not save.' Alternately, you know the darn thing won't save so you check your work halfway through by pushing 'Refresh' to see if it gives you the 'Are you sure you want to navigate away dialogue box' (indicating it has not been saved). Then you sit there, not knowing what to do because your Pipeline is clearly not saved, but you have no way of forcing the issue. Then, suddenly it tells you 'oops, looks like you are offline!', and you lose your work anyways.

Please listen to Jim, because his experience is all of our experience. And I really want to highlight and reiterate 'New Style Forms aren't working, New Style Reports aren't working'.....'Pipelines is half working'.

The one thing Developers have been shouting over and over is: 'We love the advances you are trying to make. We support and encourage innovation. We love Quickbase. But please, please, please don't remove working and beloved features until you can confidently say the replacement is as good or better.' There may be no more striking example than Pipelines and New Forms to say 'These things have a lot of potential, but are a long ways away from being able to eliminate Webhooks and Legacy Forms' (Thankfully, nothing has been said about eliminating Legacy forms).