close

Filter

loading table of contents...

Workflow Manual / Version 2110

Table Of Contents

4.4.2 Predefined FinalAction Classes

These are the predefined action classes which can be executed after a process completed or was aborted. They are used with the element <FinalAction> and by specifying the name of the action class as the class attribute.

ArchiveProcessFinalAction

Use this action to archive data of the process after it completed or was aborted and before it gets destroyed in the Workflow Server. If the RegisterPendingProcess action was used before to add the process to some users' lists of pending processes, then these users can view the completed process in Studio's Control Room.

The action can store the process data to a MongoDB database. To configure it, set the properties mongodb.client-uri, mongodb.prefix and usecaplist in the Workflow Server. See Section 6.1, “Configuration Reference” for a description of these properties.

The Workflow Server will retry the execution of this action in case of communication problems with the MongoDB database. The exception classes that trigger a retry are defined in the configuration property workflow.server.archive.retry-exception, which is described in Table 3.22, “Workflow Server Properties” in Deployment Manual.

Attribute

Type

Default

Description

maxProcessesPerUser

NMTOKEN

(unlimited)

The maximum number of processes to show in the list of finished processes in Studio's Control Room. This attribute should be set to the same value for all ArchiveProcessFinalAction and ArchiveProcess actions in different workflow definitions, because all processes are stored in the same list.

Table 4.32. Attributes of the ArchiveProcessFinalAction


Example:

<FinalAction class="ArchiveProcessFinalAction"
             maxProcessesPerUser="100"/>

        

Example 4.22. Example of the ArchiveProcessFinalAction


Search Results

Table Of Contents
warning

Your Internet Explorer is no longer supported.

Please use Mozilla Firefox, Google Chrome, or Microsoft Edge.