Object List

 

This tab allows you to name and describe the Object List.

 

 

Name: This mandatory property represents the name of the object. The name is limited to 128 characters. The object’s name should be unique to avoid confusion. We recommend that it also be somewhat descriptive so it’s easy to find. The name is used to identify the object in the Navigation pane and other places in the UI.

 

Label: Every object must be uniquely labeled within the scope of the namespace. The label is limited to sixty-four (64) characters. The label is typically the same value as the name (it is auto-filled to match the name you enter); however, uniqueness is always enforced for an object’s label. The label is recorded in the ActiveBatch namespace. The characters that may be used for the label property are restricted to alphanumeric (A-Z, a-z, 0-9), space, period (.), dash (-) and underscore (_). The label itself must begin with an alphabetic character. The label is typically used when scripting. All searches are case-insensitive. ActiveBatch does allow you to search for objects using either the label or the name properties.

 

ID: This is a unique read-only number that can be used to retrieve the object. Is it assigned by the system when a new object is saved.

 

Full Path: This read-only property provides the full namespace specification of the object. It consists of the container(s) the object has been placed in, with the object’s label appended to the end. For example, the fullpath: /IT Jobs/Nightly Run/<object label>, is such that IT Jobs is a root-level folder, Nightly Run is a plan, followed by the label of the object you are creating.

 

Description: This free form property is provided so you can document and describe the object to others. The description is limited to 512 characters. Clicking on the pencil icon will pull up a mini text editor where you can more easily enter your description.

 

State: This field indicates whether the object is enabled or disabled for use.

 

Read Only: This checkbox, when enabled, means the object list’s properties cannot be changed.  You must have “Modify” access permission to the object list object to set this feature. To clear the read-only attribute, uncheck the box.

 

The Objects property sheet consists of associated objects (if any). In the example below, there are 3 associated objects. The Object ID, Name, and Full path are provided.

 

 

Associate: This button allows you to associate new object(s) to the object list. After clicking on the button, the Select An Object dialog will appear as depicted in the image below.

 

 

Navigate to the desired object, click on it, then click OK. The object will be added to the object list.

 

Disassociate - This button allows you to disassociate (remove) objects from the list. Select the object(s) you wish to disassociate, then click the Disassociate button. Use of the Ctrl or Shift keys to multi-select objects is supported.

 

The Analytics properties are depicted in the image below.  This section details any changes made to the object list object, and provides you access to the object's revision history.

 

 

This selection allows you to view the audits that are created when the Object List object is initially defined. Changes made to the object are audited.

 

The Audits panel includes controls that allow you to filter the audits based on start and end dates. You can also limit the audits retrieved to a maximum number. The Refresh icon allows you to retrieve any audits that were generated after this dialog was initially displayed.

 

Each audit is contained in a single line in date and time sequence. Audits are read-only and cannot be modified. An icon appears at the beginning of each audit to help visually signal the severity of the audit. If an audit policy An audit policy provides a way for a user to add additional audit information when working with ActiveBatch objects and/or instances. For example, an audit policy can be created that prompts an ActiveBatch user to enter a reason why they are modifying an object, or disabling an object, or manually triggering a job or plan. The reason entered is stored in the audit trail of the object or instance. For more details see Audit Policy. has been established, you will see an additional comment icon to the right of the severity icon. If you mouse over the comment icon, the system will display the audit information as a tooltip.

 

Opening an audit item (by double-clicking on the item), depending on the nature of the audit, will sometimes reveal additional information concerning the audit. 

 

The View Plain Text button launches a small window with a list of the audits, You can copy the list and paste it into another document or program.

 

The Print button allows you to print the retrieved audits.

 

The Revision History button allows you to select one or more audits concerning changes made to an object and perform a difference operation between the selected revised objects.

 

This tab is where object security is configured. Security in ActiveBatch mirrors how security is granted using Windows security. That is, permissions applicable to the object (Read, Write, Modify, Delete, etc.) are Allowed or Denied for the Active Directory users and/or groups assigned to the object.

 

 

When new objects are created, they will either be assigned factory default Factory default security works as follows - When any new object type is created, the security assigned to the object includes two Active Directory groups - Authenticated Users and Administrators. Administrators are granted Full Control access to all objects, and Authenticated Users are granted a more limited set of permissions. security, or the factory default security will be overridden by a default policy A default policy allows you to preset a new object's properties to override factory default property values, and/or preset properties that are blank by default. See Default Policy for more details.  

 

When a default policy has been used to preset object security, the new object will either have:

 

1. The Inherit Security from Parent Object property checked (it is not checked by default). When checked, the listed users and/or groups along with their permissions granted will be read-only. The Add and Remove buttons will be disabled because security is being inherited from the object's parent container. When Inherit Security from Parent Object is checked, it is likely the ActiveBatch Administrator will be setting up security on parent container(s), and the job author will not have to modify anything about security. This would require a larger discussion with an ActiveBatch Administrator who it typically tasked to manage object security, since there are options.

2. The Inherit security from Parent Object property is not checked. The users and/or groups are listed along with their permissions granted, but there is likely some differences when compared to the factory default security, since the purpose of setting a default policy for security is to add Active Directory groups and/or users (and their access permissions) that are specific to your organization. Since Inherit Security is not checked, the Add and Remove buttons will be enabled. When this is the case, job authors will need to be advised if there needs to be any changes made to security when they create new objects.

 

As a best practice, it is best for an ActiveBatch Administrator to preset security using a default policy (for all object types) so job authors do not have to manage security, which can be time consuming and error-prone. See the ActiveBatch Installation and Administrator's Guide for more best practice information regarding object security.

 

Below is a list of permissions related to this object.

 

Access	Description
Read	User is allowed to read the object.
Write	User is allowed to write the object.
Modify	User is allowed to modify the object (Read + Write)
Delete	User is allowed to delete the object.
Use	Account is allowed to use the object.
Manage	Account is allowed to perform Enable/Disable operations.
Take Ownership	User is allowed to take ownership.
Change Permissions	User is allowed to change permissions for the object.
Full Control	All of the above access is enabled.

 

When new objects are created, they will either be assigned factory default Factory default security works as follows - When any new object type is created, the security assigned to the object includes two Active Directory groups - Authenticated Users and Administrators. Administrators are granted Full Control access to all objects, and Authenticated Users are granted a more limited set of permissions. security, or the factory default security will be overridden by a default policy A default policy allows you to preset a new object's properties to override factory default property values, and/or preset properties that are blank by default. See Default Policy for more details.  

 

When a default policy has been used to preset object security, the new object will either have:

 

1. The Inherit Security from Parent Object property checked (it is not checked by default). When checked, the listed users and/or groups along with their permissions granted will be read-only. The Add and Remove buttons will be disabled because security is being inherited from the object's parent container. When Inherit Security from Parent Object is checked, it is likely the ActiveBatch Administrator will be setting up security on parent container(s), and the job author will not have to modify anything about security. This would require a larger discussion with an ActiveBatch Administrator who it typically tasked to manage object security, since there are options.

2. The Inherit security from Parent Object property is not checked. The users and/or groups are listed along with their permissions granted, but there is likely some differences when compared to the factory default security, since the purpose of setting a default policy for security is to add Active Directory groups and/or users (and their access permissions) that are specific to your organization. Since Inherit Security is not checked, the Add and Remove buttons will be enabled. When this is the case, job authors will need to be advised if there needs to be any changes made to security when they create new objects.

 

As a best practice, it is best for an ActiveBatch Administrator to preset security using a default policy (for all object types) so job authors do not have to manage security, which can be time consuming and error-prone. See the ActiveBatch Installation and Administrator's Guide for more best practice information regarding object security.

 

Below is a list of permissions related to this object.

 

 

The dialog prompts you to enter a valid Active Directory user or group. After entering a user account or group, click the OK button. The user or group will be added to the list of users and groups displayed in the top panel.