Automatic Patch Creation

• Type of patch (field TYPPTC)

The patch type can take the following values:

• Standard
  This patch can be installed on a folder list which will be given in the integration, in theory, this list contains the supervisor folder. In most cases (including for specific and vertical developments), this is the patch to use. Indeed, the delivery of specific or vertical developments does not rely on the patch type, but on the list of activity codes which are given in the corresponding table.
• Supervisor
  This patch will only be integrated in the supervisor folder. This type is used when the user wants to insert pre-setup elements such as import/export models, automatic journals and Workflow rules that could have been modified in the different folders. In order to avoid erasing the modifications carried out, the supervisor folder only is updated. It is used to have updated setup values in case of the creation of a new folder, and also to update manually by making copies in each folder after having used the existing comparison utilities.
• Specific
  This patch is identical to the standard patch but it is used when a screen is patched to delete the specific actions (SPE) not included in the patch. You must use this value if you need to modify the name of the specific process for a dictionary action on screens. This also applies to screens, objects, reports, formulae and inquiries.
  Please refer to the detailed technical appendix for further information.
• Vertical
  This patch is identical to the standard patch but it is used when a screen is patched to delete the vertical actions (SPV) not included in the patch. You must use this value if you need to modify the name of the vertical script for a dictionary action on screens. This also applies to screens, objects, reports, formulae and inquiries.
  Please refer to the detailed technical appendix for further information.
• Add-on
  This patch is dedicated to the add-ons. It is used to keep the actions on vertical fields (SPV) and the specific actions (SPE).

The patches containing documentation elements are specifically processed: this is 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 makes it possible to avoid integrating the patch in an application from an older version.

• 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.