Redwood Documentation

Product Documentation

 

›Calendaring

RunMyJobsMonitoring Processes

Processes

  • Monitoring and Managing Processes
  • Advanced Process Search
  • Filtering Processes
  • Processes Monitor Diagrams
  • Redwood Server Process Processing
  • Process States
  • Available Columns in the Processes Monitor
  • Chains Monitor Filter Columns
  • Process Forecasting
  • Integrating Redwood Server into Third-Party Applications with PermaLink

Operator Messages

  • Operator Messages Monitor
  • Creating Operator Messages
  • Interacting with Operator Messages
  • Creating Advanced Operator Message Reply Expressions
  • Receiving Operator Messages on your Desktop

Events

  • Monitoring Events
  • Filtering Events
  • Event Filter Columns

Environment

  • Monitoring System Performance
  • Monitoring Dashboard
  • Housekeeping Dashboard
  • Monitoring SAP Systems
  • Creating Custom Monitor Checks

Submitting Processes

  • Submitting Processes and Chains
  • Submitting a Process or Chain
  • Scheduling with Times and Dates
  • Rescheduling Processes Automatically
  • Using Recurrences

Calendaring

  • Using Time Windows
  • Shifting Times and Days with Time Windows
  • Configuration Data for Time Windows
  • Using Time Windows in Processes
  • Defining Advanced Execution Times with Period Functions
  • Managing Recurrences
  • Creating Submit Frames
  • Frequently Asked Questions About Submit Frames
  • Using Submit Frames in Processes
  • Time Zones
← Creating Submit FramesUsing Submit Frames in Processes →

Frequently Asked Questions About Submit Frames

Consider the following submit frame:

Element: every minute (no time window)

Element: every hour (no time window)

Q ) What happens? Is a process using this running every minute or every hour? Does the order matter?

A ) the process would run every minute the process would be submitted for the first occurrence from the set of [1 minute or 1 hour]. As the set returned by [1 minute] is a true superset of the set returned by [1 hour], the 1 hour element can be ignored.

Consider the following submit frame:

Element: every minute (no time window)

Element: every hour during time window System_Week_Friday

Q ) What happens on Friday? Is a process using this running every minute or every hour on Friday?

A ) the process would run every minute again the [1 minute] set also contains every occurrence of [1 hour on Fridays]. The 1 hour on Fridays element can be ignored.

Consider the following submit frame:

Element: every minute (no time window)

Element: every hour during time window System_Week_Friday

Element: every 30 minutes (no time window)

Q ) What happens on Tuesday? Is a process using this running every minute or every 30 minutes?

A ) The process would run every minute the [1 minute] set contains ever occurrence of [1 hour on Fridays] and [30 minutes]. Both these elements can be ignored

Consider the following submit frame:

Element: every minute during time window System_Week_Friday

Element: every hour during time window System_Week_WorkDays

Element: every 30 minutes (no time window)

Q ) What happens on Friday? Is a process using this running every minute, every hour or every 30 minutes?

Q ) What happens on Tuesday? Is a process using this running every hour or every 30 minutes?

A ) On Fridays the process would run every minute. The every hour element is made obsolete by the 30 minute element. But on Fridays, the process would run every minute.

← Creating Submit FramesUsing Submit Frames in Processes →
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 |