Solution Corner #26: Event Objects (Recording)
Webinar: Successfully using Event Objects (EVNT) in Automic
Meta Description: EVNT objects can be used to elegantly map many use cases in Automic. Discover typical scenarios, common pitfalls, and proven tricks in this webinar!About this Webinar
With EVNT (Event) objects, many use cases can be elegantly mapped in Automic. In the webinar, we will show you typical use cases, common pitfalls – and proven tricks for safely avoiding them. Whether you are waiting for a specific data constellation, monitoring file systems, or evaluating system messages – we will provide you with the necessary tools to optimally integrate events into your workflows.The 10 Key Takeaways on Event Objects
- Event Definition: Events are objects that regularly check a condition and trigger an automation when it is met. They cycle through states like "Sleeping", "Checking", and "Active".
- Event Types: There are various types of events such as Time, File, Database, and Console events. Time and File events are the most commonly used, while Console events are considered more of a special use case.
- Functionality & Status Logic: Events check conditions at defined intervals and typically end with statuses like "ENDED_OK", "ENDED_TIMEOUT", or "ENDED_CANCEL". Choosing the right status is important for monitoring and interpretation.
- Frequency & Interval Control: Events can be executed once or repeatedly. The "Until first match" setting is especially important for typical "wait until condition is met" scenarios. Intervals can be set in minutes or at a specific time once a day, although a Schedule object is generally recommended for the latter.
- Console Event Specifics: Console events react directly to system messages without checking intervals. They are suitable for real-time triggers, such as log or system events, but have limited availability.
- Database Event Usage: Database events allow checks via SQL, VARA objects, or static values. A typical use case is triggering workflows based on database content, for example, a number of entries greater than 0.
- Concurrency Control (Wait/Active Checks): To avoid multiple executions, the "WAIT" parameter can be used with ACTIVATE_UC_OBJECT. This keeps the event active and prevents multiple triggers.
- File Events & Validation: File events check file system states such as file count or modifications. Advanced checks like "File Size Stable" help ensure that files have been fully transferred.
- Best Practices & Control: It is recommended to use workflows to control events as well as to stop them specifically via scripts, for example with CANCEL_UC_OBJECT. This allows events to be terminated cleanly and managed easily.
- Script Elements for Events: We highlight useful functions such as GET_CONSOLE, GET_EVENT_INFO, GET_FILESYSTEM, and GET_WIN_EVENT in conjunction with the different event types.
Learn Automic with PEM!
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 more! 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!
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.
To meet different needs, PEM offers different types of content: courses, tutorials, learning paths, labs and tools.
- In the courses and tutorials you will learn everything about Automic in entertaining and interactive videos.
- The learning paths offer comprehensive training on a specific Automic topic. For example, the 11-part operator learning path is suitable for beginners. Are you already an Automic expert? Then you will definitely learn something with the database SQL learning path.
- Labs are automated environments that are available at the touch of a button and where what has been learned can be put into practice.
- Tools with appropriate instructions are regularly provided on PEM . This allows Automic processes to be automated and simplified even further.
In our library, you’ll find all content items currently available on PEM. And every week, we add more items to learn Automic.
PEM Labs are comprehensive, pre-configured Automic environments designed to provide users with a hands-on and immersive experience. These labs offer instant access to multiple Automic versions, allowing users to experiment with functionality and explore new features effortlessly. Available on demand and at no additional cost for members, PEM Labs eliminate the need for complex setups or extra expenses. Whether you’re a beginner or an experienced professional, they serve as realistic sandbox environments ideal for learning and experimenting with Automic.
Labs are provisioned on demand with a single click and are automatically deleted after 24 hours.
There are two different deployment-variants for the Labs:
- Labs for Operator and Designer
These provide access to a dedicated Automic Client via the Automic Web Interface (AWI). - Labs for Admins
These labs include OS-level access through a browser, enabling members to perform all administrative tasks, including those at the operating system level.
PEM Labs are available in three formats:
- Test Labs
These labs are empty Automic clients or systems that members can use for their experiments. - Course Labs
These labs include one or more scenarios where users are tasked with solving practical exercises, similar to classroom training sessions. - Story Labs
Story Labs are like Course Labs but incorporate a storyline to make the experience more engaging and entertaining. Think of them as small adventure games where you solve puzzles using Automic.
The Operator, Designer, and Admin roles in PEM align closely with the roles available within Automic itself. Each role is tailored to specific responsibilities, ensuring users focus on the skills and knowledge most relevant to their work:
- Operator:
Operators are responsible for monitoring, executing, and managing workflows in Automic. In PEM, the Operator role covers topics like workflow execution, troubleshooting, and day-to-day operations to ensure smooth automation processes. - Designer:
Designers are the architects of workflows and automation solutions in Automic. The Designer role in PEM includes content on creating, optimizing, and maintaining workflows and objects, with a focus on best practices for efficiency and scalability. - Admin:
Admins handle system-level configurations, user management, security settings, and advanced maintenance tasks in Automic. PEM’s Admin role offers in-depth training on system setup, troubleshooting, and managing complex environments, including OS-level access through PEM Labs.
By mirroring Automic’s role structure, PEM ensures that members can seamlessly apply what they learn to their actual responsibilities within the software, making the training practical and highly relevant.
We host live sessions called Solution Corners 12 times a year, offering direct interaction with our experts. These sessions are open for questions on any Automic topic, and members can submit questions in advance for a more in-depth discussion.
Additionally, we provide online consulting—exclusive video conference sessions with our Automic specialists. Members with a consulting quota can book appointments directly via the experts’ calendars, ensuring flexible and personalized support.
In normal Automic training courses, the trainer is available to you for a few days. If you’re lucky, you might be able to provide input before the training, and if you’re particularly lucky, you might be able to ask 1-2 questions in the weeks following the training.
Our members can send us an email at any time. We answer questions immediately by email. If our members have questions about specific topics, they can also use the comment function. We call this “year-round Automic support”.
You always sign up for a membership for one year. After that, it is usually renewed automatically.
You can cancel at any time up to one month before the end of the contract with a simple email. Of course, you can limit the membership to one year at the beginning of the contract.
