Working with Process Actions
You can call a process from a decision entity if you map this process to a process action. A process action is an action that affects a process as a whole. You can:
Start a new process instance.
Join a running process instance.
Invoke a user task (requiring a manual (human) decision). For more information about manual decisions, see
webMethods BPM Process Development Help.
Process Action Input and Output
A process action can have inputs and an output. The inputs and output of a process action correspond to the inputs and output of the process the process action is based on. If a process has more than one output, you must specify in the New Action wizard, which output you want to use in the process action.
Specifying Process Action Input Values
You can specify default values for the process action inputs when creating the process action. If you do not specify default input values, you must map a parameter element to the process action input, when using the process action in a decision entity.
For more information about mapping, see
Working with Service Actions, Specifying Service Action Input Values.
Using the Output Value from a Process
You can use the output value from a process if you use the process action that was mapped from this process as:
A decision table condition value.
A decision table assignment result value.
A decision tree condition value.
A decision tree assignment result value.
An event rule assignment result value.
Executing a Process from a Decision Entity
You can execute a process from a decision entity if you use the process action that was mapped from this process as:
A decision table action result.
A decision tree action result.
An event rule action result.
Configuring a Remote Integration Server
By default, process actions are executed on the Integration Server the Rules Engine is installed on and call the Process Engine on the same host. If required, process actions can be executed on another, remote Integration Server which has a Process Engine installed. This remote Integration Server can be configured in two ways:
On
Integration Server Administrator, you can create a remote server alias pointing to the remote
Integration Server. The alias must be named
processruntime, and you must provide the necessary details as described in
webMethods Integration Server Administrator’s Guide,
Adding an Alias for a Remote Integration Server.
On
Microservices Runtime, you can configure the remote
Process Engine using configuration variables templates. For more information on working with these templates, see
Microservices Runtime Guide, Using Configuration Variables Templates with Microservices Runtime. In the template, you must define the remote
Process Engine as follows:
remoteserver.processruntime.alias=processruntime
remoteserver.processruntime.host=host_name
remoteserver.processruntime.port=2345
remoteserver.processruntime.user=administrator_user
remoteserver.processruntime.pass={AES}ThJdujaYE5C1PLAKKS0EbA==