Jump to: navigation, search

Transactions

Transactions define how applications calculate customer-defined statistics.

For more information about specifications and use of Transactions, consult the Universal Routing documentation.

The Transactions list shows the Transactions that are in your environment. It is sorted in a hierarchy by Tenants, configuration units, sites, and folders. To view objects by a particular hierarchy, select the hierarchy type in the drop-down menu above the list.

Important
Transactions that are disabled appear grayed out in the list.

Configuration Manager respects tenancy permission settings. You can access only those objects that you have been granted permissions and privileges to access.

You can filter the contents of this list in two ways:

  • Type the name or partial name of an object in the Quick Filter field.
  • Click the cube icon to open the Tenant Directory filter panel. In this panel, click the Tenant that you want to select. Use the Quick Filter field in this panel to filter the Tenant list.

You can sort the items in the list by clicking a column head. Clicking a column head a second time reverses the sort order. You can add or remove columns by clicking Select Columns.

To select or de-select multiple objects at once, click Select.

To create a new Transaction object, click New. To view or edit details of an existing object, click the name of the object, or click the check-box beside an object and click Edit. To delete one or more objects, click the check-box beside the object(s) in the list and click Delete. You can also delete individual objects by clicking on the object and then clicking Delete. Otherwise, click More to perform the following tasks:

  • Clone—Copy a Transaction.
  • Move To—Move a Transaction to another hierarchical structure.
  • Enable or disable Transactions.
  • Create a folder, configuration unit, or site. See Object Hierarchy for more information.

Click the name of a Transaction to view additional information about the object. You can also set options and permissions.

Creating Transaction Objects


Steps

  1. Click New.
  2. Enter the following information. For some fields, you can either enter the name of a value or click Browse to select a value from a list:
    • Name—The name of the Transaction. You must specify a value for this property, and that value must be unique. A combination of the name and type specified in the Type property determines the uniqueness within the Configuration Database (in an enterprise environment) or within the Tenant (in a multi-tenant environment).
    • Alias—An alternative name for this Transaction. If you specify this value, it must be unique within the object type specified in the Type property for the given contact center.
    • Transaction Type—The type of this Transaction. You must specify a value for this property. Once you set the value, you cannot change it.
    • Recording Period (min.)—A time period, in minutes, indicating how often to report the current status of the Transaction or to record it in the database.
    • Format—An application-specific format or script that defines how the Transaction is processed.
    • Tenant—In a multi-tenant environment, the Tenant to which this object belongs. This value is automatically set to the Tenant that was specified in the Tenant Directory field in the object list.
    • State Enabled—If selected, indicates that the object is in regular operating condition and can be used without any restrictions.
  3. Click Save.
Important
From 8.5.260.11, GAX now saves user preferences in the Person object by default. If the [general] userpreference_in_transaction GAX application option is set to true, then GAX saves user preferences in the Transaction object in the Transactions/UserPreference folder.

In this case, GAX copies only the annex sections starting with the option ga_preferences., from the Person annex to the Transaction annex.

When GAX creates the Transaction object, GAX removes all access permissions (for users and access groups) to the Transaction object, except the default user and the current user.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on 7 December 2017, at 02:57.