| Create Patch Code (ttiex4200m000) |  |
| Use this session to define a patch that contains all components, such as sessions, forms and program scripts, of a package VRC. To create a patch, you must specify basic properties, such as: Patch code The VRC to which the patch's components belong The VRC into which the patch must be imported The path where the patch file must be generated Subsequently, click Create Patch to generate the patch file. Important! In this session, you cannot select the components that will be included in the patch: all components of the selected export VRC will be included. To create a patch that contains only a subset of software components of a package VRC, use the Patch Codes (ttiex4500m000) session. Note s A patch file must be distributed to the relevant recipients/customers. You can, for example, place the patch file on a web site, so that the recipients can download it. Recipients of patches, e.g. customers, must import their patches through the Import Patch (ttiex1284m000) session. Important! Do not use this session to create patches that must be imported through the Product Maintenance and Control (PMC) module. To create PMC solutions, use the Solutions (ttpmc1100m000) and Patches (ttpmc1501m000) sessions. For details on PMC, refer to: PMC recipient procedure PMC distributor procedure
Fields | Description
Patch Code | A patch code identifies a patch that consists of components. For example: Forms Program scripts Sessions
Do not regenerate existing patch | If you select this check box, the patch will not be generated if the patch code already exists.
Description | The description or name of the patch.
Package | The package to which the patch's components belong.
Export VRC - Version | The version of the package VRC that contains the patch's components. You can only include components of a single VRC in a patch.
Export VRC - Release | The release of the package VRC that contains the patch's components. You can only include components of a single VRC in a patch.
Export VRC - Customer | The customer extension of the package VRC that contains the patch's components. You can only include components of a single VRC in a patch.
Import VRC - Version | The version of the package VRC into which the patch's components must be imported. This VRC is selected automatically when the patch is imported via the Import Patch (ttiex1284m000) session.
Import VRC - Release | The release of the package VRC into which the patch's components must be imported. This VRC is selected automatically when the patch is imported via the Import Patch (ttiex1284m000) session.
Import VRC - Customer | The customer extension of the package VRC into which the patch's components must be imported. This VRC is selected automatically when the patch is imported via the Import Patch (ttiex1284m000) session.
Languages | The language(s) for which language-dependent components, such as labels, messages and reports, will be included in the patch.
Sources Included | If this check box is selected, the sources of scripts and libraries (e.g. program scripts, DLLs and DAL(2) scripts) and functions are included in the patch. Only deliver sources to recipients that are allowed to change the source codes. If the check box is cleared, only the compiled versions (e.g. session objects, DLL objects, DAL(2) objects and function objects) are included in the patch.
Pathname | The path name of the folder in which the patch file must be generated.
Including Common Data | If this check box is selected, additional technical data (e.g. information on BMS Mask and domains that must be displayed as check boxes) is included in the patch file.
Commands | Description
Create Patch | Click this button to generate the patch file. The following components are stored in the folder that you specified in the Pathname field: a patch file. This is a compressed file that contains the patch's components. The recipient of the patch must import this file through the Import Patch (ttiex1284m000) session. The name of the patch file is identical to the patch code. However, the file name is in lower case, while patch codes are always in upper case. A content list that contains the names of the exported components. The name of this file is "<patch file name>.content".