Object Templates

Automic Automation is provided with object templates that are stored in the TEMPLATES folder in the Process Assembly perspective in Client 0. These standard templates contain all the configuration options that developers and object designers will need to create their objects.

As an administrator, you can create additional object templates and preconfigure them. When developers and object designers create an object based on one of these templates, the object already contains the configuration that you have predefined.

To create object templates, you must manipulate the UC_OBJECT_TEMPLATE VARA object that is available by default after installing Automic Automation. It contains the names (the key) and object type (the value) settings of all object templates that are available in your system. If you want to create a new template, you must add its name and type here.

Preconfigured object templates speed up the process of creating objects and guarantee that critical object configuration is consistent.

To Create Object Templates

  1. Open the UC_OBJECT_TEMPLATE VARA object is stored either in the DIV_VARIABLES folder on Client 0, or in the No Folder area of any other Client.

  2. Add a new entry to UC_OBJECT_TEMPLATE. To do so, make a copy of the entry that corresponds to the object type for which you want to add a template.

    Example: You want to create a template for critical Windows Jobs that should run on a specific Agent and with a specific Login object. In this case, make a copy of the standard JOBS.WIN template.

  3. Change the Key and the Value.

    To follow with our example, enter JOBS_CRITICAL.WIN in both cells.

  4. Create a template object based on this new entry in UC_OBJECT_TEMPLATE.

    1. Go to the TEMPLATES folder in the Process Assembly perspective.

    2. Right-click the standard template that corresponds to the type of object that you need. In our case, this is JOBS.WIN.

    3. Select Duplicate.

    4. On the Duplicate dialog, enter the Name of the new object template.

      Important! The name of this new object must match the value that you have entered in UC_OBJECT_TEMPLATE otherwise, this feature will not work. In our case, this would be JOBS_CRITICAL.WIN.

Now when developers and object designers create a new object, they will see a new template called JOBS_CRITICAL.WIN in the Add Object dialog. This template creates objects with your preconfigured values.

Best Practices

Clean Up the List of Tasks Regularly

The list of tasks can grow with each execution. If your organization is executing hundreds or thousands of tasks on a daily basis, working with the list is difficult unless you or your administrator perform some house-keeping operations. You have the following options:

  • (Operators) Clean up the list manually on a regular basis by right-clicking the tasks and selecting Modify > Deactivate.

  • (Administrators) Configure the templates of the underlying objects so that their tasks deactivate automatically as soon as the execution has finished. You do so in Client 0 on the Attributes object definition page. For more information, see Automatic Deactivation Section.

  • (Administrators) Clean up the Automation Engine database regularly. For more information, see Utilities.

Important! Not cleaning-up the list of tasks will have a negative impact on your overall performance and might lead to a system outage.

See also:

UC_OBJECT_TEMPLATE - Object Types and Templates