Description

The Schedules & Calendars Advanced module (English) builds on the Automic User Essentials and provides in-depth coverage of time-based automation in Automic Automation. Participants will learn how to design Schedule objects (JSCH) with Period Duration and Period Turnaround Time, add and configure tasks with Start Times and Start Offsets, and build layered Calendar objects (CALE) from Non-Recurring, Weekly, Monthly, Yearly, Group and Offset Calendar Events. The module covers Calendar conditions on Schedule tasks (Execute if all, no or one condition matches), the runtime status ENDED_INACTIVE and its return codes, Time Zone objects (TZ) for global rollouts including Daylight Saving Time, and script functions such as CALE_LOOK_AHEAD, SYS_LDATE and :SET_CALE. Practical use cases, hands-on exercises and the new Automation Assistant for AI-supported analysis of the last Schedule execution round out the module in Broadcom Automic Automation V26.

Agenda

1. Introduction and Module Scope

• Module objectives, structure, and prerequisites (Automic User Essentials)

• Target audience: developers and object designers in the Process Assembly perspective

• Overview of the objects covered: Schedules (JSCH), Calendars (CALE), Time Zones (TZ)

• Roles: administrator (company-wide Calendars in Client 0) vs. developer (assignment and usage)

2. Schedule Objects (JSCH): The Building Blocks

• What a Schedule is: container for cyclically executed tasks

• Period Duration: the time frame that determines execution regularity

• Period Turnaround Time: period change, reload of tasks, and new RunID

• Association with Calendar objects as a pre-condition for execution

3. Defining a Schedule Object

• Creating the object via Add Object and naming conventions

• Common pages: General, Attributes, Variables, Prompt Sets, Version Management, Documentation

• The Schedule page: task list in the upper panel, Properties pane in the lower panel

• Properties tabs: Calendar, Variables, Prompt Sets, Runtime, and Result per task

4. Attributes Page: Schedule-Specific Settings

• Configuring Period Duration and Period Turnaround Time

• Queue and Queue of Child Tasks, inheritance via *OWN

• Time Zone objects (TZ): local start times for global rollouts

• Effects of Time Zone assignment on Schedules, Workflows, and Jobs

5. Tasks in a Schedule: Time Control

• Adding tasks via drag & drop or Add Row, meaning of the No. column

• Start Time per task and the constraint relative to the Period Turnaround Time

• Start Offset (days) for multi-day periods and the role of the logical date

• Active checkbox and the status ENDED_INACTIVE

• Use Case and Exercise: Schedule with three different time patterns

6. AI-Supported Analysis of Schedule Executions

• Analyze Last Execution: entry points from the Explorer and the object definition page

• The Automation AI Assistant: summary, root-cause analysis, and recommended solutions

• Follow-up questions, multilingual responses, and export as JSON or Markdown

• Availability across AWI wherever a RunID exists (Process Monitoring, Explorer, Agents, Queues)

7. Calendar Objects (CALE): Layered Date Definitions

• Calendar objects as containers for Calendar Events and their reusability

• Defining a Calendar: Calendar page, Calendar Events pane, Add Event, filter function

• Layered composition: from simple Events to complex rules

• Best practices: small, maintainable Calendars and calculation performance

8. Calendar Event Types in Detail

• Non-Recurring: static dates with Maintained from / Maintained until

• Weekly, Monthly, Yearly: pattern-based Events with intervals and limits

• Group: combining Events using Intersect and Subtract

• Offset: Simple and Matching Offset, Target Events, and exception handling

• Standard Calendar Events from Client 0 (UC_MONDAY_FRIDAY, UC_MONTH_*, Q1–Q4 and more)

• Use Case and Exercise: building a layered WORKDAYS Calendar

9. Calendar Conditions, Statuses, and Monitoring

• Setting Calendar conditions on Schedule tasks via the Calendar tab

• The modes Execute if all / no / one condition matches as AND, NOT, and OR logic

• The runtime status ENDED_INACTIVE and its return codes for Calendar-driven and definition-driven skips

• Schedule Monitor: dynamic refresh, verifying skipped tasks, Reset Task

• Use Case and Exercise: workday task with maintenance-day exclusion

Prerequisites

This module builds on the Automic User Essentials. Prior experience with Automic Automation is therefore required — it is not suitable as an entry-level course.

Participants should be comfortable with the following:

• Working in the Process Assembly perspective of the Automic Web Interface (AWI)

• Creating and executing Jobs (JOBS) and Workflows (JOBP), including manual execution

• Basic handling of Automic objects, folder structures, and the Process Monitoring perspective

A basic understanding of the following areas is helpful but not mandatory:

• The Automation Engine scripting language, as covered in Automic User Essentials and, optionally, Automic User Script Essentials

• Business requirements for time-based processing, such as working days, holidays, and maintenance windows

• Working with systems across multiple time zones

What is included?

• Self-Study: 6 months access to a complete, video-based self-learning program including a hands-on practice lab
• Training Materials: Comprehensive course materials as a reference for your daily work with Automic Automation
• Official Tricise Certificate: Recognized proof of your Automic skills upon successful completion of all exams

Who should attend?

The Schedules & Calendars Advanced module is designed for anyone who already works with Broadcom Automic Automation and wants to master time-based process control. Typical participants include:

• Automic Developers and Object Designers: Staff who build and maintain Schedule objects (JSCH), Calendars (CALE), and Calendar conditions
• IT Operations Teams: Professionals who monitor scheduled processes in production and need to interpret statuses correctly
• Automation Engineers: Experienced users who want to map complex business rules – working days, holidays, maintenance windows, and quarter boundaries – into reusable Calendar Events
• Automic Administrators: Those responsible for company-wide Calendars in Client 0 and for time zone handling in global rollouts

Prior Automic knowledge is required – this module builds directly on the Automic User Essentials and is explicitly designed as an advanced module for experienced Automic users.