Priority and triggers

By default, all tools and macros within a project run with maximal parallelism. However, this is not always desirable, because you might need some actions to occur before others. For example:

• Creating or altering a database table before writing to it.

• Updating a database table before querying the table.

• Writing or replacing a file before reading it.

Previous versions of Data Management used priority settings to direct some tools to execute before others, either by setting priorities on individual tools, or by establishing priority orders at the project level. However, priorities are complex and difficult to specify, and do not support a rich action-sequencing model.

With version 9.1.1, the Data Management priority model is deprecated in favor of the Triggers feature. Support for priority settings may be removed from future versions of Data Management.