This tutorial shows how to use the Case action in Advanced ETL Processor. Use it when one package must choose different next actions from a value, such as file type, customer code, status, environment, or validation result. It keeps branching logic visible in the workflow instead of hiding it in a script drawer where future you will not thank present you.
What You Will Learn
- Add a Case action to a package workflow.
- Route execution to different actions depending on a value.
- Use variables as part of conditional workflow control.
- Review the execution log to confirm which branch ran.
Before You Start
Use a test repository or safe sample data while following the tutorial. Production jobs are a poor place to experiment.
Case Action Docs
This tutorial uses the Case action to execute different workflow actions depending on a value. It is useful when a package needs clear branching without turning the workflow into a pile of small one-off scripts.
The Case Action docs cover the parameters tab, case tab, variables tab, and execution log tab.
For related package design, review linking actions, default error actions, debugging actions, and working with variables.
Need Advanced ETL Processor First?
Download the Advanced ETL Processor trial before following the tutorial, or review Enterprise if you need scheduled unattended execution.