Scenarios

Regardless of what your slave graph is actually doing with your Revit models, the following abstract scenarios can be identified for the master graphs:

A: Process Isolated Models

Some variations:

• A1: Run the same or multiple slave graph(s) on all models in a folder
• A2: Run the same or multiple slave graph(s) on all models in a list of folders
• A3: Run the same or multiple slave graph(s) on a list of models at various locations
• A4: Run the same or multiple slave graph(s) on all models in a folder and its subfolders
• A5: Run multiple slave graphs on multiple files according to a matrix

B: Process Linked Models

Run one slave graph to find all links in a project, run a second slave graph on all links. (The variations for scenario A can, of course, be applied to scenario B, too.)

C: Process Loaded Families

Run a slave graph on all families in a folder, run a second slave graph to load all families into a project

D: Automate applications other than Revit

You can also integrate other applications into your workflow, as long as they support basic options like automatic runs and specifying which files to open. Any application that has a command line interface will definitely work.

E: Batch-purge Models

Purge is one of those commands in Revit that are not accessible with the API. However, it is possible to replay the purge command with a journal file. Since version 1.30.4, DynamoAutomation provides two nodes for doing just that. For this scenario you will only need a master graph.

The samples section contains examples for all scenarios except scenario D.