Administrative objects

Administrative objects supported for export and import include policy access control rules, measurement systems, reusable attributes, and so on. For more information, see Objects Supported for Business Administrative Change Promotion.

Only few administrative objects that the command-line utility supports are supported in the UI utility. For example, life cycle template, preference, profile, and so on. For more information, see Objects Supported for Business Administrative Change Promotion.

Modes of export

Synchronized, selective, and development.

Selective. It cannot be changed.

Specification for export

All the filtering criteria mentioned in the BACSpec.xsd or BACSpec.xml file located at <WT_HOME>\prog_examples\BAC\schema are supported.

Only date is supported in the Business Administrative Change UI.

Incremental use cases

Supported.

Not supported.

System ID registration

Need to change system ID to exchange packages between systems.

No need to change system ID. Exchange of packages between systems is supported by default.

Conflict resolutions

Need to resolve conflicts manually.

Bundled conflict resolution and bundled mapping options are not available.

Can use bundled mapping as resolution. Supports resolution by mapping of user context and group.

Import can be performed using saved or bundled conflict resolution and bundled mapping. For more information, see Import a Package of Business Administrative Changes.

Target system registration

Mandatory.

Not required. When importing packages, set the com.ptc.windchill.bac.ignoreGUIDList property to All. For more information, see Import Changes Command.

Baseline

Supported in synchronized and development modes.

Not supported.

Support for Business Administrative Change Package Creator and Business Administrative Change Package Importer user groups and their policy access control rules

Not applicable.

Applicable.