Page History

...

• Order ID
  • The Order ID is unique across a JobScheduler environment.
  • Orders are triggers that start a job chain. Therefore it might not be a bad idea to add the name of the respective occurrence - either time based or event based - to the identification of the order.
  • Recommendations
    • Add the order occurrence to the Order ID.It is somewhat redundant to add a reference to the job chain to an order as the order file name is anyway created from the Order ID and the Job Chain Name.
    • Examples
      • daily_morning
      • end_of_day_processing, end_of_week_processing, end_of_month_processing
• Order Title
  • Recommendations
    • The same recommendation applies as for the Job Title.

Schedules

• Schedule Name
  • A schedule specifies the run time for one or multiple orders or jobs and therefore is time based but not specific for a task that should be executed.
  • Recommendations
    • Add the occcurrence to the Schedule Name.
    • Examples
      • end_of_month (not: weekly_cleanup)

Locks

• Lock Name
  • The nature of locks is to be unique across a JobScheduler environment. A lock has a name and a path that is created from its location. 
  • Should you have multiple locks with the same name in different folders then this is technically viable, however, it reduces the visibility and applicability when it comes to analyzing logs.
  • Recommendations
    • The usefulness of a lock is to restrict access to a resource. Therefore we recommend to use the resourece name as the lock name.
    • Examples
      • accounting_tables for a lock that restricts access to the same tables in a database.

...