Key Terms of Allegro Job Schedule Management

Following are some key terms associated with job schedule management. These are:

• Job Schedule—This is an independent job schedule with one or more jobs. Allegro allows configuration and management of more than one job for each Aria Client.
• Jobs—A job schedule can include one or more jobs. ‘Billing’ is one job that can be part of a job schedule.
• Jobs Sequence—Jobs within a job schedule may have dependencies. Hence, Allegro allows to sequence the jobs in a job sequence configuration or in a job schedule execution (if jobs schedule is manually executed).
• Job Schedule execution—A job schedule can be executed automatically as per the schedule configured. It can also be executed manually for test/demo setup or for a specific job-schedule of a client. A job schedule is created for the specific date and is executed for that date. Users can come back to review the job schedule for any date in the past to review the details.
• Work item—When a job schedule is created/executed, work items are added for each job in a job schedule. For example, if there are 1000 accounts to be billed on a specific day then the job schedule execution process will add 1000 work-items for the billing job. Similarly, work items are created for all jobs in a job schedule. Note that it is possible to not have any work item on a specific day.
• Create Job schedule—This is the process where for a given date, a job schedule sequence is created to be executed. This can be created manually or automatically as part the job schedule configuration
• Process Job Schedule—It is an action that is invoked to execute a specific job schedule for a specific date. This can be automated or scheduled.
• Job Schedule Status—This keeps track of the current state of the job schedule. An Allegro job schedule can have the following state values:
  • PENDING: (Yellow color) A job schedule is created, but execution of the job schedule has not started yet or not completed yet
  • COMPLETED: (Aria Blue color) A job schedule has completed processing
  • ERROR: (Red color) A job schedule has paused with errors. Processing of some work items may have failed.

  A job schedule status is shown with a small, shaded circle in the job schedule execution bar. This is shown in the following screenshot
  

• Job Status—This shows the status of each job in a job schedule execution. An Allegro job can have the following state values:
  • PENDING: (Yellow color) A job is pending to be executed or has not completed yet. 
  • COMPLETED: (Aria Blue color) A job has completed processing
  • ERROR: (Red color) A job has paused with errors. Processing of some work items may have failed.
  A job status is shown as colored text in a job tile, shaded circle in the job schedule execution bar. This is shown in the following screenshot, where the Billing job in the job schedule is shown in yellow text in the activity pane.
  
• Job Statistics—When a job schedule is executed, each job has job statistics for the work items.  Allegro provides 3 levels of drill-down with job statistics for work-items in a job. These are:
  • Total count—Total number of work items for a given job in a job schedule.
  • Processed count—Total number of work items that have completed processing
  • Error Count—Total number of work items that errored.
    • If there is at least one work item in error, then the next level drill-down provides a summary of Error count for each error.
    • The next level of drill-down provides individual work-items that have failed for a specific error-code.
• Manual or Automated job—A job can be configured as a manual job in a job schedule configuration. This allows for human intervention in an,otherwise, automated job schedule. For example, if you want to verify/validate something internal/external before executing the 3rd job in a job-schedule then you can configure the 3rd job as a manual job. This way, a user can manually do the required validation/verification and then restart the automated process of the job sequence. Alternatively, if a job schedule is executed manually, then a specific job can be marked as manual. This allows all the preceding jobs to be executed upon ‘process job schedule’ and then pausing for the manual job to be executed by the user.
• Reprocess Job Schedule—If the job in a job schedule is in an ERRORED state, then a job schedule can be reprocessed starting from jobs with errored work items.
• Reprocess Job—If the job in a job schedule is in an ERRORED state, then the specific job can be reprocessed. The remainder of the job schedule is automatically executed even with reprocessing of a specific job.