Business Administrative Change UI Utility Features

This topic outlines the key features, supported use cases, and limitations of the Business Administrative Change UI utility:

Use Cases	Supported Features and Limitations
Administrative objects	Supports a subset of administrative objects, such as life cycle templates, preferences, profiles, and so on. For more information, see Objects Supported for Business Administrative Change Promotion.
Modes of export	Supports only the selective mode of export. This cannot be changed.
Specification for export	Supports filtering by date when exporting administrative changes.
Incremental use cases	Not supported.
System ID registration	No system ID changes are needed. Package exchange between systems is supported by default.
Conflict resolution	Supports bundled mapping as a resolution method. Conflicts can be resolved by mapping user context and groups. 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	Not required. When importing packages, set the com.ptc.windchill.bac.ignoreGUIDList property to All.
Baseline support	Not supported.
User groups and policy access control rules	Supports the Business Administrative Change Package Creator and Business Administrative Change Package Importer user groups, along with their policy access control rules.

Was this helpful?