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
← Automatically Deleting Old Processes and ChainsParameter Formats →

Editing Process Definitions Safely

Special care needs to be taken when you edit process definitions that have already been submitted and have not yet started or process definitions that have been submitted with a submit frame. This is especially true when you edit the parameter list by adding non-Nullable parameters or by changing a Nullable parameter to non-Nullable. If a process is resubmitted by a submit frame and the parameters are not valid, for example when a non-Nullable parameter contains a null value, the process will be aborted and reach the Modified status, which will require human intervention.

Every time a chain definition is submitted, a branched copy of the chain definition in its current state is made and attached to the process. The user cannot interact with this branched copy. When you edit the master chain definition before the process has reached the Dispatched status, the new chain definition will be used. However, when a chain definition is used several times in a submitted chain definition, the new chain definition will only be used when the first occurrence of the chain process has not reached Dispatched at modification time. This has been implemented to allow chain definitions to remain consistent.

See Also

  • Creating Process Definitions
  • Using Chain Definitions
← Automatically Deleting Old Processes and ChainsParameter Formats →
  • See Also
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 |