This tutorial shows how to collect user feedback in Advanced ETL Processor with the User Input action. Use it for interactive testing and debugging, not unattended agent execution. A scheduled package waiting for someone to type a comment is automation doing an impression of a doorbell.
What You Will Learn
- Prompt a user for text, memo, date, number, file, or folder input.
- Store entered values in package variables.
- Use user input while debugging an interactive package workflow.
- Avoid User Input actions in agent-run or separate-thread execution.
Before You Start
Use a test repository or safe sample data while following the tutorial. Production jobs are a poor place to experiment.
User Input Action Docs
This tutorial uses the User Input action to collect values during an interactive package run. The action is useful for debugging because it can pause the package and ask for a value. It does not work when the execution agent runs the package or when the package runs in a separate thread.
The User Input documentation covers the parameters tab, variables tab, execution log tab, and input prompt types.
Prompt types include text, password, memo, HTML, date, date time, time, integer, numeric, boolean, file, and folder.
Related interactive actions include Ask Question Action, Show Message Action, and Select Value Action. For troubleshooting, also review 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.