Objects Supported for Business Administrative Change Promotion
The following administrative objects are supported for export and import using the Business Administrative Change UI utility and business administrative change promotion command-line utility:
• Policy access control rules
• Profiles
• Object Initialization Rules (OIR)
• Preferences
• Life cycle Templates
• Workflow Process Templates
• Type Definitions
• Measurement Systems
• Quantities of Measure
• Global Enumerations (includes Modeled Enumerations and Custom UI Text)
• Reusable Attributes
• Document Template
• Report Template
• Context Template
 |
• The Context Template object type currently does not support delete and delete conflicts functionality.
• The export and import do not support program templates, shared team templates, and collaboration workspace templates.
|
• Report
|
|
• Currently, BAC supports the exchange of ReportTemplate-based Jasper reports if both the report and the dependent report template are included in the export package. Also, it is expected that compiled JRXML and other dependent artefacts are already available on the target system.
• In the future, BAC may support the exchange of ReportTask-based and WRS-based Jasper reports. Also, BAC will not exchange Jasper reports dependent on JSP, resource bundles, properties, or icons or images.
|
• Shared Table View
• Client Tab
|
|
The following rules apply when exporting client tabs:
• Only public tabs created by Site Administrators and Organization Administrators can be exported.
• You cannot export private tabs and tabs created by other users.
• A Site Administrator and Organization Administrator can export the tabs created by each other. However, one Organization Administrator cannot export the tabs created by another Organization Administrator.
|
• List-Based Versioning Scheme
|
|
Only Business Administrative Change Package Creator and Business Administrative Change Package Importer user groups can export and import Business Administrative Change Packages. Users in these groups must also be authorized to read these objects for export and create or modify the objects for import. After import, the versioning scheme available in the system is replaced with the imported versioning scheme.
For list-based versioning schemes, the user must be a Site Administrator. After import, the versioning scheme available in the system is replaced with the imported versioning scheme consistent with loading the XML Versioning File.
|
• Rule Sets
|
|
The Rule Sets category collects three types of objects: rule, rule set, and rule set link.
|
Objects that are not currently supported for export and import can be referenced by the administrative objects listed above. It is assumed that these related objects are available in the target system. For example, if a participant (user, group, or organization) is a member of a profile, that participant would need to be available on the target system for the import of the profile to succeed.
|
|
The temporary directory in the installation system must have read and write access with recursive permissions when the user performs export and import actions in BAC.
|