- Variables are not exposed in the Data Process Control, and are hidden from the end-user (used for programmatic efficiency)
- Variables are easier to work with programmatically, as there is no need to delineate between "Attended" and "Unattended" status.
Data can be assigned and stored to the CONFIG_VAR table at run time, and can then be called called dynamically from the data map. This allows for more efficient code, results from repeating steps can be stored once and than reused.
At the time of this post, there are three tabs in the data pipeline that support this functionality:
- Step1 - Query
- Step2 -DataMap
- Step3 - Transformations
No comments:
Post a Comment