Create a Package of Business Administrative Changes
The Export Changes tab in the Business Administrative Change utility provides the ability to create a package containing business administrative changes for exporting them to a production Windchill system.
To create a package, perform the following steps:
1. On the Export Changes tab, specify the date range and object types of the changes that you want to export, and click Search.
The Select Changes section lists the changes based on the specified criteria. If you do not specify the object types, the changes for all object types are listed.
* 
The Description column displays information only for the Life Cycle Template and Workflow Template objects.
The Modified By column displays the name of the container owner.
* 
The system displays an alert if the search results exceed 1000 records. You can set the value for the desired number of search records in the com.ptc.windchill.bac.client.preview.maxPageSize property in the wt.properties file. However, we strongly recommend you use the default value of 1000 records for optimal performance.
2. Under Select Changes, select the required changes and click Create Package.
The Review and Create Package dialog box opens.
3. In the Review and Create Package dialog box, specify a name for the package and optionally, a description.
4. Review the changes that will be included in the package. If any object has a dependency on another object, include that object as well. To edit the selection, close this dialog box and update the selection on the Export Changes tab. Then, relaunch the Review and Create Package dialog box.
Certain business administrative objects have dependencies on artifacts that are not managed by the business administrative change framework or artifacts that are code or files managed within WT_HOME, such as StateRBInfo resource bundles. Following is a list of business objects and possible dependencies that may be required to be applied to the target system to successfully import a package of business administrative changes.
Business Administrative Object
External Dependencies
Access control rule
Life cycle state
Life cycle template
Life cycle state
Team template
Actor or role
Series
Object initialization rule
Versioning sequence
Workflow process template
Custom classes for workflow expressions
Team template
Actor or role
Share Table Views
Owner of the view
Context
Rule Sets
Independent (Rule Set has no dependencies because it is a primary object.)
* 
The Rule Sets collection category collects three object types: rule, rule set, rule set link. These are the primary interconnected objects.
Report
Report template (if report is created from report template)
Client tab
Owner
Context
Rule Sets
Independent (Rule Set has no dependencies because it is a primary object.)
* 
The Rule Sets collection category collects three object types: rule, rule set, rule set link. These are the primary interconnected objects.
5. Click Create.
A success message is displayed after the package is created. A zip of the package is downloaded locally.
Was this helpful?