Provides data for the completedCallback delegate of GetBooleanAttributeAsync(String, EventHandler<(Of <<'(GetAttributeCompletedEventArgs<(Of <<'(Boolean>)>>)>)>>), Object), GetStringAttributeAsync(String, EventHandler<(Of <<'(GetAttributeCompletedEventArgs<(Of <<'(String>)>>)>)>>), Object), GetIntegerAttributeAsync(String, EventHandler<(Of <<'(GetAttributeCompletedEventArgs<(Of <<'(Int32>)>>)>)>>), Object), and GetDateTimeAttributeAsync(String, EventHandler<(Of <<'(GetAttributeCompletedEventArgs<(Of <<'(DateTime>)>>)>)>>), Object) events of a Interaction.
Namespace: ININ.IceLib.InteractionsAssembly: ININ.IceLib.Interactions (in ININ.IceLib.Interactions.dll) Version: 0.0.0.0 (22.3.0.218)
Syntax
| C# |
|---|
public class GetAttributeCompletedEventArgs<TAttributeValue> : AsyncCompletedEventArgs |
| Visual Basic |
|---|
Public Class GetAttributeCompletedEventArgs(Of TAttributeValue) _ Inherits AsyncCompletedEventArgs |
Type Parameters
- TAttributeValue
- The attribute value.
Remarks
An interaction attribute is a piece of information about an interaction that travels with it
throughout the Interaction Center. For example, Telephone calls, chat sessions, Emails, and generic
objects are entities in IC that have some type of attribute associated with them. Attributes can be
created by a variety of entities, including the Interaction Center itself. For example, the Telephony
Services subsystem creates default call object attributes when a call object is established. Handlers,
IC applications, and programs developed using APIs can create and modify attributes.
Attributes are name/value pairs. To retrieve the value of an attribute, you must know its attribute name. The value of an attribute is usually string data. However, chat and call attributes can contain 32-bit binary data in DWORD format. Email objects return data that is stored in Interaction Designer’s list variable format.
Attributes are name/value pairs. To retrieve the value of an attribute, you must know its attribute name. The value of an attribute is usually string data. However, chat and call attributes can contain 32-bit binary data in DWORD format. Email objects return data that is stored in Interaction Designer’s list variable format.
- Attribute names are not case-sensitive. "Eic_StationName" "eic_stationname" refer to the same attribute.
- Attributes names that begin with Eic_ are primarily used by Interaction Client to display information about an object.
- Attributes whose name does not begin with Eic_ are primarily used by handlers or chat objects.
- Attributes whose name ends with "Raw" contain original, unprocessed values. These attributes are logged for reporting purposes.
- Directory Services "attributes" are not the same as interaction attributes discussed here. A Directory Services attribute is an item of information that is stored in Directory Services as a registry key. Interaction attributes are name/value pairs that travel with an object as it is processed by the Interaction Center server.
 Note |
|---|
| For more information about attributes, see Interaction Attributes Reference Guide in the System APIs section of the IC Documentation library on your IC server. |
Inheritance Hierarchy
System..::..Object
System..::..EventArgs
System.ComponentModel..::..AsyncCompletedEventArgs
ININ.IceLib.Interactions..::..GetAttributeCompletedEventArgs<(Of <(<'TAttributeValue>)>)>
System..::..EventArgs
System.ComponentModel..::..AsyncCompletedEventArgs
ININ.IceLib.Interactions..::..GetAttributeCompletedEventArgs<(Of <(<'TAttributeValue>)>)>
Version Information
Supported for IC Server version 2015 R1 and beyond.
For 4.0, supported for IC Server version 4.0 GA and beyond.
For 3.0, supported for IC Server version 3.0 GA and beyond.
For 4.0, supported for IC Server version 4.0 GA and beyond.
For 3.0, supported for IC Server version 3.0 GA and beyond.
