Requirement to have a task alive for more than a year

Certified Associate Developer

We have a request to keep a task open for longer period of time say 6month - 1 year , what are the best practices we need to follow for this case , suppose subprocess run with MNI and creates 100+ task and each should be alive for more than  6 months to one year , please advise what are the best practices we can follow ? 

  Discussion posts and replies are publicly visible

Parents
  • Certified Senior Developer

    Database-driven approach would be better choice to achieve this.
    Storing tasks involves leveraging relational database tables to store task-related data. This approach provides scalability, flexibility, and performance benefits compared to storing tasks directly within the Appian platform.

Reply
  • Certified Senior Developer

    Database-driven approach would be better choice to achieve this.
    Storing tasks involves leveraging relational database tables to store task-related data. This approach provides scalability, flexibility, and performance benefits compared to storing tasks directly within the Appian platform.

Children
No Data