Java Classes in Process Objects

Java classes can be defined for various process objects to implement specific use cases within event sources, event handlers, conditions, and actions. The available classes are described below. The following links provide additional helpful information about Java classes in process objects:

• Intrexx Java API Documentation

• Intrexx Java API Documentation (Download as a ZIP file)

Event Sources

When configuring generic event sources, the following event classes can be defined:

FileSystemWorkflowEventSource

Source for events in directories on the local file system (Create, Modify, Delete).

            de.uplanet.lucy.server.workflow.eventsource.FileSystemWorkflowEventSource
        

UDPWorkflowEventSource

Source of UDP events.

            de.uplanet.lucy.server.workflow.eventsource.UDPWorkflowEventSource
        

JMSQueueWorkflowEventSource

Source for JMS queue events.

            de.uplanet.lucy.server.jms.workflow.eventsource.JMSQueueWorkflowEventSource
        

JMSTopicWorkflowEventSource

Source for JMS topic events.

            de.uplanet.lucy.server.jms.workflow.eventsource.JMSTopicWorkflowEventSource
        

Promotions

When configuring generic actions, the following event classes can be defined:

FileSystemWorkflowEventSource

Source for events in file system directories (Create, Modify, Delete).

            de.uplanet.lucy.server.workflow.eventsource.FileSystemWorkflowEventSource
        

NoopWorkflowAction

This action has no effect.

            de.uplanet.lucy.server.workflow.action.NoopWorkflowAction
        

LoggerWorkflowAction

This action writes entries to the workflow log.

            de.uplanet.lucy.server.workflow.action.LoggerWorkflowAction
        

CheckPermissionWorkflowAction

This action allows you to check permissions.

            de.uplanet.lucy.server.workflow.action.CheckPermissionWorkflowAction
        

ThrowExceptionWorkflowAction

This operation may throw exceptions.

            de.uplanet.lucy.server.workflow.action.ThrowExceptionWorkflowAction
        

JdbcExecuteUpdateWorkflowAction

This action allows you to execute SQL statements that do not return a result set.

            de.uplanet.lucy.server.workflow.action.JdbcExecuteUpdateWorkflowAction
        

StartSchedulerJobWorkflowAction

This action can be used to start jobs in the task scheduler.

            de.uplanet.lucy.server.workflow.action.StartSchedulerJobWorkflowAction
        

WorkflowActivateWorkflowAction

This action can be used to enable or disable other workflows.

            de.uplanet.lucy.server.workflow.action.WorkflowActivateWorkflowAction
        

RollbackTransactionWorkflowAction

This action causes the transaction manager to roll back the current transaction.

            de.uplanet.lucy.server.workflow.action.RollbackTransactionWorkflowAction
        

VelocityWorkflowAction

This action can be used to generate text from Velocity templates.

            de.uplanet.lucy.server.workflow.action.VelocityWorkflowAction
        

TouchSessionWorkflowAction

This action can prevent the current session from timing out.

            de.uplanet.lucy.server.workflow.action.TouchSessionWorkflowAction
        

DisableTriggerSubsequentWorkflowEventsWorkflowAction

This action can be used to disable the triggering of follow-up events.

            de.uplanet.lucy.server.workflow.action.DisableTriggerSubsequentWorkflowEventsWorkflowAction
        

EnableTriggerSubsequentWorkflowEventsWorkflowAction

This action can be used to enable the triggering of follow-up events.

            de.uplanet.lucy.server.workflow.action.EnableTriggerSubsequentWorkflowEventsWorkflowAction
        

JMSQueueMessageProducerWorkflowAction

This action allows you to send JMS messages to a queue.

            de.uplanet.lucy.server.jms.workflow.action.JMSQueueMessageProducerWorkflowAction
        

JMSTopicMessageProducerWorkflowAction

This action allows JMS messages to be sent to a topic.

            de.uplanet.lucy.server.jms.workflow.action.JMSTopicMessageProducerWorkflowAction
        

UDPSendDatagramWorkflowAction

This action allows you to send UDP datagrams.

            de.uplanet.lucy.server.workflow.action.UDPSendDatagramWorkflowAction
        

GroupTextFeedWorkflowAction

This action allows you to create text messages in Intrexx Share groups.

            de.uplanet.lucy.server.share.workflow.action.GroupTextFeedWorkflowAction
        

Starting with Intrexx version 12.0.0

SQSCreateStandardQueueWorkflowAction

Creating standard queues.

            de.uplanet.lucy.server.share.workflow.action.SQSCreateStandardQueueWorkflowAction
        

SSQSCreateFifoQueueWorkflowAction

Creating FIFO queues.

            de.uplanet.lucy.server.share.workflow.action.SQSCreateFifoQueueWorkflowAction
        

SQSDeleteQueueWorkflowAction

Deleting queues.

            de.uplanet.lucy.server.share.workflow.action.SQSDeleteQueueWorkflowAction
        

Terms and Conditions

When configuring generic conditions, the following event classes can be defined:

ApplicationAPIRequestWorkflowCondition

You can use this condition to distinguish Application API requests from other types of requests in processes.

It has three possible outputs, which are named "true," "false," and "always" by default. The names can be changed in the dialog box. At least one output must be defined. A maximum of three outputs may be defined for the condition.

If an Application API request is received, the True output is processed first, followed by the Always output (if either is available).

If there is no Application API request, the False output is processed first, followed by the Always output (if either is present). For more information, see here: Intrexx Application API.

CheckPermissionWorkflowCondition

Checks a right and, based on the result, selects the specified outcome defined for `transitionGrant` or `transitionDeny`, as appropriate.

Attributes:

• transitionGrant

• transitionDeny

• permissionClass
  The Permission class does not have to implement the de.uplanet.lucy.security.permission.IIntrexxPermission class. It must extend java.security.Permission and have one or two constructor parameters of type "String". The first parameter is the name of the permission; the second (optional) parameter is the actions.
  For more information, click here:
  https://help.intrexx.com/apidocs/jdk21/api/java.base/java/security/Permission.html
  https://docs.intrexx.com/intrexx/version/steady/api/workflow/jdk/de/uplanet/lucy/security/permission/IIntrexxPermission.html

• permissionActions
  The name of the specific permission being checked must be entered here.

• permissionName
  The GUID of the object to which the request refers must be specified here.

Example:

            permissionClass: de.uplanet.lucy.security.permission.DatagroupPermission
        permissionActions: create
        permissionName: <DG-GUID>
        

This configuration checks whether the current user has permission to create new records in the data group <DG-GUID>.

Class:

            de.uplanet.lucy.server.workflow.condition.CheckPermissionWorkflowCondition
        

Listing Workflow Condition

This condition can be used to specify an order—in the form of a list—for processing the outputs. ListingWorkflowCondition is always true. The names of the outputs must be specified in the "efferentTransitionOrder" attribute, separated by spaces. For example, if "two one three" is entered there, the system will first cycle through output "two," then output "one," and finally output "three."

Class:

            de.uplanet.lucy.server.workflow.condition.ListingWorkflowCondition
        

RandomWorkflowCondition

This condition randomly selects either the true or false output. The probability of this happening is controlled by the specified weights:

• 1:1 corresponds to p = q = 0.5

• 3:1 corresponds to p = 0.25 and q = 0.75, and so on.

Class:

            de.uplanet.lucy.server.workflow.condition.RandomWorkflowCondition
        

Starting with Intrexx version 12.0.0

TransactedAcquireLockWorkflowCondition

Sets a lock across the cluster using the lock service and releases it at the end of the transaction. The condition has two outcomes: success and failure.

Class:

                de.uplanet.lucy.server.workflow.condition.TransactedAcquireLockWorkflowCondition
            

Event Handler

When configuring generic event handlers, the following event classes can be defined:

NoopWorkflowEventHandler

This event handler does not respond to any events.

            de.uplanet.lucy.server.workflow.eventhandler.NoopWorkflowEventHandler
        

JMSWorkflowEventHandler

This event handler processes Java Messaging Service (JMS) events.

            de.uplanet.lucy.server.jms.workflow.eventhandler.JMSWorkflowEventHandler
        

UserWorkflowEventHandler

This event handler processes user-defined events.

            de.uplanet.lucy.server.workflow.eventhandler.UserWorkflowEventHandler
        

TimerJobCompletionWorkflowEventHandler

This event handler processes the end event for timers.

            de.uplanet.lucy.server.workflow.eventhandler.TimerJobCompletionWorkflowEventHandler
        

TimerJobSchedulingWorkflowEventHandler

This event handler processes the start event of timers.

            de.uplanet.lucy.server.workflow.eventhandler.TimerJobSchedulingWorkflowEventHandler
        

SessionLoginWorkflowEventHandler

This event handler processes login events.

            de.uplanet.lucy.server.workflow.eventhandler.SessionLoginWorkflowEventHandler
        

UDPDatagramWorkflowEventHandler

This event handler processes UDP events.

            de.uplanet.lucy.server.workflow.eventhandler.UDPDatagramWorkflowEventHandler
        

FileSystemWorkflowEventHandler

This event handler processes file system events.

            de.uplanet.lucy.server.workflow.eventhandler.FileSystemWorkflowEventHandler
        

BadMailWorkflowEventHandler

This event handler processes the event when an email cannot be processed and is moved to the BadMail folder.

            de.uplanet.lucy.server.mailservice.workflow.eventhandler.BadMailWorkflowEventHandler