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
← Runtime LimitsDefining Parameters →

Setting Process Definition Options

FieldDescriptionDefault Value
Default Output FormatThe format of the output files when the extension can not be mappedText
Default Log FormatThe format of the log files when the extension can not be mappedText
Overview FormatFormatting used in the overview diagrams. This allows you to distinguish processes based on parameter values, especially useful for duplicates of the SAP_AbapRun process definition. You cannot change the overview format of built-in process definitions. You may insert parameter values using the syntax ${parameters.<name>}, such as ${parameters.VARIANT}

TemplateTemplate process definitions are used to create new process definitions, they cannot be submitted or part of a chain definition.false
MaintenanceMaintenance process definitions are low profile process definitions; processes of these are not to be displayed in the default filters.false
Top LevelTop level process definitions are listed in the submit wizard as processes you can submit. Process definitions that should only be submitted as part of a chain definition should not have this set to truetrue
Critical ProcessCritical Process processes are shown in the scorecard under Critical Processes.

Reaction Process TypeCheckReaction Process Type processes can be called from a process server when a process server check fails. AnyReaction Definition Type processes can be called from a process server as well as other objects. Promote Further PusherReaction Definition Type processes can be called on System_Import_Archive processes to promote the attached CAR file to another systemPush AcceptorReaction Process Type processes can be called when an inbound CAR file arrives to validate it PusherReaction Process Type processes can be called by a Remote System when you promote objects to it[None]
Evaluate Runtime Parameters With UserThe subject to use for evaluating runtime parameter expressionsprocess definition owner

Format

Processes can potentially generate output files. These can be log files that are guaranteed to contain log records in standard format, text files containing freely formatted information or error messages, or more complex files such as PDF or HTML files. Which files can be generated is dependent on the type of process that is executed.

The system will set the Format of the files created by the process.

Reaction Process Type

Reaction processes are processes that can react to a particular type of event. Unlike process definitions and wait events, reaction process definitions have a set of parameters that are filled automatically by the caller; there is no need to write REL to fill the parameters. Reaction processes have the following parameters in common:

  • SourceObject - Name of the object that called the reaction process
  • SourceObjectUniqueId - UniqueId of the object that called the reaction process
  • SourceObjectType - Object type that called the reaction process
  • Address - destination/recipient address
  • Data - a free form expression

See Reaction Process Definitions for more information.

Runtime Parameter Evaluation

When runtime parameters are evaluated, a session is created as the owner for evaluation, by default. You can set this to the process definition owner in which case the process definition owner needs permissions to all objects used by the call in the expression you specified, not the process owner.

JobChain JobDefinition ProcessDefinition

← Runtime LimitsDefining Parameters →
  • Format
  • Reaction Process Type
  • Runtime Parameter Evaluation
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 |