Objects Supported for Business Administrative Change Promotion
The following administrative objects are supported for export and import using the Business Administrative Change UI utility:
• Policy access control rules
• Profiles
• Object Initialization Rules (OIR)
• Preferences
• Life cycle Templates
• Workflow Process Templates
• Type Definitions
 |
The attributes on a type that were deleted from the source system are not deleted from the target system when using the Business Administrative Change UI utility. You can delete the attributes on a type using the Type and Attribute Manager on the target system.
|
• Measurement Systems
• Quantities of Measure
• Global Enumerations (includes Modeled Enumerations, Custom UI Text, and Security Labels)
• Reusable Attributes
• Document Template
• Report Template
• Visualization Configuration
• Context Template
|
|
• The Context Template object type does not currently support delete or delete-conflict functionality.
• Export and import do not support program templates, shared team templates, and collaboration workspace templates.
|
• Report
|
|
• Business Administrative Change (BAC) supports the exchange of ReportTemplate-based Jasper reports if both the report and the dependent report template are included in the export package. It is also expected that compiled JRXML and other dependent artifacts are already available on the target system.
• BAC may support the exchange of ReportTask-based and WRS-based Jasper reports in a future release. Also, BAC does not exchange Jasper reports that depend 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, organization administrators, and business administrators can be exported.
• Private tabs and tabs created by other users cannot be exported.
• A site administrator, an organization administrator, and a business 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 them for import. After import, the versioning scheme in the system is replaced with the imported versioning scheme.
For list-based versioning schemes, the user must be a site administrator or a site business administrator. After import, the versioning scheme is replaced in a manner consistent with loading the XML versioning file.
|
• Rule Sets
|
|
The Rule Sets category includes three object types: rule, rule set, and rule set link.
|
• Task Form Template
Objects that are not currently supported for export and import can still 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 must exist in the target system for the profile import 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.
|