An object definition consists of several pages. The General page is available for all objects. As a developer and object designer, on the General page you define the basic object information and apply custom values to it that you can later use for filtering.
The General page of executable objects contains the following two sub pages:
If you have the necessary privileges, the General page has a further sub page: Object Authorizations. For more information, see Authorizations Page.
Note: The variables icon indicates that the input field can be populated using variables. For more information, see Inserting Variables/VARA Objects in Objects and Scripts.
This page includes the following:
Accessing the General Page
After adding an object, the object definition pages open to the object-specific page. Click the General tab on the left pane to open the General page.
Object Info Section
The only settings you can change here are:
Optional. Short description that helps you recognize the object at a glance. Particularly important in Workflow objects because it can be displayed on the task boxes. For more information, see Name, Title, and Alias.
In executable objects only. Activate it if you want this object to be processed, otherwise its status is ENDED_INACTIVE_OBJECT (return code: 1925).
Audit information on the object. More detailed information on the object revisions is available on the Version Management Page.
Some of the fields in this section are not available for certain object types.
Archive Key 1/2
Freely definable keywords you assign to the object. Later on you can perform searches or you can filter objects using them. They are displayed in separate columns in various lists across the application.
You can type them here or you can select variables you have previously defined for this purpose. Alternatively, archive keys can be set or read with the following script elements:
Free text, available for executable objects only. For example Cost Center, Department Identifier, etc.
Available for executable objects only. The custom attributes are filtering and grouping criteria. You can use the values you enter in the custom attributes as follows:
- To filter tasks in the Process Monitoring perspective, see Business Unit or Region.
- In Service Level Objective objects (SLOs), they are the potential beneficiaries of the services monitored by the SLO object.
Custom attributes are defined by administrator users in the UC_CUSTOM_ATTRIBUTES variable when configuring the system. For more information, see UC_CUSTOM_ATTRIBUTES - Grouping Criteria in Executable Objects.
To Define Custom Attributes
- Select a Key from the first drop-down list.
- Type a new Value or select an existing one from the list. The available values originate from a VARA reference object.
- Click Add. You must have selected values in both fields.
Extended Reports Section (Executable Objects Only)
The Automation Engine has a comprehensive auditing functionality that includes the possibility to produce extended reports for executable objects in addition to the standard ones.
When configuring your system, the administrator can write specifications in the UC_CLIENT_SETTINGS variable that determine whether or not they should be created. If so, this variable also determines which reports should be created. This applies client-wide.
Here you define whether these settings should be applied to this object or if you want to overrule them:
As defined in UC_CLIENT_SETTINGS
The extended reports are created as defined in this variable
All extended reports
This option overrules the client-wide definition. For this object, all extended reports are generated, no matter what has been specified in the UC_CLIENT_SETTINGS variable
No extended reports
This option overrules the client-wide definition. For this object, no extended reports are generated, no matter what has been specified in the UC_CLIENT_SETTINGS variable.