Skip to main content

Commands - Execute customized events to external system

How to trigger a customized event to e.g. ERP system

S
Written by Sandra
Updated over 3 months ago

Overview

The Commands feature allows users to manually trigger actions in external systems directly from TOPS CT. This functionality enables on-demand document creation and targeted updates to integration partners.

Use case example

A shipper needs to create customs documents for an international shipment. Instead of waiting for automated processes, they can:

  1. Select the relevant transport order in TOPS CT

  2. Access the Commands menu via right-click

  3. Choose "GenerateCustomsDocuments" command

  4. Confirm the action to trigger immediate document creation

This allows the customer to proactively generate necessary documentation when needed, rather than waiting for scheduled system updates

Configuration

Master Data Setup

  • Commands are configured in the Master Data section

  • Division form includes a multi-line text field for command configuration

  • Only alpha-numeric characters, dashes, and underscores are permitted (no whitespaces)

  • Commands can be deleted, making them unavailable for future selection

Using Commands

Accessing Commands

  • Select one or multiple orders (SO, MO, TO)

  • Right-click to open the context menu

  • Navigate to the "Commands" option

  • Select desired command from the list

Using commands

Command Execution

  • A confirmation dialog will appear: "Do you want to trigger the command?"

  • Click confirm to execute the command

Supported Order Types

Commands can be executed on the following order types:

  • SO (Service Orders)

  • MO (Main Orders)

  • TO (Transport Orders)

  • PO (Purchase Orders)

System Behavior

Event Handling

  • Each command generates a "Command" event

  • Events are processed independently with undetermined execution order

  • Full event details are available via integration

History Tracking

The system maintains a history of command execution including:

  • Timestamp

  • User who executed the command

  • Command name in event text

Note: Access to command execution is controlled by AOR (Area of Responsibility) permissions.

AOR commands

Did this answer your question?