Context menus provide additional functions specific to the context of the current transaction. Right-clicking activates the context menu. The functions available are independent

• of the nature of the transaction (display or input transaction),
• of the nature of the field (display or input field),
• of the type of panel (framepanel or XML panel),
• of the position of the cursor, and
• of the authorization status of the registered user.

Right-clicking the mouse with the pointer hovering over a field, regardless of whether the field is for display or input, makes this field the current field.

Below are descriptions of all possible context menu functions. Whether a function is actually available or not depends on the relevant status and/or editing mode of the transaction in which the context menu is opened.

Shows the help text for the current field. This function has the same effect as pressing the F1 key.

Activates the Editor to amend helptexts for the current field. This function is only available to users with the appropriate authorization, i.e. users authorized to run the transaction Adding a Helptext.

Shows the transaction, panel and field details in the status line.

Shows the documentation relevant to the current transaction.

Shows the full range of the application documentation.

Shows the Windows dialog box for printing the panel.

Saves the panel content as an image file (with the extension .“dsp”) in the “dump” directory of the installation. The path and the automatically generated file name are displayed in the status line.

This function is only available to users defined as 'Designer'.

Shows details of producer and production. The most important detail is the Build version, displayed in the bottom right corner. The number shown clearly identifies the installation.

Enables information to be stored for support purposes while running the transaction. A check mark in front of the entry indicates that one of the subsequent functions has been activated. The function activated is also indicated by a check mark. It is possible to activate combinations of functions.

This function is only available to users defined as 'Designer'.

These functions should only be activated according to the instructions from the Support Team, because the application performance can be considerably affected.

In a Thin Client installation on a Unix server, the generated output files are stored in the Server Session Logfile located in the 'tmp' directory of the installation. The file name has the following structure:

'td2s<yyyy><mm><dd><hh><mi><ss><hs><tds>_<pid>.log'

- Example: td2s20020624171303357_7299.log

In a Fat Client installation, the results of the activated functions are displayed in the Debug window of TradeDesign.

Info
Writes information on the start of the transaction in the log file.

Communication
Writes information about the communication between client and server in the log file.

Profiling
Writes information for the analysis transaction GENPRF (Profile Analyzer) in the log file.

SQL Query
Writes all SQL commands in the log file.

SQL Data
Writes the return values (data found) for all SQL statements in the log file.

Rules
Writes the use of all event, default and check rules carried out in the log file.

User Rules
Writes the use of each sub and function carried out in the log file.

Built-in
Writes all internal TradeDesign functions carried out in the log file.

Basexec
Writes all TD Basic commands carried out in the log file.

Flow
Writes the assessment and mapping of the flow of all modules running within the transaction in the log file.

Application
Writes the debug information that the application issues if the tdContextDEBUGLEVEL_APPLICATION has been flagged.

Generates a display file (screen shot) of all panels relating to the current transaction in the DISPLAY\MANDSP\<UIL> directory of the environment. The file name is made up as follows:

<name of transaction>.DSP

<UIL> = languagecode (i.e. EN or DE)
<name of transaction> = 6-letter mnemo of the transaction.

This display file can be viewed by clicking 'Display file'.

When the documentation is generated, these transaction panels are used instead of panels that might be automatically generated.

Supplementary function to the 'Save Image for Documentation' section above.

The current panel is appended/attached to the end of the display file.

In particular, this is used when transaction panels are not always displayed at the same time and therefore cannot all be saved at the same time. This for example applies to panels that only become visible once a special button has been clicked.

The texts below can be edited on the “Text” panel of the “Maintaining System Parameters” (DBITDP) transaction.

Reverses the last change made to the current field.

Removes the selected content and transfers it to the Clipboard.

Copies the selected content and transfers it to the Clipboard.

Inserts content temporarily stored in the Clipboard in the current field.

Deletes the selected content.

Selects the complete contents of the current field.

When displaying XML documents in the Viewer, several more functions - described below - become available, in addition to those mentioned above. It does not matter which transaction type (business transaction, static data transaction, ect.) was used to activate the Viewer.

Adjusts the display of the document so that the full width can be viewed without having to scroll horizontally to see a whole line of text.

Adjusts the display of the document so that the full height can be viewed without having to scroll vertically to see a whole page.

Adjusts the display of the document so that all pages can be viewed at once.

Enlarges the display of the document to twice its original size.

Enlarges the display of the document to one and a quarter times its original size.

Displays the actual size of the document in the Viewer window.

Reduces the display of the document to three quarters of its original size.

Reduces the display of the document to half its original size.

Displays the Windows dialog box used to print the document.