Java classes in process objects
Java classes can be defined for diverse process objects. These implement specific use cases within event sources, event handlers, conditions and actions. The selectable classes are described in the following. The links below provide additional information about Java classes in process objects:
Event sources
The following event classes can be defined when configuring generic event sources:
FileSystemWorkflowEventSource
Source for events in local directories (Create, Modify, Delete).
de.uplanet.lucy.server.workflow.eventsource.FileSystemWorkflowEventSource
UDPWorkflowEventSource
Source for 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
Actions
The following event classes can be defined when configuring generic actions:
FileSystemWorkflowEventSource
Source for events in local 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 in the workflow log.
de.uplanet.lucy.server.workflow.action.LoggerWorkflowAction
CheckPermissionWorkflowAction
Permissions can be checked with this action.
de.uplanet.lucy.server.workflow.action.CheckPermissionWorkflowAction
ThrowExceptionWorkflowAction
Exceptions can be thrown with this action.
de.uplanet.lucy.server.workflow.action.ThrowExceptionWorkflowAction
JdbcExecuteUpdateWorkflowAction
SQL statements, which do not return result sets, can be executed with this action.
de.uplanet.lucy.server.workflow.action.JdbcExecuteUpdateWorkflowAction
StartSchedulerJobWorkflowAction
Jobs from the task scheduler can be started with this action.
de.uplanet.lucy.server.workflow.action.StartSchedulerJobWorkflowAction
WorkflowActivateWorkflowAction
Other workflows can be activated or deactivated with this action.
de.uplanet.lucy.server.workflow.action.WorkflowActivateWorkflowAction
RollbackTransactionWorkflowAction
This action causes the transaction manager to rollback the current transaction.
de.uplanet.lucy.server.workflow.action.RollbackTransactionWorkflowAction
VelocityWorkflowAction
Velocity templates can be generated with this action.
de.uplanet.lucy.server.workflow.action.VelocityWorkflowAction
TouchSessionWorkflowAction
A timeout of the current session can be prevented with this action.
de.uplanet.lucy.server.workflow.action.TouchSessionWorkflowAction
DisableTriggerSubsequentWorkflowEventsWorkflowAction
The triggering of subsequent events can be deactivated with this action.
de.uplanet.lucy.server.workflow.action.DisableTriggerSubsequentWorkflowEventsWorkflowAction
EnableTriggerSubsequentWorkflowEventsWorkflowAction
The triggering of subsequent events can be activated with this action.
de.uplanet.lucy.server.workflow.action.EnableTriggerSubsequentWorkflowEventsWorkflowAction
JMSQueueMessageProducerWorkflowAction
JMS messages can be sent to a queue with this action.
de.uplanet.lucy.server.jms.workflow.action.JMSQueueMessageProducerWorkflowAction
JMSTopicMessageProducerWorkflowAction
JMS messages can be sent to a topic with this action.
de.uplanet.lucy.server.jms.workflow.action.JMSTopicMessageProducerWorkflowAction
UDPSendDatagramWorkflowAction
UDP datagrams can be sent with this action.
de.uplanet.lucy.server.workflow.action.UDPSendDatagramWorkflowAction
GroupTextFeedWorkflowAction
Messages can be created in Intrexx Share groups with this action.
de.uplanet.lucy.server.share.workflow.action.GroupTextFeedWorkflowAction
Conditions
The following event classes can be defined when configuring generic conditions:
ApplicationApiRequestWorkflowCondition
In processes, you can use this condition to distinguish application API requests from others.
It has three possible outputs, which are named "true", "false" and "always" by default. The names can be changed in the dialog. At least one output must be defined. A maximum of three outputs may be defined in the condition.
If there is an Application API Request, the True output is processed first and then the Always output (if applicable).
If there is no Application API Request, the False output is processed first and then the Always output (if applicable). More information about this is available here: Intrexx Application API
CheckPermissionWorkflowCondition
Checks a permission and selects the specified output defined for transitionGrant or transitionDeny based on the result.
Attributes:
-
transitionGrant
-
transitionDeny
-
permissionClass
The permission class does not need to implement the de.uplanet.lucy.security.permission.IIntrexxPermission class. It must derive from java.security.Permission and have one or two constructor string parameters. The first parameter is the name of the permission, the second parameter (optional) defines the actions.
More information about this is available 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 to be checked must be defined 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 if the current user has the permission to create new records in the <DG GUID> data group.
Class:
de.uplanet.lucy.server.workflow.condition.CheckPermissionWorkflowCondition
ListingWorkflowCondition
This condition can be used to specify a sequence for processing the outputs in the form of a list. ListingWorkflowCondition is always true. The names of the outputs must be defined in the attribute "efferentTransitionOrder" separated by spaces. If, for example, "two one three" is entered there, the output "two" is passed through first, then the output "one" and finally the output "three".
Class:
de.uplanet.lucy.server.workflow.condition.ListingWorkflowCondition
RandomWorkflowCondition
This condition is used to randomly select 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, etc.
Class:
de.uplanet.lucy.server.workflow.condition.RandomWorkflowCondition
Event handlers
The following event classes can be defined when configuring generic event handlers:
NoopWorkflowEventHandler
This event handler does not respond to an event.
de.uplanet.lucy.server.workflow.eventhandler.NoopWorkflowEventHandler
JMSWorkflowEventHandler
This event handler processes Java messaging events (JMS).
de.uplanet.lucy.server.jms.workflow.eventhandler.JMSWorkflowEventHandler
UserWorkflowEventHandler
This event handler processes custom events.
de.uplanet.lucy.server.workflow.eventhandler.UserWorkflowEventHandler
TimerJobCompletionWorkflowEventHandler
This event handler processes the end event of 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