When to Build
A build can occur automatically (with no user interface) after being triggered by a user-invoked action (for example, Check In or Promote). Alternatively, a build can occur based on a manual request (for example, from an explicit Build Structure action invoked on the CAD document information page)
Automatic Builds
An automatic build retains the convenience of having the build occur without any user intervention (as in prior releases). You may configure the system to automatically build at the default values after the following events.
• Creation of a new CAD document iteration with a build rule to a part
• Change of state of a CAD document with a build rule to a part
• Modification of the CAD Document Master with a build rule to a Part
• Some combination of the conditions in the preceding bullets
• Never occur automatically
An automatic build might also need to build more than just the object affected. The object’s children may need to be built as well. The set of children affected by an automatic build is based on their “maturity” or lifecycle state.
The capabilities of the automatic build include the following.
• Can execute on checked-in CAD documents only.
• Modify just the latest iteration, on the version of the part associated via the build rule.
• Automatically commit (check in) the changes to the parts.
• Can execute on selected CAD documents only.
Otherwise, a recursive build builds all children that meet the lifecycle state to build.
You receive success/failure messages in the Event Management utility. If the build fails, then the event that triggered it still continues, as the two structures are allowed to be out-of-sync.
Manual Builds
The command to build part structure and attributes from CAD documents is available in the following locations within Windchill.
• In a CAD document commonspace information page within:
◦ the main actions menu.
◦ the structure browser.
• In a part information page (either checked-in or working copy version) within:
◦ the main actions menu.
◦ the structure browser.
• In the Structure Editor
• In common implementation of the See Actions menu when the part is driven. For example, in:
◦ the Folder browser.
◦ the Search results.
• In the user interface for the following actions:
◦ Check In
◦ Promote
◦ Set State