Each of the job object management functions: Financial asset, Expense, Leasing contract is made up of several standard tabs that are used to enter information.

For each of these functions, it is possible to set up one or more transactions, each of these transaction being identified by a code.
The setup consists in personalizing, on the one hand, the list of tabs displayed in the function and on the other hand, the fields contained in each of the visible tabs.

The list of transactions set up in this way for a given function will be displayed for the user in the Transaction selection window displayed automatically on opening the function.

Prerequisite

SEEREFERTTO Refer to documentation Implementation

Screen management

The personalization of a transaction is carried out in three stages:

 The first stage is carried out in the displayed screen. It consists in defining the general transaction characters, such as the job object, the code and the title of the transaction and potentially its access code.
 
After having selected the job object, the Screen tab is loaded with the list of tabs defined for the standard transaction associated to this object. The Visible flag, available at the level of each of these tabs, can be modified and is used to define whether the tab should appear or not in the transaction.

Before going to to the second stage, it is necessary to confirm the transaction creation via the button.
 The second stage is carried out after clicking on the button . This stage consists in personalizing the fields in the tabs that were declared as Visible during the first stage.

  The last step is initialized by the button  . It is used to trigger the automatic generation of the transaction that's been set up.

Header

The header is used to define the general transaction characteristics :

- specifying thejob object,
- by entering a code and a title for the transaction,
- specifying whether the transaction is active ournot,
- defining, if necessary, access criteria to the function, specifying:
--> A group of companies.
--> An access code used to restrict the access to the transaction to a single user or a group of users. When an access code is entered, the transaction can only be accessed by the users whose function profile gives them the appropriate access rights.
--> A legislation code.

Tab Screens

This tab displays, in the form of a table, the list of tabs (referenced by a screen code) defined for the standard transaction associated to the object selected in the header.
The Visible flag is used to specify for each of the tabs, whether they must appear or not in the transaction.

Validation

This button is used to trigger the confirmation processing for the current transaction. This processing consists in generating the masks as well as the specific window associated to the transaction.

  • The masks are generated under the following name:
    WE + Name of the object (First 2 characters) + Transaction code + Number of the tab in the reference window.
  • The window is generated under the following name:
    W + Name of the reference window + Transaction code.

Window

This button is used to view the set up transaction.