Skip to main content

Int4 Suite 4 — User Guide

Welcome to the user guide for Int4 Suite 4, the enterprise testing platform for SAP and other integrations.

New here? Start with Int4 Suite at a glance — a short orientation to what the product does, the core concepts everything is built from, and where to go next.

This guide is organised around the main areas of the product. Pick a section below to jump straight to the screens you use most often.

  • What's new — the highlights of Int4 Suite Version 4.
  • Dashboard — the home page: installation-wide totals, the last day's activity, which systems under test can be reached, and your own runs and crawls.

Test Cases​

Design, organise, and edit the test cases that drive every test run.

  • Cockpit — the combined folder tree and test case workspace, including the detail editor for opening and editing a single test case.
  • Process tests — chain test cases into end-to-end business processes, see them as a map, and complete the chain with suggested steps.
  • All test cases — the flat list of every test case you can see, with multi-select execution, migration, and export.
  • Test case analysis — explore large test case sets by their business dimensions and drill down to the test cases behind a value.
  • Test case loader — bulk-import test cases from a ZIP archive, pairing request and response payloads automatically.
  • AI assistant — the chat panel that reads and changes records for you, with confirmation before every change.
  • Crawlers — configurations that discover messages on a platform and auto-create test cases.
  • Crawler runs — the history of crawler executions and what each one created.
  • Trace schedulers — configurations that keep SAP Cloud Integration iFlow traces enabled.
  • Trace scheduler runs — the history of trace-scheduler executions.

Test Runs​

Track what the platform has executed and inspect the results.

  • All test runs — the live list of every test run, with status, duration, re-run, and links into the run detail.
  • Test run details — the result of one run and of each test case in it, including the payload comparison views.
  • Performance report — processing times measured across repeated runs.
  • Scheduled test runs — recurring test runs that fire on a schedule, with their status and next-run times.

API Explorer​

  • API Explorer — build, send and check API requests, keep their history, and promote a request to a test case.

Messenger​

Stand in for partner systems that are missing from your test landscape.

  • Virtualization objects — model how a stand-in system receives messages and answers them.
  • Instances — run a virtualization object in an environment, and review or release the messages it handles.
  • External channels — inbound endpoints that outside callers use to reach Messenger.

Configuration​

Set up the artefacts that test cases reference — connected systems, automation objects, scripts, and the value-mapping data used to compare payloads.

  • Automation objects — definitions of the integration flows or interfaces that test cases exercise.
  • Business dimensions — the catalogue of business values, such as order or material numbers, read from payloads.
  • Business objects — customer-defined, scripted actions that drive connector-based test steps.
  • Mapping objects — tables that translate values, such as plant or company codes, between the system groups of your landscape.
  • DB rulesets — definitions of which SAP backend tables and columns to read for database comparisons.
  • Scripts — reusable scripts that test cases and automation objects can call.
  • Data store — buckets of values that scripts write and read across test runs.
  • Global sequences — reusable number ranges that generate unique values in test data.
  • Global parameters — tenant-wide settings, including the AI Agent provider and key.
  • Content packages — import and export packaged content such as business dimension catalogues.
  • Systems under test — the connected SAP and HTTP systems that test cases talk to.
  • System landscape — the matrix view that maps systems under test into groups and assigns value mappings.
  • Value mappings (SAP PO) — the SAP-PO-specific tables that translate values between systems during comparisons.
  • PI/PO objects — list and remove objects left behind on an SAP PI/PO system.

IAM​

Manage who can sign in to Int4 Suite 4 and what each person is allowed to do.

  • Users — list, create, and edit users; assign roles.
  • Roles — define which permissions a role grants.
  • Permission groups — bundle permissions for reuse across roles.
  • Project scopes — define the projects that can be assigned to users and to data.
  • Licenses — upload and review the licence files that enable optional features.

Your account​

  • Profile — your account, the application version, your licence and your effective access.
  • Settings — theme, data grid density, and the about and legal information.

How this guide is organised​

Each page in this guide has the same shape:

  • Overview — what the screen is for, in user terms.
  • Tasks — step-by-step instructions for the most common things you'd do on the screen.
  • Field reference — what every column, field, and filter on the screen means.
  • Tips & edge cases — non-obvious behaviour, licence-gated features, and things that catch new users out.
  • Prerequisites & permissions — what your user needs in order to use the screen.

Button names, column headings, and other UI labels in this guide are kept in sync with the application itself, so the words you read here match exactly what you see on screen.

Was this page helpful?Send a quick note to the documentation team.
0 / 2000 characters