Process driven or data driven task?

Process driven! Appian is meant to implement applications driven by business processes. A business process orchestrates the collaboration of people, data and systems. Assigning a task to a person requires management by due dates, escalations and exceptions. All of this is directly implemented OOTB in Appian. Why would you want to re-implement the wheel?

And yes, there are rare use cases where the task assignment concept in Appian does not fit. I first try to advice my clients to change heir approaches before I start building DB driven tasks.

I always try to go for 100% process driven at first and I'll make adjustments along the way depending on the user requirements.

Hello vaishals,

Appian's given approach is Process Driven and Stefan has explained it precisely. So we should consider that the best way is to use the process driven. But if you want to have a complete history of audits of your tasks, then you should go for data driven. Data driven will help you keep the record of all the tasks and all the information around the task and also minimizes the long lived process instances.