This topic outlines the best practices when using DriveWorks with SOLIDWORKS PDM.
The following should be performed on all machines where DriveWorks generates any file that is required to be checked into SOLIDWORKS PDM.
The DriveWorks modules that can generate files include:
Therefore we recommend the PDM Local view be applied to a top-level folder/drive.
SOLIDWORKS PDM will display this user as the creator of each file generated by DriveWorks.
For example the vault view will display the message Checked in by DriveWorks next to each file.
The Plugin must be enabled and have the settings applied on each DriveWorks application that requires access to the vault.
This is done by opening each DriveWorks application, and:
See SolidWorks PDM Plugin Settings for information about the settings in the plugin.
The DriveWorks setting Default specification folder must be set to a location inside the vault that all files will be stored from.
With this set and the path rule of each file being relative (see note below) to this location, the files DriveWorks generates will all be checked into the vault after each has been driven.
Each file type has a Path parameter that can have a rule applied.
When the rule result does not start with a drive letter (D:\) or a UNC locator (\\MACHINE-NAME) the file will be created relative to the Default specification folder setting.
These files include:
Some features in DriveWorks can produce files that require an absolute (full) file path to locate the file, these include:
When using the above to create files, that require checking into the SOLIDWORKS PDM vault, the Check in a file into vault task should be added to the Specification Flow.
The SOLIDWORKS PDM plugin only supports Queued Generation (manual and automatic).
OnDemand Generation is not supported for checking models and files into the vault.
See Info: Model Generation Behavior for more information.
Individual Group files (.drivegroup) and Project files (.driveprojx) can be stored in the vault.
If revision control of the Group and Project files is required we recommend utilizing the Copy Group/ Pack and Go functionality in DriveWorks Data Management to manually create backup and restore points.
Shared Groups are SQL Server based and therefore have no physical file that can be controlled by SOLIDWORKS PDM.
The Master files, from which all files are generated, can be stored in the vault.
This entirely depends on if PDM functionality is required for the master documents and components or not.
DriveWorks will be able to copy the masters and check the newly created files into the vault regardless of where the masters are saved.
Master file versions of SOLIDWORKS models and drawings, managed by SOLIDWORKS PDM, can be selected through rules.
The following must be done to allow this:
When using separate Development and Production environments that require to be managed by SOLIDWORKS PDM, consider the following:
Or
Either scenario introduces complexities for overwriting key Production files with the revised Development files.
If revision control of the Group and Project files is required we recommend utilizing the Copy Group/ Pack and Go functionality in DriveWorks Data Management to manually create backup and restore points.
When multiple DriveWorks modules are in use the following is required on each DriveWorks machine:
To regenerate already released models and documents inside the PDM vault you will need to perform the following:
This is the only way drawing files can be regenerated with SOLIDWORKS PDM
This should be applied to the Leave State Event of the running state.
Apply the rule DWSpecificationId to the Specification Id property of the task. This will result in the Id of the currently edited specification.
Set the Type property to Existing.
See also