When publishing a package, each item in the package that is approved will be published. If the item is already published but not in sync, it will be synchronized. Not all configuration items have an approved and publish step. These are considered approved and published directly when imported.
Some configuration items are ready to use after import and some require a manual publishing step to be effective. This table shows if manual publishing is required for the configuration items that can be added to a package.
| Item Type | Publish/Synchronize | Comment |
|---|---|---|
| Custom Menu | Automatic | |
| Information Card | Manual | |
| Custom Field | Manual | |
| Custom Logical Unit | Manual | |
| Custom Page | Automatic | Published when the Custom Logical Unit the page is connected to is published. |
| Custom Tab | Automatic | |
| Custom Enumeration | Manual | |
| Conditional Field Action | Automatic | |
| Custom Events | Manual/Automatic | Manual if the Event does not previously exist in the target environment, automatic when it does. If an Event has an enabled Event Action, the Event will automatically get enabled when publishing the package. |
| Custom Event Actions | Automatic | If the event action is enabled, the corresponding trigger will be generated and deployed. Hence, if the trigger references non existing tables or columns, it will give an error when importing. As a workaround, this issue can be avoided by disabling such event actions before importing or making sure those non existing objects have already imported and published with a separate ACP. |
| Quick Report | Automatic | Needs to be granted to users in order to be accessed. |
When publishing Custom Fields or Information Cards from the respective administration page, all attributes on that Logical Unit that are approved will get published. The situation is more complex when publishing an Application Configuration Package. When publishing a package that have Custom Fields or Information Cards, other attributes on involved Logical Units may get affected despite that they do not belong to that package. The following situations can occur for attributes that are not part of a package being published, if there is an attribute in the same LU which is in the package.
| Approved | Published | Result | Comment |
|---|---|---|---|
| No | No | Not Published | |
| No | Yes | Not Published | The published attribute not belonging to the package will no longer be published! |
| Yes | No | Not Published | The item is not published. The Custom Field or Information Card is set as not synchronized |
| Yes | Yes | Published | The item will be synchronized even though it does not belong to the package! |