Global Parameters
Overview
Global Parameters is where administrators manage settings that apply to the whole installation rather than to one test case, folder or system under test. A change here affects every user.
The page lists its sections on the left; select one to show its settings on the right. There are two sections:
- AI Agent — which AI provider and model the platform's AI features use, the provider's API key, and optionally a master-data server the AI assistant can look things up on. Enabling AI is a single administrative step: choose a provider you have a contract with, store its key and pick a model — no test needs to change. When you open the model picker, the platform asks the provider for the models your key can actually use, so you choose from what is really available.
- SAP NW RFC SDK — the SAP NetWeaver RFC SDK that RFC connections to SAP backend systems need. The SDK is SAP software that cannot be shipped with the product, so an administrator uploads it once here; it is checked, stored centrally and used by every backend instance. This section is shown only to users allowed to manage system extensions.
API keys and tokens are kept in the secure secret store. After you save one, the page only indicates that a value is stored; it never shows the value again.
Tasks
How to set up the AI provider, key and model
- Select AI Agent in the section list and select Edit. The bar above the settings shows Editing mode.
- Choose the Provider: OpenAI, Google or Anthropic. The key and model fields below switch to the chosen provider.
- Enter the provider's API key, for example in OpenAi API Key.
- Open the model field, for example OpenAi model. The platform loads the models your key can use — you briefly see Loading available models.... Type to filter the list (matches are highlighted) and select a model, or type a model identifier that is not listed.
- Select Save Changes. You see Global parameters saved successfully.. Select Cancel instead to discard your changes.
If neither a typed nor a stored key is available, the model field shows Provide an API key (or keep an existing stored key) to load models.. If the provider rejects the key, an error message says the API key is invalid.
How to replace or remove a stored key or token
- Select Edit. A stored key shows (unchanged); leaving the field alone keeps it.
- To replace it, type the new value.
- To remove it, select Set empty below the field. The stored value is deleted from the secret store when you save.
- Select Save Changes.
Once you start typing in a field that holds a stored value, you must either finish entering a new value or select Set empty — otherwise the field shows Enter a new value or select set empty and you cannot save. The same applies to Master data MCP token.
How to let the AI assistant look up master data
If your organisation runs a master-data service that speaks the Model Context Protocol (MCP), the AI assistant can query it while answering, for example to find a valid material or customer number for a test.
- In the AI Agent section, select Edit.
- Under Master data, enter the server's address in Master data MCP URL. It must start with
https://(orhttp://). - If the server needs authentication, enter its bearer token in Master data MCP token.
- Select Save Changes.
To switch the integration off, clear Master data MCP URL and save.
How to provide the SAP NW RFC SDK
- Download the Linux build of the SAP NW RFC SDK from SAP for the processor architecture your Int4 Suite installation runs on. By default, version 7.50 patch level 12 or later is required.
- Select SAP NW RFC SDK in the section list.
- Select the SDK's ZIP file in the upload area and select Upload & validate.
- Wait for the check to finish. On success the status changes to Installed and the detected version and architecture appear next to it. If the check fails, a message explains which check failed and nothing is stored.
To check a stored SDK again — for example after the platform moved to different hardware — select Re-validate. If the SDK no longer fits, the status changes to Invalid and the reason is shown.
Field reference
AI Agent
| Field | Description |
|---|---|
| Provider | The AI provider the platform uses: OpenAI, Google or Anthropic. Defaults to OpenAI. Only the chosen provider's key and model fields are shown. |
| OpenAi API Key, Google API Key, Anthropic API Key | The API key for the provider. Kept in the secret store; after saving, the field shows (hidden) when not editing. |
| OpenAi model, Google model, Anthropic model | The model the AI features use. Pick from the provider's list or type an identifier. |
| Master data MCP URL | Optional address of a master-data MCP server the AI assistant may query. Leave empty to turn the integration off. |
| Master data MCP token | Optional bearer token for that server. Kept in the secret store like the API keys. |
SAP NW RFC SDK
| Field | Description |
|---|---|
| Status: | Not provided — no SDK yet; RFC connections cannot be used. Installed — a checked SDK is available to all backend instances. Invalid — an SDK is stored but no longer passes the check; the reason is shown below the status. |
| Version and architecture | Shown next to the status: the SDK version reported by the library and the processor architecture it was checked for, for example x86_64. |
| Last validated | When the SDK last passed the check and by whom. |
Tips & edge cases
- Only the selected provider's key is changed. Switching provider leaves the key stored for the previous provider in place; nothing on the page shows that it is still there. To remove it, switch back to that provider, select Set empty and save.
- Models are not checked when you save. You can save any model identifier. A wrong or retired one only causes an error when an AI feature tries to use it. If AI features report that the AI model configuration is not set, check this section first.
- The model list is filtered. The platform shows only models suited to text and agent work, based on their names. A new model with an unusual name may be hidden, or an unsuitable one shown — type the identifier directly if needed. The list is loaded when you open the picker and reused for a few minutes.
- The assistant only reads master data. It uses only the lookups the master-data server marks as read-only. If the server is unreachable or refuses the token, the assistant carries on without master data. When you store a token, the address must start with
https://— the assistant does not send a token over plainhttp://(except to a server on the same machine) and skips the server instead. - Only one SDK at a time. Uploading a new SDK replaces the stored one once it passes the check. A failed upload leaves the previous SDK in place.
- The SDK must match the platform. An SDK checked for a different processor architecture than the one the platform currently runs on is reported as Invalid. Upload the matching build.
- Upload limits. Only ZIP files are accepted, up to 64 MB unless your administrator configured a different limit.
- The SDK section has its own buttons. Upload & validate and Re-validate act immediately; the page's Edit and Save Changes buttons are not needed for this section.
Related features
- Systems under test — RFC connections to SAP backend systems need the SAP NW RFC SDK.
- Test case loader — one of the AI features that uses the provider configured here.
- Roles — grant Global Parameters and System Extension permissions.
Prerequisites & permissions
About permissions. What you can see and do is decided by the roles assigned to your user. Each role bundles permission groups, and each permission group allows activities — Read, Write, Delete, Execute and, for schedules, Change owner — on a kind of record (for example Test Case, Automation Object, System Under Test). A role grants its groups per project scope, so you may be allowed to change records in one project but only view, or not see, those of another.
If a button is disabled, a page says you don't have access, or a list comes back empty, missing permissions are the most likely cause — or, for whole product areas, the installed licence. You can review your own access under Profile → My access; an administrator can change your roles under IAM → Users.
- Global Parameters: Read — open the page.
- Global Parameters: Write — enables Edit and loading the provider's model list.
- System Extension: Read — shows the SAP NW RFC SDK section.
- System Extension: Write — upload and re-validate the SDK. Without it the section shows You do not have permission to manage the SAP NW RFC SDK..
These permissions apply to the whole installation; they are not limited to a project scope. The page itself does not require a specific licence feature; the AI features that use the provider configuration have their own licence requirements.