TotalAgility: The Clarity Series • 4 min read

TotalAgility: Process vs. Case Management - When Should You Use Each?

What is the difference between Process and Case Management in Tungsten TotalAgility? In Tungsten TotalAgility (TTA) formerly Kofax TotalAgility (KTA) a standard Process models a predictable, start-to-finish sequence of steps (like an assembly line for invoice routing), whereas Case Management manages an outcome where the exact sequence of steps is unknown in advance (like a fraud investigation or customer complaint). Cases use a base process, reusable case fragments, milestones, and runtime ad-hoc tasks so knowledge workers can adapt on the fly without creating unmaintainable "spaghetti" workflow maps.

If you add enough conditional branches, backward loops, and business rules, you can technically force a standard TotalAgility Process to mimic a Case. But just because you can doesn't mean you should. Here is how to choose the right modeling approach for your next project—and how we structure maintainable workflows in our Tungsten TotalAgility consulting services.

1. The Core Mental Model: The Assembly Line vs. The Detective

The real difference between a Process and a Case is not what TotalAgility can technically draw, it is how predictable the work is at runtime:

• A Process Is an Assembly Line (Control the Sequence): Step A happens, then Step B, then Step C. Even with exception paths, the overall sequence is known when you design it. For example: Receive Invoice → Extract Data → Validate → Approve → Post to ERP.

  
  

• A Case Is a Detective Investigation (Manage the Outcome): You know the end goal, solve the case or resolve the claim—but the exact steps depend on what the investigator discovers along the way. One case may need a witness interview and legal review; the next may need financial records and a compliance check in a completely different order.

2. The "Spaghetti Map" Trap: What Happens When You Force a Process to Act Like a Case

When developers try to use a standard Process for unpredictable human work, they have to anticipate every possible "What If" scenario at design time:

• What if the customer uploads an extra document halfway through?

  
  

• What if Legal needs to review the file before Finance or after?

  
  

• What if the customer disputes the outcome and reopens an earlier step?

  
  

  
  

Within a few months, your process map accumulates dozens of overlapping lines, backward loops, and exception branches until it looks like a bowl of spaghetti. The workflow might still run, but it becomes nearly impossible for another developer to read, troubleshoot, or update without breaking something in production. (If your legacy KTA environment already suffers from overly complex maps, running an automated scan with TA Audit quickly flags excessive branching and maintainability risks.)

3. How TotalAgility Case Management Solves Human Unpredictability

Instead of drawing one giant map connecting every possible future step, TotalAgility Case Management builds a flexible container around three core features:

A. Case Fragments (Your Bucket of Reusable Tasks)

A Case Fragment is a modular sub-process associated with a case. It has all the power of a normal process activities, SLAs, resources, and business rules, but it shares direct access to the parent case’s variables, states, and roles. Instead of forcing a rigid path, you give the case a bucket of fragments (such as Investigate Dispute, Request Customer Evidence, or Compliance Review) that can be triggered in any order, as many times as needed, until the case is resolved.

B. Milestones (Keeping the Case Focused on the Goal)

A Milestone represents a key target date or checkpoint in the case lifecycle such as Case Opened → Initial Review Due → Investigation Target → Resolution Target. Even though the daily work inside the case is flexible, milestones keep SLAs on track and can fire automated triggers or escalations when a target date approaches.

C. The Lifesaver: Runtime Ad-Hoc Tasks

The single best feature for operational teams is the Ad-Hoc Task. In a rigid Process, if a caseworker suddenly needs an extra document or a specialist sign-off that wasn't drawn on the original workflow map, they are stuck waiting for a developer change request. In a TotalAgility Case, the worker simply creates a new Ad-Hoc Task on the active case job setting the description, due date, priority, and user or group assignment and keeps moving.

4. The Hybrid Architecture: Combining Cases and Sub-Processes

You do not have to choose between 100% Process or 100% Case. The cleanest enterprise intelligent automation architectures combine both:

• The Case Is the Master File: It holds the customer context, tracks high-level milestones, manages roles, and lets knowledge workers make judgment calls.

• Deterministic Sub-Processes Do the Heavy Lifting: Whenever the Case needs predictable busywork done such as classifying an incoming document, extracting table data, or posting a transaction to SAP it kicks off a structured background Process and returns the clean data back to the Case.

  
  

5. The Architect’s Cheat Sheet: How to Pick the Right Model

Before building your next TotalAgility workflow, run through these rules:

• Use a Standard Process IF: The work is predictable, happens in a set sequence, and relies heavily on straight-through automation such as touchless AP invoice processing, standard document classification, or fixed approval routing.

  
  

• Use Case Management IF: The end goal is known but the path is not, human judgment drives the next step, and workers need on-the-fly Ad-Hoc Tasks such as fraud investigations, customer complaints, appeals, or complex customer onboarding and claims workflows.

  
  

• Use a Hybrid Model IF: You are managing a long-running customer or investigative file (Case) that periodically triggers repeatable background automation tasks (Processes).

  
  

Designing a complex case management solution or untangling a legacy KTA workflow? Talk to our Certified Master Developers through our Tungsten TotalAgility consulting services.

TotalAgility Process vs. Case Management FAQ

What is the difference between a Process and a Case in Tungsten TotalAgility?

A normal TotalAgility Process executes a predefined, start-to-finish sequence of steps for repeatable work. A TotalAgility Case manages variable, outcome-driven work using a base process, modular case fragments, milestones, and runtime ad-hoc tasks that adapt as knowledge workers investigate and make decisions.

What is a Case Fragment in TotalAgility?

A case fragment is a sub-process associated with a TotalAgility case. It contains standard workflow nodes, resources, and SLAs, but remains dependent on the parent case with direct access to shared case variables, states, and milestones allowing fragments to be started dynamically in any order.

How do Milestones work in TotalAgility Case Management?

Milestones represent key target dates or lifecycle checkpoints within a TotalAgility case. They track progress toward the final outcome and can trigger automated alerts, escalations, or background processes when target deadlines approach or pass.

Can users create Ad-Hoc Tasks in TotalAgility without a developer?

Yes. TotalAgility Case Management allows authorized users to create runtime ad-hoc tasks directly on an active case job, specifying the task description, priority, due date, and assigned person or group without modifying the underlying workflow design.

Can a TotalAgility Case trigger normal automated Processes?

Yes—the most effective enterprise architectures use a hybrid model where the TotalAgility Case manages the overall customer file, milestones, and human decisions, while triggering deterministic sub-processes in the background for OCR extraction, validation, and ERP integration.