Automatic Patch Creation

• Type of patch (field TYPPTC)

The patch type can take the following values :

• Standard : this is a patch that is likely to be installed in a list of folders that will be given on the integration, this list integrating in principle the supervisor folder. In the majority of cases (including the specific/custom and vertical developments), it is the type of patch to be used. In fact, the delivery of specific/custom or vertical developments is not conditioned by the type of patch, but by the list of activity codes that are given in the corresponding grid.
• Supervisor  : this is a patch that will only be integrated in the supervisor folder. This type is used in order to integrate pre-parameterization elements (import/export templates, automatic journals, Workflow rules...) that may have been modified in the different folders. To avoid the deletion of the modification carried out, only the supervisor folder will be updated. This is used to have the pararmeterization values up to date in the case of the creation of a new folder and also used to manually update by copy in each folder after having used the existing comparison utilities.
• Vertical : this is a patch identical to the standard patch, but it is used, when a screen is patched, to delete specific/custom actions (SPV) not present in the patch.
•  Specific : this is a patch identical to the standard patch, but it is used, when a screen is patched, to delete specific/custom actions (SPE) not present in the patch.

In the previous versions, a patch of the type SPX is used to delete an SPE action present in a screen. From version 150, these last two types of patch, much more flexible, are used to update the SPE actions (which previously existed) and the SPV action (which are new).

Important note : The patches containing the documentation elements are processed in a particular fashion, described in the corresponding appendix.

• field AW

• Destination type (field TYPEXP)

• Patch (field VOLFIL)

• Direct generation (field FLAGPAT)

If the box is checked, the extraction will be made on the list of selected elements without any other filter being possible. If this box is not checked, the patch file that will be created will only contain a header with the list of elements to be patched. Recall the file in manual patch creation, in order to generate this file and its contents. The question Load object? will then be asked. By responding Yes to this question, the patch header will be loaded in its entirety. It will be possible to manually modify the detailed list of object to patch, to complete it and to finally launch the extraction of patch elements to re-write the patch file with, at the same time, the header file listing the elements and their contents.

• Start date (field DATDEB)

Used to define an interval for the date to be selected for the elements to be patched. The date of the last modification is used for the modified elements and the creation date is used for the newly created elements.

• End date (field DATFIN)

• Minimum version (field VERSION)

This minimum version code is used to avoid the integration of the patch with an inferior version in an application.

• Code (field CODE)

Define the codes for the element types likely to be written in the patch file.

• Object title (field LIBEL)

Title associated to the previous code.

• Number (field NB)

Indicate the number of the element for each type found during the preliminary search for the elements to be patched. The detail can be viewed by right click on the line.

• Y/N (field PATCH)

Final possibility to refuse or to select the objects to patch.