K2 Workflow and Task - Complete an asynchronous server event

Use the K2 Workflow and Task - Complete an asynchronous server event action A tool for building the processes, logic, and direction within workflows. Actions are the steps the workflow performs to complete a process. to complete an asynchronous server event. Asynchronous server events wait for a call-back from the external system to finish the server event. The user account used by the external system must be granted server event permissions for it to be allowed to complete the server event. An example of an asynchronous server event is using the Wait for external system option in a workflow.

For more information about the K2 Workflow and Task connector, go to K2 Workflow and Task.

Before you begin: 

Jump to:

Configure the K2 Workflow and Task - Complete an asynchronous server event action

  1. Add the action to the workflow and open the action configuration panel. For more information, see Add an action to the workflow.

  2. Select a Connection. If you do not have a connection, see Add a connection.

  1. Type the Serial number of the asynchronous server event.

K2 Workflow and Task - Complete an asynchronous server event action fields and settings

Field

Description

Variable types

Connection Credentials and other settings that enables workflows to communicate with external systems, services, or applications. It's required to pass data between the workflow and the indicated service, which could be a cloud service, business application, or content store.

The K2 Workflow and Task connection to use to complete an asynchronous server event.

To refresh the available connections, click .

(n/a)
Serial number The unique identifier for the K2 Workflow and Task asynchronous server event that you want to complete.
You can use the Wait for external system option in a K2 workflow to retrieve the serial number. 
Text, Decimal, Integer, Boolean, DateTime, Collection