Mass changes

📄️ Agent group: Create

This module supports creating new and editing existing agent groups. For the platform 'CIT' it is possible to set the 'Solution'. Supported solutions are 'FTPAGENT', 'INFORMATICAAGENT', 'MAILAGENT', 'WEBSERVICEREST' and 'WEBSERVICESOAP'. Specifying 'All' or 'All active and inactive' as the mode, you need to specify the max number of parallel tasks. If the option is 'Limit maximum parallel tasks', the limit has to be set in the field 'Max. parallel tasks'

📄️ Agent Group: Edit

This module supports setting the mode of the agent groups. For the mode First it is possible to define the agent that should be at the top of the list.

📄️ Job: Set Agent Log

Since version 8 of the UC4 Operations Manager some protocol information will not be written to the report (REP) anymore. Instead the information will be written to another report called agent log (PLOG). This report must be activated via an option. This module can activate and deactivate the option.

📄️ Agent: Replace

The module can be used to replace agents in several objects. The rules for the replacement has to be defined in a mapping file.

📄️ Object: Create

This simple module allows to create objects. Optionally a title can be provided. To create the objects a folder and a template must be specified.

📄️ Runnable: Set Deactivate Condition

The module sets attributes for the deactivation condition, which can be read with the module info.DeactivateConditionRead.

📄️ Delete

Delete objects based on different filter options

📄️ Folder: Delete Recursive

The module can be used to delete hugh amounts of objects in a folder structure. The restriction for the maximum number of object to be returned by a search are irrelevant for this module.

📄️ Object: Edit documentation

The module provides several possibilities to add or change the documentation of objects. All methods of modification can be applied the text and XML documentation. The new text is read from a file.

📄️ Runnable: Generate at Runtime

All executables objects have the option 'generate at runtime'. It defines if the object should be generate just before the start or when its parent is generated. This module can be used to to activate or deactivated. If the option is already in the desired state the object will be skipped.

📄️ Object: Folder Synchronization

This module finds all objects it has found with the set filters in the source connection in the target connection and moves the object to the same folder as the source connection. If the folder in the destination connection does not already exist in which the object with the same name is located in the source connection, this folder will be created.

📄️ Login: Edit

The module is used to edit login objects. It is able to modify existing entries and to add new ones.

📄️ Runnable: Maximum Runtime Monitor & Actions

For runnable objects a monitor of the maximum runtime can be defined that may trigger actions on deviations. The module allows to edit the attributes for the monitor options and the actions.

📄️ Object: Move

The module moves objects to another folder. The original folder structure will be created below the destination folder. It is possible to remove parts of the original folder. If there is a link in the destination folder it will be removed before moving the object.

📄️ Runnable: Set PromptSets

This module can attach PromptSets to executable objects. A mode can be used to select if previously set PromptSets should be removed or if the new ones should only be added.

📄️ Runnable: Amend Variables

The module can modify the variables of executable object shown in the tab variables & promptsets. As input a b4A script is used.

📄️ Object: Edit Processes

A lot of objects contain processes, which may contain AE script or operating system code. In migration projects or while implementing new standards it might be necessary to do mass changes. This module can be used in four different modes to perform these changes.

📄️ Object: Rename

An important concept for |Automic| environments is the naming of objects. Naming objects is the base for an authorization concept. The rules for the naming for objects may change over time for different reasons. This module provides the functionality to rename objects based on rules defined in a mapping file.

📄️ Object: Restore

The Automation Engine offers an object-based version management, which can be activated. Each object gets its own version number, which will be increased when the object is saved. If a transport has be rolled back it is not possible based on one version number for all objects. This module provides the possibility to restore the last or last but one version. Additionaly objects can be restored to version of a given point in time.

📄️ Runnable: Set Result Evaluation

Error handling for failed tasks of workflows and schedules can be defined by setting an object and a status that defines the positive status for all tasks (e.g. ENDEDOK or ANYOK). This module is able to set the object and the OK status.

📄️ Schedule: Add Task

This module is able to add objects as tasks to one or more schedules. Additionally to the task name a time and a calendar condition can be defined. If a list of calendar keywords is sepcified all of the keywords must be found in the given calendar object.

📄️ Schedule: Deactivate Task

This module can activate or deactivate schedule tasks that re identified by the start time anf object name. Additionally the reload of the definition at turnaround can be triggered.

📄️ Schedule: Remove Task

The module removes tasks from a schedule object if the name of the object matches a given pattern.

📄️ Service Level Objective: Edit

Designation

📄️ Runnable: Edit sync attributes

The module is able to add or replace the sync attributes of objects. Which sync attributes should be edited is defined in a file.

📄️ Object: Title Generator

The title of objects is used to provide a short description of the functionality of objects. In newer versions of the Automation Engine the title of objects becomes more important as it is used in several situations in the AWI instead of the object name. To provide an automatically generated title for objects thsi module can be used. It can generate titles based on several object attributes.

📄️ User: Deactivate

With this module user accounts can be activated and deactivated. One use case is to combine this module with ana.UserLastSession to deactivate users who did not log on for a given amount of time.

📄️ User: Edit

The module is used for creating and modifying users. It writes user information from a file (CSV format) to a client that can be created with the module info.UserRead. A lot of user options can be set and the memberships of user groups can be defined.

📄️ User Group: Add Users

The module adds users to a user group. The users can either be specified as a list of user name patterns or read from the members of a list of groups

📄️ User group: Edit Authorization

To edit group authorizations this module can be used. It supports actions like 'Add' or 'Remove' and 'Set' und reads the authorizations from a file in JSON format.

📄️ User group: Edit Privileges

To edit group privileges this module can be used. If privileges already have the required state it will not be touched when the action is 'Add' or 'Remove'. The action 'Set' will remove all privileges and afterwards set the selected.

📄️ User: Edit Privileges

To edit user privileges this module can be used. If privileges already have the required state it will not be touched when the action is 'Add' or 'Remove'. The action 'Set' will remove all privileges and afterwards set the selected.

📄️ Variable: Delete entry

This module is able to delete entries in variable objects. If key can not be found in the object, it is interpreted as an error.

📄️ Variable: Edit

This module can be used to change values or keys in variable objects. The modifications to perform are defined in a b4A script, which is similar to the replacement rules defined for the |Automic| utility DB Change. A rule may replace a value if the whole or a part of the old value matches a given pattern.

📄️ Variable: Set entry

This module can be used to change or add entries to variable objects. Only the key must be passed on to the module. All values (1-5) are optional.

📄️ Variable: Synchronize (Edit)

The module matches the entries of variables with the same name in several clients. It is als possible to set different values in specific clients.

📄️ Workflow: Add Tasks

This module is able to add objects as tasks to one or more workflows. The position in the workflow will be defined by the predecessor. When adding the task all successors of the given predecessor will be set as sucessors of the new task. The status in the dependencies of the successors can be provided via option.

📄️ Workflow: Deactivate Task

This module can activate or deactivate tasks in the defintions of workflows. The task kann be defined by just the name or additionally with the running number. If just the name is given, then very task with this name is deactivate or activate.

📄️ Workflow: Replace Task

Similar to the module mc.WorkflowTaskAdd this module can modify workflow objects. In this case it replaces tasks in a workflow. The rules for the replacement are defined in a mapping file.