| | Dependencies (ttpmc1140m000)Use this session to define the dependencies
between solutions or patches. You can generate the dependencies automatically, or define the
dependencies manually. If not all dependencies that would be generated are present,
you receive a warning during the export of the solution or patch. After you define all the dependencies, you can change the
solution status to Dependencies defined and the solution is
ready to be exported. You can change the status in the details session of the Solutions (ttpmc1100m000) session. If the status of the solution was Exported,
and you change the dependencies, then the solution status is reset to Dependencies defined. You can only start the current session through the Vues, Références, Actions menu in the Solutions (ttpmc1100m000) session. Base VRC A means in PMC to identify products in a unique way. Updates at
the distributor side are provided with the base VRC identifier. A base VRC can
contain the code of the physical VRC in which the related master product is
installed, for example, B61_a, but can also be a code not related to a physical
VRC, for example, 7.6_a_tt. At the recipient side, every update VRC is linked
to a base VRC identifier. The installation process checks if the base VRC
identifier of the update matches with the base VRC identifier of the update
VRC. If not, you cannot install the update in that update VRC. Solution Code A unique identification of the solution in a base VRC. Related VRC The base VRC of the solution or patch to which the current solution or patch is related. Solution The solution or patch with which a dependency relation exists. Type In PMC, the relation between solutions. Dependencies are
defined at the PMC distributor side and are part of the meta data of a PMC
solution and guarantee that PMC solutions are installed in the correct
configuration and sequence at the PMC recipient side. The following values indicate the dependency type between
solutions. Three dependency types are available: You can only install solutions that are dependent on other
solutions if the other solutions are already present, or are also
installed. The same dependency types exist between patches. However, to keep the descriptions readable,
only solutions are mentioned, but patches are meant as well. One exception
applies: the post-requisite type is not applicable to patches. You must specify dependencies of type co-requisite and
prerequisite for the solution being created. You must add post-requisites dependencies to the already
released solution and the post-requisite dependency must point to the solution
being created. Remarque Be sure to add the post-requisite dependency before you
release the new solution. The post-requisite dependency is transferred to the
recipient in the dump of the solution being created. This implies that this
dependency is only known at the recipient side after the newly created solution
has been scanned. Manual If this check box is selected, the dependency was not
generated, but defined manually. Remarque If you generate or regenerate the dependencies, the Generate Dependencies (ttpmc1240s000) session start. In this session, you can specify whether
or not you want to delete existing manually defined dependencies. | |