(Update with the copy of version: 8.5.2) |
|||
| Line 4: | Line 4: | ||
====privilege.twitter.can-use==== | ====privilege.twitter.can-use==== | ||
| − | * Default Value: true | + | * Default Value: <tt>true</tt> |
| − | * Valid Values: true, false | + | * Valid Values: <tt>true</tt>, <tt>false</tt> |
* Changes take effect: When the session is started or restarted. | * Changes take effect: When the session is started or restarted. | ||
* Description: The agent is permitted to use the Twitter channel. | * Description: The agent is permitted to use the Twitter channel. | ||
====twitter.auto-answer==== | ====twitter.auto-answer==== | ||
| − | * Default Value: false | + | * Default Value: <tt>false</tt> |
| − | * Valid Values: true, false | + | * Valid Values: <tt>true</tt>, <tt>false</tt> |
* Changes take effect: When the session is started or restarted. | * Changes take effect: When the session is started or restarted. | ||
* Description: 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 [[Documentation:HTCC:IWWDep:OverridingInteractionWorkspaceOptions:8.5.2|Deployment Guide]]. | * Description: 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 [[Documentation:HTCC:IWWDep:OverridingInteractionWorkspaceOptions:8.5.2|Deployment Guide]]. | ||
Revision as of 15:55, October 3, 2014
Workspace Web Edition provides the following options for managing Twitter:
privilege.twitter.can-use
- Default Value: true
- Valid Values: true, false
- Changes take effect: When the session is started or restarted.
- Description: The agent is permitted to use the Twitter channel.
twitter.auto-answer
- Default Value: false
- Valid Values: true, false
- Changes take effect: When the session is started or restarted.
- Description: 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.
Comments or questions about this documentation? Contact us for support!