Jump to: navigation, search
Line 8: Line 8:
 
* Set Interaction Disposition
 
* Set Interaction Disposition
  
You use the following options in the <tt>interaction-workspace</tt> section to configure [[ConfigurationOptions#Twitter|Twitter]] interactions:
+
You use the following options in the '''[interaction-workspace]''' section to configure Twitter interactions:
* <tt>[[ConfigurationOptions#privilege.twitter.can-use|privilege.twitter.can-use]]</tt> &mdash; Enables agent to use the Twitter channel.  
+
* [[ConfigurationOptions#privilege.twitter.can-use|privilege.twitter.can-use]] &mdash; Enables agent to use the Twitter channel.  
* <tt>[[ConfigurationOptions#twitter.auto-answer|twitter.auto-answer]]</tt> &mdash; Specifies whether a Twitter interaction is automatically accepted when an Interaction Server Invite event is received. This option can be overridden by a routing strategy as described in Deployment Guide.  
+
* [[ConfigurationOptions#twitter.auto-answer|twitter.auto-answer]] &mdash; Specifies whether a Twitter interaction is automatically accepted when an Interaction Server Invite event is received. This option can be overridden by a routing strategy as described in Deployment Guide.  
* <tt>[[ConfigurationOptions#interaction.disposition.is-mandatory|interaction.disposition.is-mandatory]]</tt> &mdash; Specifies whether it is mandatory for the agent to set a disposition code before Marking Done an interaction. This option can be overridden by a routing strategy.
+
* [[ConfigurationOptions#interaction.disposition.is-mandatory|interaction.disposition.is-mandatory]] &mdash; Specifies whether it is mandatory for the agent to set a disposition code before Marking Done an interaction. This option can be overridden by a routing strategy.
* <tt>[[ConfigurationOptions#interaction.disposition.is-read-only-on-idle|interaction.disposition.is-read-only-on-idle]]</tt> &mdash; Prevents changes to the disposition code after the interaction has been released. This option can be overridden by a routing strategy.
+
* [[ConfigurationOptions#interaction.disposition.is-read-only-on-idle|interaction.disposition.is-read-only-on-idle]] &mdash; Prevents changes to the disposition code after the interaction has been released. This option can be overridden by a routing strategy.
* <tt>[[ConfigurationOptions#interaction.disposition.key-name|interaction.disposition.key-name]]</tt> &mdash; The key that is used to populate attached data or a user event when a disposition code is submitted to the back-end system, such as T-Server, Interaction Server, and Contact Server. This option can be overridden by a routing strategy.
+
* [[ConfigurationOptions#interaction.disposition.key-name|interaction.disposition.key-name]] &mdash; The key that is used to populate attached data or a user event when a disposition code is submitted to the back-end system, such as T-Server, Interaction Server, and Contact Server. This option can be overridden by a routing strategy.
* <tt>[[ConfigurationOptions#interaction.disposition.use-attached-data|interaction.disposition.use-attached-data]]</tt> &mdash; Enables the adding of attached data from the interaction in UserEvent. This option can be overridden by a routing strategy.
+
* [[ConfigurationOptions#interaction.disposition.use-attached-data|interaction.disposition.use-attached-data]] &mdash; Enables the adding of attached data from the interaction in UserEvent. This option can be overridden by a routing strategy.
* <tt>[[ConfigurationOptions#interaction.disposition.value-business-attribute|interaction.disposition.value-business-attribute]]</tt> &mdash; A character string that specifies the name of the Business Attribute that contains the Attribute Values that are used as an enumerated value for a disposition code. This option can be overridden by a routing strategy.
+
* [[ConfigurationOptions#interaction.disposition.value-business-attribute|interaction.disposition.value-business-attribute]] &mdash; A character string that specifies the name of the Business Attribute that contains the Attribute Values that are used as an enumerated value for a disposition code. This option can be overridden by a routing strategy.
  
  
 
[[Category:V:HTCC:8.5.2DRAFT]]
 
[[Category:V:HTCC:8.5.2DRAFT]]

Revision as of 16:38, July 9, 2015

Twitter Interactions

Workspace supports the following functionality for Twitter interactions:

  • Accept an interaction
  • Reject an interaction
  • Ignore an interaction
  • Mark Done an interaction
  • One-Step Transfer an interaction
  • Set Interaction Disposition

You use the following options in the [interaction-workspace] section to configure Twitter interactions:

  • privilege.twitter.can-use — Enables agent to use the Twitter channel.
  • twitter.auto-answer — Specifies whether a Twitter interaction is automatically accepted when an Interaction Server Invite event is received. This option can be overridden by a routing strategy as described in Deployment Guide.
  • interaction.disposition.is-mandatory — Specifies whether it is mandatory for the agent to set a disposition code before Marking Done an interaction. This option can be overridden by a routing strategy.
  • interaction.disposition.is-read-only-on-idle — Prevents changes to the disposition code after the interaction has been released. This option can be overridden by a routing strategy.
  • interaction.disposition.key-name — The key that is used to populate attached data or a user event when a disposition code is submitted to the back-end system, such as T-Server, Interaction Server, and Contact Server. This option can be overridden by a routing strategy.
  • interaction.disposition.use-attached-data — Enables the adding of attached data from the interaction in UserEvent. This option can be overridden by a routing strategy.
  • interaction.disposition.value-business-attribute — A character string that specifies the name of the Business Attribute that contains the Attribute Values that are used as an enumerated value for a disposition code. This option can be overridden by a routing strategy.
Comments or questions about this documentation? Contact us for support!