Development > Utilities > Patches > Setup templates 

This function is used to define setup templates that can be used in the function Setup copy.
Creating setup templates makes it possible to avoid entering all the setups upon each copy.

Each setup template is associated with one or several data templates describing the data to transfer. Each data template is completed by:

  • a selection formula on the main table of the data template.
  • and a type of transaction used to revalidate the setups if needed.

They are applied upon setup copy.

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

Entry screen

Fields

The following fields are present on this tab :

Block number 1

  • Title (field INTPAT)

Block number 2

  • Module (field MODULE)

Module belonging to the setup. This field is used to specify whether the screen has to be created in the folder database. It is specified when the module linked to the screen is active in the folder.

Table Data models

  • Selection (field EXPSEL)

Close

 

Specific Buttons

The following fields are present on the window opened through this button :

Block number 1

  • field OBJET

 

  • field CLES

 

Block number 2

  • From folder (field DOSORG)

This field is used to define the folder from which the record is going be copied. The possible syntaxes are described in the dedicated appendix.

  • All folders (field TOUDOS)

This option is used to copy the record to all the folders defined in the dictionary (ADOSSIER table from the current solution).

  • To folder (field DOSDES)

This field used to define the folder in which the record is going be copied. The possible syntaxes are described in the dedicated appendix.

Close

This button is used to copy the record definition from or to another folder.

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

The label "Subprog PATCHMOD" does not exist anymore in the SUBXXX processing.

This error means that a transaction revalidation was requested for an object for which no revalidation is necessary. As a matter of fact, this revalidation is triggered by the execution of the PATCHMOD label in the processing associated with the object. Since this label does not exist, there is no need to plan a revalidation.

Tables used

SEEREFERTTO Refer to documentation Implementation