Suche

1. What You Will Learn

After finishing this tutorial you will be able to use pathing conditions correctly and to properly incorporate them
into your PAK workflows in the Editor.

2. Prerequisites

To complete this guide you need:

This HowTo does not contain a detailed introduction to the editor.
Click here
to learn everything about the PAK workflow Editor.

3. What are pathing conditions

After an exclusive or inclusive gateway, there is usually more than one possible path to take.
It usually depends on a condition, which of the paths should be used during execution.
These conditions will be added to the outgoing edges of the gateway.

For Example: We want to ask the user a simple question, but depending on their answer we have to take different paths of execution.
In our example we just want to write the users answer into the Datastore.

750
Figure 1. Example workflow
Any condition added to an edge, that is not rooted at an exclusive or inclusive gateway will be ignored!
For Exclusive and Inclusive Gateways an empty condition has an actual meaning. When one path from that type of gateway has an empty condition then the path is considered the default path. When no other conditions are met the path with no condition, the default, will be chosen instead.
If a gateway is encountered and you have a case, which is not part of any condition of the outgoing paths, the workflow will fail.
For example, you have a path that will test if a number is greater than 5, and a path where you test if it is less than 5.
If the number is equal to 5, the workflow will fail with the exception, that no follow-up node is defined for that gateway.
Therefore, to ensure a fail-safe workflow, you will have to make sure, to cover all possible scenarios of a gateway.

4. Conditions

The expressions are parsed and processed from left to right.

4.1. Basic Logic

Allowed Operations Description

==

equals

!=

not equals

>

greater than

>=

greater or equals

<

less than

<=

less or equals

&&

AND (i.e. (true && false) ⇒ false)

||

OR (i.e. (true || false) ⇒ true)

!

negation operator, not

?

exists-check for Optionals
Logical operations should be inside of braces.

4.2. Interpolation

Interpolation can be used in conditions.
The optional expression („?“) is not compatible with interpolation.
Multiple interpolations are usable in strings while a single interpolation can be used like a variable.

Syntax Description

${myAmazingField}

to pass the value of the field myAmazingField

${Person.age}

to pass the value of the property age from the field Person

${java(variable)}

to pass the value of a java based system property

${env(variable)}

to pass the value of a environment variable of your system
You can find a more detailed guide on interpolation here!

4.3. Examples

Example Meaning

${keyOrOutputField} == someValue

the value behind the interpolation is equal to someValue

(a < 5 ) && !b

a is less than 5 AND NOT b

a==5

a is equal to 5

(!(x <= 6) && (x > 9)) || (y!=8)

(NOT (x less or equal 6) AND (x greater than 9)) OR (y NOT Equals 8)

someString == x

x has the value of someString

y != anotherString

y has not the value anotherString

a? || b?

is a available OR is b available

a? && a == „someString“

is a available AND then check if it is equal to the value of „someString“

5. In the BPMN Editor

Using the introduction example, we will build a simple workflow that will, depending on the users input, write one or the other value into the Datastore.

  1. Add an exclusive or inclusive gateway from the workflow controls to your workflow.
    Continue by adding the rest of the workflow with multiple paths from the gateways.

    250
    Figure 2. gateways with conditions on outgoing paths
    500
    Figure 3. workflow before adding conditions

  2. After the paths from the exclusive/inclusive gateway were added you can assign conditions to them.
    By clicking on the corresponding edge, a condition can be added to the corresponding Properties field.
    The Name-Property enables the user to label edges.
    If Name remains empty, the edges will have no description, and you have to click on the edge to see its condition.

    300
    Figure 4. Properties of the edge
    500
    Figure 5. Finished workflow

  3. This is what the execution and the datastore would look like, if the user chose „yes“.

A guide, on how to run a workflow in the executor can be found here!
750
Figure 6. Execution of the example workflow

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.

Jenkins

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.

Codebeamer

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.

Git

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.

Core

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.

Support

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.