Appian Community and Appian Academy are being upgraded. As a part of the upgrade, Appian Community is currently in read-only mode, and user registration is disabled until August 3. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!

The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.

Choosing Between Appian’s Built-In Human Tasks vs Custom Task List Database

Hi Appian Team and Community,

We’re designing a generic, audit-compliant task module to support multiple business processes—KYC, retail and corporate loan origination, ESG, and more. Before finalizing our architecture, I’m weighing two approaches for task management:

Option 1: Appian’s Built-In Human Tasks via Process Models

  • Uses process reports and task assignment rules

  • Tasks are tied to process instances

  • UI and SLA logic driven by Appian’s native task engine

Option 2: Custom Task List Database

  • We build our own TASK_GROUP and TASK tables

  • Tasks are instantiated based on business rules and metadata

  • UI, counters, and SLA logic are fully controlled via record types and expressions

My Questions:

  1. If we rely on Appian’s built-in human tasks, what happens if the process instance is deleted or archived? – Can we still access task metadata (status, assignee, timestamps) via process reports or APIs?

  2. What are the trade-offs between using Appian’s native task engine vs a custom task registry? – Especially in terms of auditability, lifecycle control, and cross-process reuse

  3. Is it common practice in enterprise-grade implementations to build a custom task pool for traceability and reporting? – Or do most teams rely on Appian’s built-in task management?

For context: our vendor recommended the database-driven approach, citing limitations in Appian’s native task handling—particularly around long-term traceability, cross-process reuse, and lifecycle control once processes are deleted. That inspired us to explore a fully generic task registry that can support dynamic instantiation and stage-based progression across domains.

We’re aiming for a scalable, future-proof design that supports dynamic task instantiation based on business rules, stage-based progression, and full audit history. I’d love to hear how others have approached this, and what Appian recommends for long-term maintainability.

Thanks in advance!

Thanks in advance!

 

  Discussion posts and replies are publicly visible

Parents
  • Certified Lead Developer

    1) No. Store any relevant data to database.

    2) Instead of re-inventing the wheel, I go for process tasks in 99% of all my use cases, even for global organisations with large work loads. This works great.

    3) My recommendation, from more than 15 years of enterprise Appian projects, is, to go with process tasks.

Reply
  • Certified Lead Developer

    1) No. Store any relevant data to database.

    2) Instead of re-inventing the wheel, I go for process tasks in 99% of all my use cases, even for global organisations with large work loads. This works great.

    3) My recommendation, from more than 15 years of enterprise Appian projects, is, to go with process tasks.

Children
No Data