This function is used to create a patch file that integrates all those elements created or modified between two dates. These elements can be marked by an activity code.

The elements that should be patched can be defined in two different ways:

  • either by directly generating the file (the number of elements available by type are listed),
  • or by generating a patch file that only contains the list of the elements. In that case, this file will be read in the pach function in order to load the complete list of the elements concerned and modify this list, if need be.

Screen management

Preliminary selection window

On entering the function, a first window makes it possible to define the search criteria of the elements to be patched.

Criteria

Start date (field DATDEB1)

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 DATFIN1)
User (field USR)

Block number 3

Script to run (field TRT)

If a process is entered here, it will be added, in the form of an execution request (EXE) in the patch file to be created. Thus, on the integration of the patch, the process in question will be executed in each folder to be processed.

Grid Objects

Code (field CODE1)

Defines the different element types likely to be integrated in the patch file.
Object title (field LIBEL1)

Title associated with the previous code.
Y/N (field PATCH1)

The search for the number of objects to patch is made uniquely for elements where this field is set to Yes.

Table number 2

Language (field LANGUE)

This field is used to define the language that should be patched. If it is entered, only the texts in this language will be extracted on the generation of the patch.

Table number 3

Activity code (field CODACT)

If an activity code is entered, it is used as a filter on the search for elements to be patched.

Detail
Yes to all the rest

When faced with an entry grid with multiple choices and a Yes/No answer on each line, this function makes it possible to answer Yes to all the lines starting from the current line.
No to all the rest

When faced with an entry grid with multiple choices and a Yes/No answer on each line, this function makes it possible to answer No to all the lines starting from the current line.
Standard Rerouting Action
Standard Rerouting Action
Validation window

Once the first window is entered and validated, the selection processing is run (a progress window displays the selection in process), and after a few moments, a second window opens. This window displays the information on the result of the search and some information can be added to directly create the patch file.

Type of patch

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.

File

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.

Block number 3

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.

Grid Objects

Code (field CODE)

Define the codes for the element types likely to be written in the patch file.
Object title (field LIBEL)

Title associated with 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.

Functions accessible by right click on the

Detail

Used to view the detailed list of those elements patched on the line (only the number is specified).

Yes to all the rest

When faced with an entry grid with multiple choices and a Yes/No answer on each line, this function makes it possible to answer Yes to all the lines starting from the current line.

No to all the rest

When faced with an entry grid with multiple choices and a Yes/No answer on each line, this function makes it possible to answer No to all the lines starting from the current line.

List of possible elements in automatic patch

All those elements likely to be patched can be patched in an automatic patch. The grid below provides a list of hese elements:

Code

Meaning

Name

Rank

AAA

Lines arising from a setup model

Specific format, see corresponding section

100

ABA

Batch recurring task

Recurring task code

46

ABF

BI Fact table

Table code

54

ABG

Group of tasks

Group code

47

ABI

BI Dimension

Dimension code

55

ABM

BI Datamart

Datamart code

56

ABO

Report Business Objects

Report code

58

ABT

Batch task

Task code

45

ABV

BI Synchronization rule

Code of the rule

57

ACL

Control table

Table code

18

ACN

Inquiry

Inquiry code

36

ACS

Access codes

Dealt with in the form of a condition (CODACS='value')

14

ACT

Action

Action code

16

ACV

Definition of an activity code

Activity code

1

ADC

Description of a script (dictionary)

Script name

9

ADF

Documentation links

Type ~ Element code

50

ADI

Contents of a miscellaneous table

Table number

24

ADO

Functional help (all paragraphs)

Type ~ Help code

49

ADP

Parameter (both its definition and value if they exist at the general level)

Parameter code

32

Sales Management

Setup of a miscellaneous table

Table number

23

ADX

Script file (only in its compiled form)

Script file name

11

ADZ

Field help

Help code

48

AEN

Import/export sequencing

Dealt with in the form of a condition (CODE='value')

35

AFC

Function

Function code

17

AGB

Global variable

Variable name

20

AHH

BI Hierarchy

Hierarchy code

59

AHI

Purge formulae

Formula code

7

AII

BI predefined condition

Condition code

60

ALH

Query tool

Code for the request

51

ALQ

SQL query tool

Code of the SQL request

52

ALT

Graphical query tool

Code for the request

53

AMK

Screen

Screen code

28

AML

Local menu

Local menu number

2

ANG

Navigation

Navigation code

10

ANM

Definition of a counter:

Code of the counter

15

ANT

Widget Netvibes parameters

Object code for widget

65

AOB

Definition of an object

Code of the object

30

AOE

Import/export template

Template code

34

AOP

Object properties

Code of the object

31

APH

Setup models

Template code

100

APR

Graphical process

Process code

63

ARP

Report definition in the dictionary

Report code

29

ASL

Conditioned style

Dealt with in the form of a condition (COD='value')

19

ASU

Description of a sub-program in the dictionary

Name of the sub-program

21

ASY

Presentation style

Style code

61

ATB

Table definition (the contents are not transferred, the update of the structure is made without losing common data)

Table code

25

ATN

Transactions

Transaction code

8

ATY

Data type

Code of the type

22

AUR

URL

URL code

27

AVW

View

Code of the view

26

AWA

Workflow rule

Code of the Workflow rule

43

AWE

Web service

Publication name

64

AWI

Window definition

Code of the window

33

AWM

Workflow data model

Model code

41

AWR

Workflow assignment rule

Code of the assignment rule

42

AWW

Setup of the Workflow workbench

Code of the workbench

44

BIA

BIAR objects

Object code

4

ELT

Element of the client interface (xsl, image, miscellaneous file)

File path

3

ETA

Crystal Reports report (file with .rpt extension)

Report name

13

EXE

Request to run a script

Script name

6

GAU

Automatic journals

Document code

40

PS1

Statistical trigger

Trigger code

37

PS2

Statistical code

Statistical code

38

TAB

Complete structure and contents of a table (excluding its 'dictionary' definition).
The global patch of a table is a 'flat' save of this file: as a .dat file when saving a table in the save directory (SVG). Not all the links to this table are taken into account and especially the translatable texts contained in the ATEXTRA table.

Table code

39

TFO

Formulae table

Formula code

62

TRT

Source of a script (the script will be compiled on patch installation)

Script name

12

TXT

Text file (in the TXT directory)

Text name

5

Table abbreviation

Partial contents of the table

Extraction condition (expressed in the form of a Where clause)

100

Error messages

The only error messages are the generic ones.

Tables used

SEEREFERTTO Refer to documentation Implementation