Library

At Library, you can manage the following:

• Use Modules to set up containers for the Tasks that you can execute on Agents. Modules hold information about how these Tasks should be executed, such as Task settings, order of execution of Tasks, parameters and conditions.
• Use Tasks to configure the actions that you can be perform by an Agent. With a Task you can, for example, install software on Agents or manage users and groups in Active Directory, but also query security risks on Agents or query mailboxes on Microsoft Exchange servers.
• Use Projects to set up containers for multiple Modules. You can combine Modules into a Project if you find yourself repeatedly scheduling the same sequence of Modules. By combining several Modules into one Project, the Modules in the Project can be scheduled as one Job instead of as a series of separate Jobs.
• Use Run Books to set up containers for Modules and/or Projects. If you find yourself repeatedly scheduling the same sequences of Modules and Projects on different Agents or Teams, you can combine these Modules and Projects into a Run Book. This makes Job scheduling easier.
• Use Resources to manage files that are needed to perform certain Tasks, such as MSI files, setup files, patches, hotfixes, etc.
• Use Variables to set up placeholders for information that can be used in multi-tenant Ivanti Automation sites, in order to manage different settings for different customers and/or projects.

You can use the following elements in Tasks, Modules, Projects and Run Books to make them generic:

• Use Conditions to set up rules that determine whether a Task, Module or Run Book Job should be executed.
• Use Functions to generate information in various fields in Tasks automatically.
• Use Parameters to set up placeholders for the values in various fields in Tasks, such as text, file paths, credentials, etc. The actual values of these fields can be provided when the Task is used in a Job. This makes it possible to create generic Modules, Projects and Run Books that can be customized to each situation when required.
• Use Evaluators to set up rules that determine the status of a query Task, based on the query results. This makes it possible to let the execution of succeeding Tasks depend on the results of a query. Evaluators are available for certain query Tasks only.

Library section content can be stored to source control. This version supports GitHub, with GitLab support planned for the following releases. For more information, see Source control.

Within a Library item, such as Modules or Run Books, use the Search toolbar button to search that item for matching strings. The Load all data on startup option preloads searchable data when you open the search dialog box, making searches faster. In environments with a lot of Automation data, you may want to disable this if the preload wait is too long for you.

The Only show first 20 results search option is enabled by default and also helps speed up searches. Clear this option if you want to see the complete set of results.

UI Responsiveness

To responsive of the Automation user interface (UI) can deteriorate if too many objects have to be loaded. For best results, Ivanti recommends the following limits:

Library Section	Number of records	Number of subfolders
Modules	2500 or less	150 or less
Projects	3000 or less	230 or less
Run Books	3000 or less	230 or less
Resource	2000 or less	150 or less

Exceeding these limits may result in interactions taking several seconds or more to be visible.