Basic Administration > Managing Data > Context Template Administration > Working With Context Templates > Support for Delete Operation for Context Templates
Support for Delete Operation for Context Templates
The context templates are deleted from the user interface by selecting any of the following available options:
• All — All the iterations of the context template are deleted on selecting this option.
• Non-latest — All iterations except the latest one are deleted.
• Latest — Only the latest iteration of the context template is deleted.
For the BAC utility, the ability to detect and propagate the administrative objects that are deleted is enabled with the following command. On enabling the property as shown in the example below, deleted iterations can be viewed on the UI. Restart the Windchill server after enabling the property.
xconfmanager -s com.ptc.windchill.bac.delete.tracking=true -t <Windchill\codebase\wt.properties -p
#Where <Windchill> is the installed location of your Windchill solution.
Export of the Deleted Context Template
From the BAC page, search for the context templates which are deleted. Select the required context templates and create a package.
1. Browse Site > Business Administrative Change > Object Type.
2. Select the Object Type as sContextTemplate and click Search.
3. Select the required context templates with Action as Delete and click Create Package.
4. Click Create on the Review and Create Package window.
5. Report is generated for the exported package as seen in the example below. Also, XML file is available with all the details.
Import of the Deleted Context Template
If the context template is deleted from the source system, the delete operation is propagated through a BAC operation. The context template gets deleted from the target system too.
1. Browse Site > Business Administrative Change > Import Changes.
2. Browse to the location where package to be imported is stored.
3. Click Import Package.
4. Following scenarios are reported to result in a failure and the subsequent operation fails:
◦ If the context template is already in use.
◦ If the context template is checked out.
◦ If the user who is importing the package do not have proper permissions.
Was this helpful?