These days I have seen developers moving to using database tasks rather than a traditional User Input Task approach.
What are the possible advantages of using DB tasks in terms of reducing memory footprint, creating short lived processes, performance, concurrency and auditing?
Any way whether a process task report or using DB task, we'll be creating tasks to save task IDs, then how it is different and advantageous in comparison to process task report approach?
Discussion posts and replies are publicly visible
I strongly suggest to stay with Appian OOTB as much as possible. Use processes and UITs. This is what Appian is made for. And this is not a "traditional" vs "somethingElse". IMHO, this is more about people trying to force Appian into a use case it is not made for.
And yes, there are use cases which cannot be implemented in the "traditional" way. But they are very rare.