debug mode for macros and script code in ETL
when writing macros or script code in ETL it is often difficult to find out what went wrong and when it went wrong.
The only way at the moment is to scan the log files for error messages.
For development it would be helpfull to have a debug mode for those scripts and macros to see step by step if they are working correctly.
This could be combined with the object manager I proposed within another feature request.