What You Will Learn

This guide shows you how to run and manage a Command without executing a Workflow.

For the following chapters the Workflow Executor app has to be in the ‚expert mode‘. How to toggle this mode can be found here.

1. Where to find the Commands?

All available Commands will be displayed on the left side of the Workflow Executor app which can be seen here:

Single Command Runner Tree View

Commands from predefined repositories will be automatically fetched by the app.

Make sure to activate expert-mode under Options > Configuration. More about that can be found here.

2. Run a Command

The following chapter will show how a command can be run in the app.

2.1. Selecting a Command

Commands are ordered by the group and subgroups which they are assigned to.
Via a dropdown menu each group can be iterated through.
Once a command has been found, click the command to select it.

Open Command

2.2. Provide values for the Command

Once a command has been selected you will be prompted with a view which allows you to insert values which your command will need to be run.

Single Command Runner Command Selected View
1 Commands can have different versions, via this drop down menu the version of the command can be selected.
2 Input fields where values for the command can be defined. Inputs with a red border are mandatory, the command cannot be run without them!
3 Here you can determine the naming of the output variables of the command.

The selected command ‚Merge Collections‘ needs two list of items, so we provide them:

Single Command Runner Values Provided

2.3. Running the Command

Once all the values are provided for the command we run it. This can be done via a toolbar in the upper right of the app.

Single Cmd Run Toolbar
1 Reload: Is active after command termination; Used to reload the command and clearing all text fields to accept new inputs.
2 Run: Is active after command selection and termination; Used to run a command with the specified parameters.
3 Abort: Is always active; Used to stop a running command or close the parameter editing window.

Now to run the command we click the run button in the toolbar:

Start Command

While the command is run, the ‚Workspace Datastore‘ tab will be filled with the output variables provided by the command, the values of these variables can be reused by other commands later on.

Single Command Runner Output Var In Workspace Datastore

2.4. Using predefined Values

While you can choose to use a custom value for every input. You can also choose from a list of predefined values like an empty value or previously written values. In order to do this simply click on the fx button.


For example, clicking Use Empty Value results in locking the input field and supplies an empty value to PAK. You can also choose to select a value which was previously written to the datastore.


Selecting a value from the datastore copies the stored value while still keeping the field editable. Inputs for optional fields are set to use their standard value by default. In order to input your own value, simply click the fx button and select Use Custom Value.

SCR FX Default

Sonatype Nexus

PAK features connectors and commands for Sonatype Nexus. This means the software can directly interact with Nexus repositories for storing and managing artifacts. Through these connectors, PAK can automate tasks like uploading binaries or retrieving dependencies, ensuring efficient artifact management within Nexus.


PAK has connectors and commands for Jenkins. This allows the software to directly communicate with Jenkins servers, enabling the automation of CI/CD (Continuous Integration/Continuous Deployment) tasks. Through these connectors, PAK can trigger builds, fetch build statuses, or manage job configurations, streamlining the CI/CD processes within Jenkins.

Git Hub

PAK possesses connectors and commands for GitHub. This means the software can interface directly with GitHub repositories, facilitating actions like code pushes, pull requests, or issue tracking. Through these connectors, PAK can automate various GitHub operations, enhancing code collaboration and repository management.

Atlassian Confluence

PAK is equipped with connectors and commands for Atlassian Confluence. This enables the software to directly interact with Confluence spaces and pages. Through these connectors, PAK can automate actions such as creating, updating, or retrieving documentation, ensuring efficient content management and collaboration within Confluence.


PAK features connectors and commands for Codebeamer. This allows the software to seamlessly integrate with Codebeamer’s ALM (Application Lifecycle Management) platform. Through these connectors, PAK can automate tasks like issue tracking, test management, or requirements tracing, enhancing the coordination and management of software development processes.

JFrog Artifactory

PAK has connectors and commands for JFrog Artifactory. This means the software can directly interface with Artifactory repositories, enabling actions like artifact storage, retrieval, and management. Through these connectors, PAK can automate tasks such as deploying artifacts or managing repository configurations, streamlining the integration and management of binary artifacts within Artifactory.

Amazon Web Services (AWS)

PAK has connectors and commands for Amazon Web Services (AWS). This means the software possesses specialized interfaces to directly interact with AWS services and execute actions on the AWS platform. Through these connectors, PAK can automate AWS-specific commands, such as launching EC2 instances, managing S3 buckets, or configuring Lambda functions. This allows for efficient integration, management, and automation of AWS resources and services directly from PAK.

Atlassian Jira

PAK features integration tools and capabilities for Atlassian Jira. These tools allow for a direct connection to Jira and the execution of specific actions. Using these integration tools, PAK can automate Jira actions such as adding comments or changing ticket priorities, ensuring seamless handling and coordination of Jira processes.


PAK has connectors and commands for Git. This means it has interfaces to directly communicate with Git and execute actions. Through these connectors, the software can automate Git commands such as retrieving changes or creating branches, enabling efficient integration and management of Git tasks.

Generic Human Tasks

PAK offers you a standard set of commands which require creative input from the user. Enables you to start with automating your workflows, that still need abit of human input.

Generic Commands

PAK offers a standard set of commands giving you the first steps to automate your workflows.

Nexus Maven Command Pool

Nexus is an artifact repository manager for storing binaries, libraries, and artifacts, supporting formats like Maven. Maven, a software project management tool, is based on the Project Object Model (POM) and allows developers to consistently define projects and dependencies. Our Command Pool offers commands for interactions between Maven and Nexus, such as artifact uploads or dependency retrieval.

Artifactory Maven Command Pool

Artifactory allows developers to store, retrieve, and manage binary files and artifacts, providing a
central source for all binaries used in a development process. Apache Maven is a software project
management and comprehension tool that enables developers to consistently describe a project and
its dependencies. Our Command Pool offers a collection of commands used to facilitate interactions
between Maven and Artifactory, such as uploading artifacts or retrieving dependencies.

Open API Command Interpreter

The OpenApi Command Interpreter allows you the automatic parsing of commands from an OpenApi defintion. No additional code needs to be written anymore, just add the address to the definition and our framework does the rest!

Kotlin Command Interpreter

The Kotlin Command Interpreter allows you the parsing and execution of commands within a Kotlin environment to automate various tasks or processes.

Bpmn Interpreter

Workflows come in many shapes and forms. The BPMN (Business Process Model and Notation) Interpreter enables the parsing of worklows defined in the BPMN format into the PAK intern model.

Human Task Interpreter

The Human Task Interpreter allows you the parsing and running of commands within a HTML and Javascript environment. Use this to build commands which need the creative input of a workflow user!

Java Command Interpreter

The Java Command Interpreter allows you the parsing and execution of commands within a Java
environment to automate various tasks or processes.


The heart of the PAK-Framework. Contains the means to run workflows with the PAK engine, but also the possibility to enrich the frameworks interfaces with your own implementations and solutions.

RocksDB Persistence

Data that is generated by a workflow run needs to be saved for short or longer terms. Our solution to the Persistence Interface of the PAK-Framework is to use the high-performance, key-value based RocksDB developed by Facebook.

PAK online

PAK Online is a web based application and provides an Open API based REST API. It enables you to upload workflows and run them periodically or on REST demand.

Command Line App

Run tasks and workflows on the console or as part of a CI/CD Pipeline with our Command Line Interface.

Workflow Editor

With our specially developed editor, a wide variety of workflows can be easily modeled in the wide known BPMN process format.

Workflow Executor

The Workflow Executor is the application to run your workflows. It features a multilingual UI and easy managment of your favorite workflows.


We offer a community website where you can exchange ideas and support each other. For our Pro packages we also offer full support via email.