Dependencies for customizations

Individual solutions, patches, or Feature Packs for customizations must have dependencies to corresponding updates of the parent standard product. Not having these types of dependencies can result in runtime compatibility problems. For example, if only a solution for the standard parent product is installed, and the installation of an update for the customizations was also required.

To establish these dependencies, define co-requisite dependencies between the updates of the parent product and the corresponding updates for the customized product. The co-requisite dependencies are generated automatically if the customization uses the same solution numbers that were also used in the parent standard product. This method only works if the customization base VRC, and the standard product base VRC, are part of the same base VRC combination at the distributor side. At the recipient side, the update VRCs for the parent standard product and the customization must also be included in a VRC combination.

The co-requisite relationship is only in one direction: from the customization to the standard parent product. You cannot install a solution for the customization without simultaneously installing the corresponding standard solution for the parent product. When you have not scanned the customized solution, you can still install a solution for the standard parent product without simultaneously installing the corresponding solution of the customization. This can result in runtime compatibility problems. The customization report solves this problem. When you check standard solutions in a customized environment, you can optionally print a customization report. This report signals customized components and informs the recipient that, together with the standard solution, an update for the customization must also be installed.