Integration with Other Applications > Windchill Workgroup Manager Documentation > Cadence Team Design Option > Administration and Configuration > Policy File Overview
  
Policy File Overview
The policy file contains the configurations for the system project level. For each system project there must be one policy file. You must specify this policy file to apply the system project when you launch the Enable Team Design wizard from the Cadence Team Design Option dashboard.
Cadence ships the Cadence Team Design Option application with a policy file template that you can edit and customize according to your requirements. It contains the following information for each design object:
Exec steps provide information on how to create the tar files. This specifies the content of Windchill objects and gives you the ability to merge multiple objects into one.
Pre Exec and post Exec operations to be provided. You can provide the command along with the parameters that you want to execute. For example, in pre exec you can specify that cleanup be done before the exec operation that creates the tar files.
By default, the pre exec operation for a schematic runs bomhdl to generate the logical BOM. Similarly for PDF, Used Component .csv file, and so on.
An option that specifies whether the design object gets checked out manually or automatically along with another object. This is true only for Package and Constraints. For example, Package Design can be automatically checked out/in along with Logical/Physical objects.
For more information about creating a custom policy file for a project, see Customizing the Policy File to Generate Derived Data.
To Modify the Policy File of a Checked-in Project
1. From the TDO dashboard, check-out the Project_settings file.
2. Update the exiting policy file located in the “.sdm/policy” folder, or replace it with a newly created file.
3. From the TDO dashboard, check-in the Project_settings file.
* 
Customers who choose to update the policy file do so at their own risk.
The project integrator must be made aware of the changes to the policy file in order to understand their impact on the project.
Customers must only make necessary changes to the policy file, and make such changes manually.