Prerequisite

• To track the execution of asynchronous system activities, it is necessary for the configured asynchronous system activity to be awaiting execution in a workflow in progress.
• The workflow must be under execution for the asynchronous system activity to be enabled according to the flow.

Introduction

Asynchronous system activities execute an operation that pauses the workflow execution. The workflow is paused until a call executes the asynchronous system activity. As soon as the activity is executed and finished, the workflow returns to its usual execution flow.

This article takes into account that, in a workflow in progress, there are asynchronous system activities waiting to be executed while the workflow is paused.

In practice, the asynchronous system activity waits to be executed by the executeSystemActivity SOAP web service. As soon as it is executed, the execution of the workflow can continue.

In the Configuration > General parameters (WF019) menu, it is possible to parameterize the functioning of the system activities:

In the Path to read XML files whenever performing system activity field, indicate the directory in which XML files responsible for updating processes attributes will be located when the system activities are executed.

System activities are not executed by the user, that is, they wait for the customer to call the workflow API to execute them.

XMLs should be in this directory according to the following standards:

process_XXX_YYY.xml

• XXX = process number.
• YYY = system activity ID #.

See the example below:

<Process number="process number">
	<Attributes>
		<Attribute>
			<id>attribute_1_id</id>
			<value>attribute_1_value</value>
		</Attribute>
	<Attribute>
			<id>attribute_2_id</id>
			<value>attribute_2_value</value>
		</Attribute>
	<Attributes>
</Process>