TDM Task Overview
Data generation or extract, provisioning, and entity reservation are implemented by creating and executing TDM tasks.
A TDM task is created in the TDM App and holds a list of instructions and settings that define the data source, task actions, subset of processed entities and/or tables, the target environments and additional information. For example, a TDM task might: Extract 5 customers with small and medium business plans from Production and load them into the UAT target environment.
The actual data processing and entity reservation are performed during task execution, where each task can be executed multiple times.
TDM 10: Simplified Task Management and Execution
Overview
TDM 10 introduces a revolutionary simplified way to provision and manage test data — one that makes it easier for testers, developers, and business users to run tasks independently, with confidence, and without needing deep TDM expertise.
The classic TDM workflow remains fully supported: users can continue creating and executing tasks as they always have. TDM 10 adds a complementary model on top of that — one where expert engineers define governed tasks that can be used as templates, and task runners run them through a clean, guided UI, editing only the attributes the creator has explicitly allowed.
The result is a governed self-service model that enables non-experts to run approved tasks safely while allowing experts to retain full control over task behavior.
A Simpler Way to Execute Tasks
The simplified execution model is designed around two goals: making life easier for testers, and giving task creators better control over what each user group can do.
Rather than requiring every task runner to understand the full scope of a task's configuration, TDM 10 lets qualified engineers set that up once — and then hand off a streamlined execution experience to the people who need it. Task runners get a guided window tailored to their role, with sensible defaults already in place and only the relevant parameters exposed.
This means:
- Testers and business users can run tasks without technical assistance
- Creators retain full control over governance, scope, and defaults
- Each user group sees only the tasks they are permitted to execute
- Only attributes the creator has explicitly unlocked can be changed at runtime
Key Capabilities in TDM 10
TDM 10 delivers several new capabilities that together make up the simplified task execution experience:
Tasks as Templates — Pre-defined tasks can be used as templates. The creator sets the purpose, scope, and default values once; task runners run from that baseline every time. The task itself acts as a reusable template. Runtime changes apply only to the current execution and never modify the saved task definition.
Creator Controls — Task creators decide, attribute by attribute, what task runners may change. Everything else stays locked, ensuring governance and defaults are preserved across every execution.
Self-Service UI — Execution is available directly in the TDM Self-Service portal. A guided window walks task runners through only the parameters relevant to them — no API calls, no technical background required.
Expanded Parameter Overrides — A broad set of attributes can now be marked as editable by the creator, giving task runners meaningful flexibility exactly where it's appropriate.
Task Groups — Tasks are organized into logical groups by domain, team, or use case, with collapsible group navigation that makes it fast to find the right task without sifting through a flat list.
Execution Dashboard — A unified operations center gives each user a complete view of their task activity — history, in-progress runs, and scheduled executions — with the ability to rerun any previous execution directly from the UI.
How Simplified Tasks Work
The model is built on a clear separation of roles.
Task Creator
The creator is a qualified engineer or data expert who:
- Sets the task's purpose, scope, and default parameter values
- Marks each attribute as either editable (task runner may override) or locked (task runner cannot change)
- Optionally leaves editable attributes empty, so the task runner provides the value at runtime
- Assigns which users or Fabric roles are permitted to execute the task
Only users with the appropriate Fabric roles can create tasks.
Task Runner
The task runner — a developer, tester, or business user — works in a simple, guided execution window:
- Sees all task parameters, with clear visual indication of which are editable
- Edits only the attributes the creator has unlocked
- Runs the task without modifying the underlying template
- Can view and rerun previous executions from the dashboard
Execution never alters the task itself. The template remains intact for future runs.
Attributes Available for Runtime Override
When defining a task, the creator selects which of the following attributes task runners may adjust at runtime. Anything not marked editable is locked and cannot be changed.
| Attribute | What the Task Runner Can Do |
|---|---|
| Business Entity (BE) | Select a BE at runtime if left empty in the template; locked if populated by the creator |
| Source Environment | Pick a different source environment per run |
| Target Environment | Pick a different target environment per run |
| Selection Method | The following attributes can be overridden:
|
| Synthetic Data Generation Parameters | Edit the parameter values and/or add new parameters |
| Task Globals (Variables) | Provide or override values for Fabric Global variables defined in the task |
| Entity Reservation | Enable or disable entity reservation, and set how long reserved entities are held (units and value) |
| Data Version (Snapshot) | Select an existing snapshot to load (load tasks), or set the retention period for a newly extracted data version (extract tasks) |
| Per-LU Settings | Override per-LU execution settings: maximum number of workers, source affinity, and target affinity |
| Table Filters | Adjust filter values applied to reference tables included in the task |
| Pre-Execution Process Inputs | Supply input parameter values for pre-execution processes |
| Post-Execution Process Inputs | Supply input parameter values for post-execution processes |
| Execution Note | Attach a free-text note to the execution for tracking or documentation purposes |
Access Control and Task Groups
Task creators control not just what task runners can change, but who can execute at all.
During task creation, the creator can restrict execution to:
- The creator only
- The creator's user group
- Specific named users or Fabric roles
- All users
This permission model integrates directly with Fabric roles, so access follows the same identity framework used across the K2View platform.
Tasks are also assigned to task groups — logical collections organized by domain, team, or use case. Task runners browse tasks through collapsible group navigation rather than a flat list, making it much faster to find the right task.
Simplified Execution at a Glance
Summary
TDM 10's simplified task execution model makes it easy for any team member to run test data tasks confidently — without needing to understand the full configuration behind them. Expert engineers define the template and the guardrails once. Testers, developers, and business users execute from a clean, guided interface, with exactly the flexibility they need and nothing more.
The classic TDM workflow is still there for those who want it. Simplified execution is an additive capability — a better experience for the teams that need it most.
TDM Task Overview
Data generation or extract, provisioning, and entity reservation are implemented by creating and executing TDM tasks.
A TDM task is created in the TDM App and holds a list of instructions and settings that define the data source, task actions, subset of processed entities and/or tables, the target environments and additional information. For example, a TDM task might: Extract 5 customers with small and medium business plans from Production and load them into the UAT target environment.
The actual data processing and entity reservation are performed during task execution, where each task can be executed multiple times.
TDM 10: Simplified Task Management and Execution
Overview
TDM 10 introduces a revolutionary simplified way to provision and manage test data — one that makes it easier for testers, developers, and business users to run tasks independently, with confidence, and without needing deep TDM expertise.
The classic TDM workflow remains fully supported: users can continue creating and executing tasks as they always have. TDM 10 adds a complementary model on top of that — one where expert engineers define governed tasks that can be used as templates, and task runners run them through a clean, guided UI, editing only the attributes the creator has explicitly allowed.
The result is a governed self-service model that enables non-experts to run approved tasks safely while allowing experts to retain full control over task behavior.
A Simpler Way to Execute Tasks
The simplified execution model is designed around two goals: making life easier for testers, and giving task creators better control over what each user group can do.
Rather than requiring every task runner to understand the full scope of a task's configuration, TDM 10 lets qualified engineers set that up once — and then hand off a streamlined execution experience to the people who need it. Task runners get a guided window tailored to their role, with sensible defaults already in place and only the relevant parameters exposed.
This means:
- Testers and business users can run tasks without technical assistance
- Creators retain full control over governance, scope, and defaults
- Each user group sees only the tasks they are permitted to execute
- Only attributes the creator has explicitly unlocked can be changed at runtime
Key Capabilities in TDM 10
TDM 10 delivers several new capabilities that together make up the simplified task execution experience:
Tasks as Templates — Pre-defined tasks can be used as templates. The creator sets the purpose, scope, and default values once; task runners run from that baseline every time. The task itself acts as a reusable template. Runtime changes apply only to the current execution and never modify the saved task definition.
Creator Controls — Task creators decide, attribute by attribute, what task runners may change. Everything else stays locked, ensuring governance and defaults are preserved across every execution.
Self-Service UI — Execution is available directly in the TDM Self-Service portal. A guided window walks task runners through only the parameters relevant to them — no API calls, no technical background required.
Expanded Parameter Overrides — A broad set of attributes can now be marked as editable by the creator, giving task runners meaningful flexibility exactly where it's appropriate.
Task Groups — Tasks are organized into logical groups by domain, team, or use case, with collapsible group navigation that makes it fast to find the right task without sifting through a flat list.
Execution Dashboard — A unified operations center gives each user a complete view of their task activity — history, in-progress runs, and scheduled executions — with the ability to rerun any previous execution directly from the UI.
How Simplified Tasks Work
The model is built on a clear separation of roles.
Task Creator
The creator is a qualified engineer or data expert who:
- Sets the task's purpose, scope, and default parameter values
- Marks each attribute as either editable (task runner may override) or locked (task runner cannot change)
- Optionally leaves editable attributes empty, so the task runner provides the value at runtime
- Assigns which users or Fabric roles are permitted to execute the task
Only users with the appropriate Fabric roles can create tasks.
Task Runner
The task runner — a developer, tester, or business user — works in a simple, guided execution window:
- Sees all task parameters, with clear visual indication of which are editable
- Edits only the attributes the creator has unlocked
- Runs the task without modifying the underlying template
- Can view and rerun previous executions from the dashboard
Execution never alters the task itself. The template remains intact for future runs.
Attributes Available for Runtime Override
When defining a task, the creator selects which of the following attributes task runners may adjust at runtime. Anything not marked editable is locked and cannot be changed.
| Attribute | What the Task Runner Can Do |
|---|---|
| Business Entity (BE) | Select a BE at runtime if left empty in the template; locked if populated by the creator |
| Source Environment | Pick a different source environment per run |
| Target Environment | Pick a different target environment per run |
| Selection Method | The following attributes can be overridden:
|
| Synthetic Data Generation Parameters | Edit the parameter values and/or add new parameters |
| Task Globals (Variables) | Provide or override values for Fabric Global variables defined in the task |
| Entity Reservation | Enable or disable entity reservation, and set how long reserved entities are held (units and value) |
| Data Version (Snapshot) | Select an existing snapshot to load (load tasks), or set the retention period for a newly extracted data version (extract tasks) |
| Per-LU Settings | Override per-LU execution settings: maximum number of workers, source affinity, and target affinity |
| Table Filters | Adjust filter values applied to reference tables included in the task |
| Pre-Execution Process Inputs | Supply input parameter values for pre-execution processes |
| Post-Execution Process Inputs | Supply input parameter values for post-execution processes |
| Execution Note | Attach a free-text note to the execution for tracking or documentation purposes |
Access Control and Task Groups
Task creators control not just what task runners can change, but who can execute at all.
During task creation, the creator can restrict execution to:
- The creator only
- The creator's user group
- Specific named users or Fabric roles
- All users
This permission model integrates directly with Fabric roles, so access follows the same identity framework used across the K2View platform.
Tasks are also assigned to task groups — logical collections organized by domain, team, or use case. Task runners browse tasks through collapsible group navigation rather than a flat list, making it much faster to find the right task.
Simplified Execution at a Glance
Summary
TDM 10's simplified task execution model makes it easy for any team member to run test data tasks confidently — without needing to understand the full configuration behind them. Expert engineers define the template and the guardrails once. Testers, developers, and business users execute from a clean, guided interface, with exactly the flexibility they need and nothing more.
The classic TDM workflow is still there for those who want it. Simplified execution is an additive capability — a better experience for the teams that need it most.
