Many projects follow the best practice of putting linked files (.rvt, .dwg, Point Clouds, markups, etc.) in one or more specific worksets. This allows the Revit file to be opened with linked file workset(s) closed while still opening the critical worksets. This will result in a faster and cleaner PDF export process.
In this topic you can learn how Ideate Automation controls the open workset condition.
If the selected Ideate Automation script does not contain an
CloseWorkset command option, then the file open condition defaults to the last saved workset state. If that state is to Specify Worksets, then Ideate Automation accepts the existing workset open condition without making any changes.
Opening a Revit file open with all worksets open will make the file opening process take the longest time but has the benefit of including all data about the file and any linked files. The following built-in scripts are setup to open the Revit file with all worksets open by default:
AUT-Revit_File_Data— This script is set to default to open with all worksets open in order to obtain consistent file open times data, but can be changed as shown above.
AUT-Export_DWGand AUT-Export_DWG_Long — These scripts are set to open with all worksets open in order to ensure the resultant DWG output includes all data.
AUT-Export_IFC— This script is set to open with all worksets open in order to ensure the resultant IFC output includes all data.
AUT-Export_NWC— This script is set to open with all worksets open in order to ensure the resultant NWC output includes all data.
ANN-Export_Issues— This script is set to open with all worksets open in order to that all views will render correctly. This is required for proper clash detection results.
IBL-Document_Issuance— This script is set to open with all worksets open in order to include revision info from linked files for quality assurance. This is an optional setting.
Opening a Revit file open with all worksets closed will make the file opening process take the shortest time. Several workflows do not require the overhead of this extra data in order to deliver accurate results.
The following built-in scripts are setup to open the Revit file with all worksets closed because the data output is not impacted by the workset state:
The following built-in scripts are setup to open the Revit file with all worksets closed because the data output is typically is not impacted by the workset state. These scripts are hard-wired to open with all worksets closed. This means that any linked file data will be excluded from the export unless the command option is changed within the script.
Opening a Revit file while excluding certain worksets will make the file opening process take a shorter time while allowing data found within other worksets to still be included.
The following built-in scripts are setup to open the Revit file with an option to specify which worksets should be closed during the file open process. As shown in the image above, the Exclude Worksets option defaults to find any workset that includes the word “link” within the workset name and makes those close. You can add additional criteria or select the red X to remove the criteria.
Per the requirements listed within the Description of these tasks, in order to be able to use a script that includes this command option, the workset data must first be cached locally. This can be done by first running the AUT-Get_File_Data task.
Thank you for taking time to inform us about a bug or feature request.