A Task Template can be associated with multiple processes
-
True
-
False
A Task Template is associated with a single, specific process. The template defines the UI layout, fields, and actions for tasks belonging to that particular process. While different processes can have task templates that look similar, each template must be explicitly linked to one process definition. This one-to-one association ensures that tasks render correctly with the appropriate fields and workflow actions for their process.
The marked answer is False, meaning a Task Template is tied to a single process, not shared across multiple processes. In workflow/BPM tools, a Task Template usually defines the specific fields, actions, and behavior for one particular task type within one process definition; reusing it verbatim across unrelated processes would break the tight coupling between the template's fields and that process's data model. This is a tool-specific (likely a BPM/workflow platform) modeling rule rather than general CS knowledge, so it's asserted based on typical workflow-tool design rather than a universally known fact.