When running the Release Models task in a Specification Flow, all rules associated with the Model Rules and Generation Tasks are evaluated; the models to be generated are placed in a queue. The generation is completed either through the DriveWorks Pro add-in inside of SOLIDWORKS or by DriveWorks Autopilot. Both methods read the model generation queue, and the DriveWorks add-in inside SOLIDWORKS allows users to select which top-level model they wish to generate. Autopilot will simply pick the next model in the list.
Whether in your DriveWorks training or first projects, you have experimented with capturing and releasing models to your specifications. Since the models are released inside the specification, the generation of those models is linked to the specification, right? Well, no.
When introduced to DriveWorks, the context usually revolves around CAD automation. Classic demo examples include configuring folding doors, semi-truck trailers, scissor lifts, etc. Many of us see a huge benefit in being able to automate our CAD generation (along with other documents) so we do not have to configure roughly the same model for every single quote.
DriveWorks Live Integration Theme is a theme used by DriveWorks Live that hosts the DriveWorks Live Web API. It allows DriveWorks to integrate directly into a new or existing website, giving you the ability to customize the website itself to your liking, instead of having to use the pre-made DriveWorks forms through an iFrame.
In DriveWorks, users can group multiple projects into one top-level project. Certain projects lend themselves to grouping small child projects into one large project. For example, if I wanted a project for a layout of conveyor belts, I could have one project for one conveyor section, and then the layout project could contain multiple conveyor section projects and verify they all had the same width so that they would be compatible.