Redwood Documentation

Product Documentation

 

›Processes and Chains

RunMyJobsProcess and Chain Definitions

Process Definitions

  • Creating Process Definitions
  • Setting Chain Definition and Chain Definition Properties
  • Integrating Redwood Server with Web Services
  • Redwood Definition Types
  • Maintenance Process Definitions
  • Template Process Definitions
  • Top Level Process Definition
  • Submit Form Editor
  • Default System Process Definitions

Processes and Chains

  • Advanced Chain Diagram Quick Reference
  • Chain Diagram Quick Reference
  • Chain Runtime Viewer Quick Reference
  • Advanced Chain Definition Editor Quick Reference
  • Advanced Chain Runtime Viewer Quick Reference
  • Advanced Diagram Quick Reference
  • Parameter Validation using Constraints
  • Processes Waiting on Events
  • Setting the Scheduling Behavior on the Control Tab
  • Setting the Retention Period for Processes
  • Runtime Limits
  • Setting Process Definition Options
  • Defining Parameters
  • Constraint Definitions
  • Constraint Class
  • Raising Events
  • Processes with Locks
  • Reaction Processes
  • Restart Behavior on the Process Status Tab
  • Searching Files
  • Setting the Name and Editing the Process Definition Source
  • Customizing Processes with Specific Actions
  • Using Table Parameters
  • Automatically Deleting Old Processes and Chains
  • Editing Process Definitions Safely
  • Parameter Formats

Chain Definitions

  • Using Chain Definitions
  • Creating Chain Definitions
  • Steps
  • Chain Processes
  • Creating Chain Definitions with Sequential Processes
  • Creating Chain Definitions with Parameter Handling
  • Creating Chain Definitions with Parallel Chain Processes
  • Creating Chain Definitions with Chain Processes Dependencies
  • Creating Chain Definitions for Multiple SAP Systems
  • Precondition Functions

Restart Behavior

  • Controlling Global and Partition Restart Behavior
← Parameter Validation using ConstraintsSetting the Scheduling Behavior on the Control Tab →

Processes Waiting on Events

Processes can wait for one or more events, this forms the basis of event-driven process scheduling. You specify as many events as you need to be waited on. The processes based upon those process definitions cannot be executed before the events upon which they are dependent are raised. When a process is created for a process definition, it inherits all the events to be raised, and must wait for those.

A process waits only once for a specific event. So if the event was raised but the process did not start (for example, due to the closing of a queue), the process does not wait again for an event from the same event definition the next time the queue is released.

When a process waits for an event it gets the EventWait status.

Automatically started processes

An event-waiting process can be auto-started when the event is raised. Make sure that all parameters (if any) have default parameter values and a default queue is set. You can set auto-start to:

  • Never - A process will never be submitted.
  • Always - A process will always be submitted.
  • Only one - Only submit a process when there is no process of the same process definition in a pre-running state, a process definition that has not yet reached status Running.
note

An event-waiting process must first be scheduled before it gets the EventWait status.

Restricting When to Wait for an Event

Events can have restrictions applied, for example, only be used on Sundays; in this case processes ignore the event on other days.

Clearing Events

The process that is triggered by the event should clear the event, so that another event-waiter (created later) will wait for another occurrence of the event.

Values

TabFieldDescriptionDefault Value
Wait EventsEvent DefinitionThe event definition the process will be waiting for.

Wait EventsAuto SubmitShould the process start automatically each time this event is raised?Never.
Wait EventsClears EventShould the start of the process clear the event?No.
Wait EventsClear Comment

Wait EventsOnly Waited For When > Time WindowTime window to use for restricting when the event is used, either open or closed in the specified time zone or the default time zone, when omitted.

Wait EventsOnly Waited For When > ExpressionBoolean REL expression (returning either true or false)

Examples

Attach an Event on Weekends

  1. Attach an event to wait on Weekends.
  2. Choose "Definitions > Processes".
  3. On the Wait Events tab, choose Add.
  4. Select an event definition, fill Workdays in the Time Window field, select System_Week_WorkDays, select closed in the is field.
  5. Choose Save to save the chain definition.

Attach an Event when other Events are Raised

  1. Attach an event to be raised by process 1 of the first step for status Error only if any of two other events are raised.
  2. Choose "Definitions > Chains".
  3. Choose process 1 of the first step.
  4. Choose Raise Events, choose and select an event definition.
  5. In the When expression field, fill =Event.isEventRaised('Mypartition.MyEvent1') || Event.isEventRaised('Mypartition.MyEvent2')
  6. Choose Save and Close to save the chain definition and close the dialog.

JobChain JobDefinition ProcessDefinition

← Parameter Validation using ConstraintsSetting the Scheduling Behavior on the Control Tab →
  • Automatically started processes
  • Restricting When to Wait for an Event
  • Clearing Events
  • Values
  • Examples
    • Attach an Event on Weekends
    • Attach an Event when other Events are Raised
Docs
Getting StartedInstallationFinance InstallationConcepts
TroubleshootingArchiving
Learn and Connect
Support Portal
BlogEventsResources
ISO/ IEC 27001 Information Security Management
Automate to be human

2023 All Rights Reserved |

Terms of Service | Policies | Cookies | Glossary | Third-party Software | Contact | Copyright | Impressum |