Often, enterprises may have significant investments in proprietary applications that contain workflows. In many situations, users may wish to call InRule from a Workflow Foundation workflow for complex decision management of workflow process instance data. Users may also have a need in other situations to have InRule execute one or more workflows as a result of a rule execution. For more technical information, please refer to the Developer Help file.
A workflow end point can be configured in a rule application to give InRule the ability to call the Execute Workflow action. Entity state from the rule application calling the action can be passed to the workflow from the rule engine.
Note - although the Def classes for the runtime rule application will be available via workflows, Property Setters along with any methods that modify the runtime obj ect will not be permitted.
The following is a description of the Workflow endpoint form:
The name of the workflow endpoint to be referred to from other elements of the rule application.
Select the workflow from an assembly, the name(s) of the available workflows in the assembly will be displayed in the Workflow Type drop-down list.
Select the workflow from an XOML file.
Build the workflow XOML inside the end point.
Custom Workflow Configuration
Allows users to define getting and setting properties or services configuration required for successful execution of the workflow.
Bind Context Object
Allows the binding of the InRule execution context to a named property on the root workflow instance.