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

Identifies the code of the setup model.

  • Description (field INTPAT)

Only the title is displayed.

Block number 2

  • Module (field MODULE)

Module to which the setup belongs.

This activity code is used to mark a development or setup considered as optional (it is then activated or deactivated based on the value of the indicator linked with the activity code).It is also used to identify specific additions or to group under the same significant code a set of elements of the dictionary that need to be simultaneously activated to enable a function of the software to be implemented.

An activity code starting with X, Y or Z is considered to be specific.

Table Data models

The data model selected here is used to define the data that will be extracted to be entered or copied in the patch file.

SEEINFO There may be several identical data models within the same setup model.

  • Selection (field EXPSEL)

A selection formula is entered here, which will be applied on the main table defined in the data model.

This formula can include the variable [L]CODLEG, which is the legislation code entered when launching the copy.

When the setup data describe the entry transactions, the mere copy of setup data is not enough: It is also necessary that the corresponding transactions are revalidated (i.e.. that the code - processing, screens, windows according to the cases - must be regenerated.) It is triggered when entering here the code of the corresponding setup object.

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 makes it possible to define the folder from which the record is going be copied. The possible syntaxes are described in the dedicated annex.

  • All Folders (field TOUDOS)

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

  • To Folder (field DOSDES)

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

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