Hello, how can we help you?

Recent Searches: Configure validity rule - Using the Word Online add-in - Using AI resources in the editor - Importing and exporting files

Tracking the execution of asynchronous system activities

 

Prerequisites

  • 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, an asynchronous system activity waits until it is 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. For example: /var/sesuite/xml/ or C:\sesuite\xml\.

System activities are not executed by the user; that is, they stay waiting for the client to call the workflow API to execute them.

XMLs should be in this directory in the following standard:

process_XXX_YYY.xml

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

See the example below:


<Process number="process number">
	<Attributes>
		<Attribute>
			<id>attribute_1_identifier</id>
			<value>attribute_1_value</value>
		</Attribute>
		<Attribute>
			<id>attribute_2_identifier</id>
			<value>attribute_2_value</value>
		</Attribute>
	</Attributes>
</Process>


To learn more about the method that executes the asynchronous system activities of the workflow and how to start it, click here.

For further details on the web service, see the documentation available in the Integration guide or in the WSDL itself.

 

 

Conclusion

As soon as the asynchronous system activity is executed via web service, the workflow will have its course resumed automatically. To track the progress of the instance, use the Workflow (WF022) menu.


Was this article helpful?