Technical information:
All profile parameters are normally stored in the Windows registry. There is also the possibility of working with a guixt.ini file instead. This makes sense if you work with different profile variants, or if you want to install GuiXT with a predefined profile on other computers.

You put a file guixt.ini in the SAP GUI folder. The file should contain the statement 

IgnoreRegistry   Yes

since otherwise  values read in Windows registry could overwrite your guixt.ini settings.

Please refer to location of GuiXT profile for additional information.

Here you specify various directories. They can be on your personal PC or on the local network. You can either name the drive by the letter or use the UNC notation.

You can also use system variables to define R/3-System dependant (&database), client dependant (&client) or user dependant (&winuser) directories (i.e.: Directory1 \\Server\GuiXT\scripts\&database). Windows environment variables offer a further possibility. Please use the notation &%[ENVNAME], where ENVNAME is the name of the variable. Example:  C:\&%[GUIXTDIR]\Scripts.

Scripts1,... Scripts4 are the directories that are searched for GuiXT scripts. The search sequence is always Scripts4, then Scripts3, then Scripts2, then Scripts1. You could, for example, have company-wide scripts in Scripts1, and some scripts of your own in Scripts2. Especially if you develop new scripts it makes sense to use your own directory for a certain period of time. You can activate and deactivate the script directories as you go along.

GuiXT Scripts, Images (gif, jpg) and InputScripts can be stored in

• local files, e.g. in C:\GuiXT\Scripts
• central file servers, e.g.  \\p00145\GuiXT\Scripts
• http-servers, e.g. http://www.synactive.com/demo.d.45
• ftp-servers, e.g. ftp://synactive.com/demo.d.45
• SAP Web Repository (R/3 database), e.g. sapwr:z.guixt.demo
  For details please click on  GuiXT scripts in SAP Web Repository

History is the directory used by the InputAssistant. Both the history of input fields and the definition of input sets are stored here.

Shared input sets is also read by the InputAssistant. In this directory you can define Input Sets that are shared by several users.

Domains contains the domain files used for local value help (InputAssistant).

Help views Directory with own help files (Viewer). For each transaction you can create a separate file, e.g. e.transaction.VA01.html for transaction VA01, language key E.
In addition, GuiXT expects an image file  "help.gif" in this folder (format 18x18 pixel. e.g. ). This is the icon that GuiXT displays in the toolbar if there exists a help file for the current transaction. You can use an image command  with  ViewHelp=... to override the help file.
In the SAP logon screen the help file e.transaction.logon.html is searched. Here the language key is set according to the language of the logon screen.

Local script buffer contains the scripts and images that are read from a central file server or from the R/3 database (transaction variants in R/3 4.6). They are automatically synchronized with the server or the R/3 database via a common time stamp. See also File cache parameter below.

User catalog. here you can specify in a text file, different user dependant script directories. Refer to description user catalog for additional information.

• All files from a directory with UNC notation ( e.g. \\p00145\GuiXT\Scripts) are replicated locally
• If you use a drive letter instead, e.g. S:, then no replication takes place, even if the drive letter is assigned to an external directory.
• Before a replicated file is read from the local cache the first time during an R/3 session, the update time on the server is checked. The file is loaded again from the server if necessary.
• All subsequent times the file is read from the cache instead of the server during the same R/3 session.

If you use GuiXT directories on web server (starting with http:// or ftp://) combine with GuiXT file cache for optimal performance

Encryption

All script files and the user catalog are kept in the cache in encrypted format. Images are not encrypted. 

Mark the components that you are using.

Please mark "GuiXT" and no other components if you want to use GuiXT without a license key in R/3 Rel.4 and upwards.

You need a license key if you want to use the Synactive components. Only GuiXT itself, without any other component, requires no license key for R/3 Release 4 and upwards.

Please observe that the license key is specific for your choice of GuiXT components and for your R/3 installation number.

The testkey is issued by Synactive on request for a period of 30 days. It covers all components. Please use the "Order" page in www.synactive.com if you need a testkey. It is then sent to you via email.

A user key is generated when you click on "Activate GuiXT" in the R/3 status screen. This is only necessary when a new license key had been installed.

It is not necessary to change these keys manually.

You can specify the names of R/3 systems for which the GuiXT configuration should be active. The names of the systems can be found in "System" "Status" "Database data" "Name", e.g. D11. You can specify several systems. 

When GuiXT is started, the GuiXT window can be visible, visible and minimized, or hidden. The "hidden" mode is especially useful for users that do not need to change GuiXT scripts or options.

Please note that the profile screen will no longer be available when you activate the "hidden" option. If you start GuiXT again with the parameter "visible", the GuiXT window is shown and you can change the profile options:

guixt.exe visible

Refers to the Tip command in GuiXT scripts. You can specify any SAP standard icon id. It is used in order to indicate that a tip (quickinfo) is available.

This option is only used for debugging purposes. When activated, the system displays a trace in a separate window. The trace can be saved to a file and sent to Synactive for further analysis.

When the Trace option is activated (see above), the system saves the trace to the file which is indicated here, incl. path

Refers to the InputAssistant. If the Update active option is on, the InputAssistant updates the history files for each entry field.

With Show ... you can define which mouse buttons are used to show the input history. The application button on the keyboard can always be used.

The option Display history icon shows the HistoryIcon on the screen where history data have been stored. By pressing the icon the fields on the screen will be filled in with the latest values entered. The default value is "No".

No language key in script file name

If you mark this option GuiXT searches the scripts without a language key, e.g. instead of SAPMF05A.E0100.txt it reads the file SAPMF05A.0100.txt.
In addition, in the screen elements you will now find the technical field name in the first column. See Special Topic Multi language support

If you mark this option you can work with SAP URL in any html display in Internet Explorer.

Controls are automatically built up when processing an InputScript (without activating this option you have to use "Enable Controls" in InputScript). It is generally useful to enable this option.

GuiXT uses notepad as script editor. Instead of Notepad, you can work with a text editor of your choice.

In GuiXT scripts you can inquire about these user options with if Q[Option=xxxx]. For example, you can offer an option display_help. When the user activates this option in the profile, you can display a help text for certain transactions, either as image file using Image or as rtf or html file using View. Each user can then decide individually whether or not to use the help text. 

This special option is currently not included in the standard GuiXT. Please contact Synactive if you are interested.

The purpose of the option is to display a structured layout of the material number. You specify a bitmap of your choice that is automatically shown in the lower part of each material number field.

Example:

User name and password for remote function calls. The password is stored in encrypted format. Please see RFC (Remote Function Call) in GuiXT. You can also perform the RFC in the current client by selecting the option "Script download via current client".

IgnoreRegistry Yes
StartHidden Yes

// Components and license key
Component GuiXT
Component InputAssistant
Key jnfglm

// Scripts and Input Sets from Server
Directory1 \\P00112\GuiXT\Scripts
InputSets \\P00112\GuiXT\Inputsets

// History
HistoryUpdate Yes
History C:\GuiXT\History

// Local value help
Domains \\P00112\GuiXT\Domains

// Cache
Replication Yes
Directory0 C:\GuiXT\Temp

The following parameters are possible only in guixt.ini:

The GuiXT profile entries in the Windows registry are ignored if you specify IgnoreRegistry Yes. This makes sense for SAP GUI 4.6B and upwards, if all parameters should be taken from guixt.ini. In this case, put the guixt.ini file into the SAP GUI directory.

For SAP GUI 4.6B and upwards. If GuiXT is activated in the SAP GUI options, then it is no longer possible to deactivate it.

Please note that this command is not possible in Enjoy mode.
In this case you have to modify the registry entry
HKEY_CURRENT_USER/Software/SAP/SAPGUI Front/SAP Frontend Server/Administration
and add a string variable with the name "DisappearItems" and value "Activate GuiXT". If this variable exists already with some other menu entries, you can add the new entry "Activate GuiXT" at the end separated by ';', e.g. "Generate graphic;Activate GuiXT".
If GuiXT should always be active, you have to set the variable "GuiXT" in
HKEY_CURRENT_USER/Software/SAP/SAPGUI Front/SAP Frontend Server/Customize
to 1.

Maximum time, in seconds,  allowed for file access to "http://...",  "ftp://..." or  "\\server\..." files. Example:

FileAccessTimeout  60

After 1 minute (60 seconds) GuiXT tries to get the file from its cache instead. A log entry is made in GuiXT protocol.

If you do not specify  FileAccessTimeout explicitly, GuiXT takes a default value of 300 = 5 minutes.