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'm going to resurrect this as I see most folks advocating for the OOTB task approach - is this still the favored approach? I've long held that DB tasks are the way to go - especially in regards to scalability and control over the platform. The OOTB tasks may be faster in the short run, but long-term you are going to be paying for it if you find that you do need to transition over the DB tasks. Also - general Appian best practices is to limit the use of long-running processes, which the OOTB task approach can encourage.All this said because I'm looking for a recipe on how to implement DB tasks easily...