Development >  Script dictionary >  Transaction type  

Display all Hide all

This function is used to exploit all the types of transactions. 

Transactions are used to define the properties for certain screen fields (entry, display, invisible). The Transaction generation utility, in the menu Development / Utilities / Dictionary, uses both the transaction type dictionary and the detailed definition of each transaction, to generate the screen and windows from the basic screens and windows. This utility calls the sub-program GENDOS written in the process associated with each transaction.

This information is used by the "Transaction copy" utility in the menu Development / Utilities / Dictionary, This utility calls the sub-program TRTCOP written in the process associated with each transaction.

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

Entry screen

Presentation

This tab is used to record the information related to the transaction generation and copy.

 

Close

 

Fields

The following fields are present on this tab :

Block number 1

The code for a type of transaction is constructed from 1 to 10 alphanumeric characters. The Adonix reserved words are prohibited.

 
  • Description (field ZDES)

 

Generation

  • Active (field ENAFLG)

Select this check box to activate the current record.

The data and setup of disabled records is kept, but they cannot be used on other records (documents, settings, etc.) or for mass processing by recalling the record code.

Authorizations granted for a given function can prohibit the creation of an active record. In this case, this check box is deactivated by default. It can only be modified by an authorized user or using a signature Workflow.

For accounting batch tasks, you cannot change the active status of a recurring task from this function. To do so, you must use the Journal status monitor function (VALPCE).

An activity code is used to:

  • make optional an element in the dictionary if the value associated with the activity code is null.
  • identify the specific/custom elements if they are marked with a code starting with X, Y or Z.
  • size a maximum number of lines when the activity code marks elements from a grid.

In this way, if the activity code is disabled, the marked element will not be useable, and the associated code (if any) will neither be generated nor can be activated.
  • Module (field MODULE)

The module to which the transaction type belongs. The selection of the transaction types from the "Transaction generation" utility is organised by module. The copying of transactions can only take place for active modules.
  • Script (field CODTRT)

The generation of the associated screens and windows must be programmed in the GENDOS sub-program of the process indicated in this field.

The copying of the transactions must be programmed in the TRTCOP sub-program of the process indicated in this field.

This is the object that will use the window generated by the entry transaction.

Block number 3

  • Copy (field COP)

The copy is authorized for this transaction if the "active" and "copy" flags are set.

Transaction

"Entry transaction" object as well as the table associated with it.

 
  • Field code (field FLDCOD)

Field in the table on which a selection range will be applied at the start of the copy utility.

  • Condition (field CND)

Expression used in the copy utility in order to process only certain transactions.

Block number 5

Close

 

Specific Buttons

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

Block number 1

  • field OBJET

 
  • field CLES

 

Block number 2

  • From folder (field DOSORG)

Use this field to define the folder from which the record will be copied. The possible syntaxes are described in the Dedicated appendix.
  • All folders (field TOUDOS)

Use this option to copy the record to all the folders defined in the dictionary (ADOSSIER table of the current solution).
  • To folder (field DOSDES)

Use this field to define the folder to which the record will be copied. The possible syntaxes are described in the Dedicated appendix.

Close

This button is used to copy the transaction type definition to another folder.

Menu Bar

Options / Validation

Error messages

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

Reserved code

The entered process code is a code reserved for Adonix, and it therefore cannot be used.

Non-existent field

The field entered must exist in the table identified above.

 

Tables used

SEEREFERTTO Refer to documentation Implementation