Change Package Object Support
Change packages support objects in the tables below at the following levels:
-
Full: You can add the object to a change package and it installs successfully.
-
Semi: You can add the object to a change package and it can be installed, but manual action is required on the target system to complete the process. For example, enabling an endpoint after installation or updates to a component model or shared configuration properties. Objects that reference business rules or workflows do not have these associations included in the dependency analysis or impact analysis, so there is manual effort to confirm all necessary business rules are included in the Primary Items. Typically, these have an orange background color.
-
Addition only: You can add the object to a change package will not be installed. This level provides a reminder of a 'to-do list' item with the option to add details for the installer in the Instruction parameter within the change package, describing the manual configuration. For example, when a scheduled export or bulk update is required, the BGP ID can be searched for in the Add Items window and selected. A BGP is not created on installation, however the Instruction can include details about the timing and frequency, business rule or export configuration and collection required, making an external document unnecessary.
-
Unsupported: You cannot add the object to a change package. These can be addressed by adding an instruction for the installer via metadata on the change package itself when a custom attribute is added to the change package object type.
Additional information is included in the VCSI: Considerations and Limitations topic.
* The Tags node cannot be added to include all tags, but Tag Groups can be included. All tags in a group are included.