OP06 - What are Automic Objects?

Almost everything in Automic is an object. In this tutorial, you will learn what an object is, how to create objects and what you need to be aware of while making them. You will also learn the difference between an object and an execution and what is meant by “object uses“. Lastly, the video shows you the most common method of activating time-driven workflows in Automic.

ℹ️ This Automic Tutorial is part of PEM Automic and was published on October 30th 2024.

📋 Content: 1 video

🕒 Duration: 10 minutes

A comprehensive guide to Automic objects

If you work with Automic, you may have noticed that almost everything is an object. In this article, we'll take you through the different types of Automic objects, how to create them, how to use them and how to implement them.

What are Automic objects?

In Automic Workload Automation, objects are the basis for all automation processes. Everything from jobs and workflows to agents and clients is considered to be an object. There are four main categories:

  • Executable objects: These include jobs and workflows that execute specific automation tasks.

  • Active objects: Can be changed automatically, such as calendars or VARAs.

  • Passive objects: These cannot be changed during runtime, such as PromptSets, which act as input forms.

  • System objects: These are responsible for managing Automic, such as agents and clients.

Each object type has a short name in capital letters, which you will use regularly within the Automic Web Interface (AWI).

Creating Automic objects

Objects are created in the Process Assembly perspective. There are many templates, the selection of which can vary depending on your authorisations and admin settings.

There are certain rules for naming objects: Names must be unique across clients and only contain certain characters. A consistent naming convention is important in order to manage user rights effectively.

Use of Automic objects

The strength of Automic lies in the reusability of the objects. For example, you can select an agent object to determine on which end system a job is executed, or use a login object to determine the user.

Workflows in Automic can contain other workflows, which allows you to create complex automation structures.

Difference between objects and executions

One aspect of Automic that is often misunderstood is the difference between objects and executions. Objects are static definitions in Process Assembly, while executions are traced in Process Monitoring. Each execution has a unique RunID that is unrepeatable throughout the system.

By the way: “executions“ that are still active are called “tasks“.

Schedule objects play an important role in the automation of executions by activating objects on a time-controlled basis.

Automic learning with PEM Automic

Would you like to learn more about Automic without having to travel across the country for workshops? At PEM, you decide when and how you want to continue your education! In interactive courses, tutorials and videos, you will learn everything you need to know about Automic. And we are always there for you via comment function or email.

Does that sound interesting? Then get started today with PEM, Automic Training 2.0 and year-round Automic support!

Buy Now
Try it for free

FAQ about Automic Training on PEM

PEM is the most innovative and fastest growing Automic learning platform. It offers PEM members a comprehensive range of online training courses that can be accessed 24/7 and from anywhere. The platform includes dozens of videos and interactive courses and is aimed at beginners and professionals alike.