...

Introduction

The interceptors allow for project-specific extensions of the yuuvis® Momentum standard process flows. The running process flow can be intervened in redirected by a condition set on the processed object , that has to be specified in the interceptor definition. Whenever the process flow satisfies meets the condition, the project-specific process extension is included for the currently processed object at this position of the process flow. The standard process is resumed subsequently.

Main part(s)

Subsection(s)

for (int i = 0; i < 10; i++)
{
	System.out.println("Hello World " + i);
}

Summary

Thus, the alternative process can entirely replace the standard one from this position on or resume the standard process at a specified position.

Interceptor Configuration

The condition for the intervention of the process flow is defined in the interceptor configuration file \system\interceptorConfiguration.json.

Parameters

The following parameters are available for the interceptor configuration:

Interceptor Types

There are different types of interceptors available that interrupt the process flow at different positions.

Interceptor Configuration Example

The following example configures an interceptor that will be trigger by every update of a content (action code 301). At the take-off point after the REPOSITORY service, the enriched request body is passed to the external endpoint specified by url.

To activate this configuration, the REPOSITORY service needs to be restarted. 

{
	"interceptors": [
		{
			"type": "dms.request.objects.upsert.database-before",
			"predicate": "spel:options['action']==301",
			"url": "http://exampleinterceptorcontentupdate/api/dms/objects/upsert",
			"useDiscovery": true
		}
	]
}

Summary

This article gave an overview of the interceptors in yuuvis® Momentum. If you want to extend the functionality of your system, system hooks also might be an interesting topic for you.

Another Tutorial

...

...

Another Concept Article

...

Another interesting Tutorial

...