interaction.override-option-key
Section: interaction-workspace
Default Value: No default value
Valid Values: An attached data key name (string). The list is provided in the Attached Data in the strategy.
Changes Take Effect: After the next platform configuration refresh interval.
Introduced: 9.0.000.31
Specifies that certain application options can be overridden by using a transaction object. The value of this option provides the key name of the attached data that contains the list of transaction objects.
(Update with the copy of version: 9.0.0DRAFT) |
(Update with the copy of version: 9.0.0DRAFT) |
||
| Line 1: | Line 1: | ||
= Overriding Workspace Options = | = Overriding Workspace Options = | ||
| − | You can override a Workspace option by using a routing strategy that overrides the configuration option based on attached data and Transaction objects. This enables you to change the appearance of interactions for each line of business based on a key-value pair that is defined in the annex of Transaction objects. | + | You can override a Workspace option by using a [[Documentation:Composer:Help:Welcome|routing strategy]] that overrides the configuration option based on attached data and Transaction objects. This enables you to change the appearance of interactions for each line of business based on a key-value pair that is defined in the annex of Transaction objects. |
Workspace Agent Desktop uses Transaction objects of the <tt>object list</tt> type. Attach a transaction name or list of transaction names to the interaction in your strategy. The transaction names in the list must be separated by commas. Workspace Agent Desktop reads the transaction objects at rendering time to override the static options. | Workspace Agent Desktop uses Transaction objects of the <tt>object list</tt> type. Attach a transaction name or list of transaction names to the interaction in your strategy. The transaction names in the list must be separated by commas. Workspace Agent Desktop reads the transaction objects at rendering time to override the static options. | ||
| Line 11: | Line 11: | ||
<p>Transaction objects rely on the option reference to determine if a particular option can be overridden in a Transaction. You can only override options in the <tt>interaction-workspace</tt> section. Therefore, you must replicate the <tt>interaction-workspace</tt> section to the annex of the Transaction objects.</p> </li> | <p>Transaction objects rely on the option reference to determine if a particular option can be overridden in a Transaction. You can only override options in the <tt>interaction-workspace</tt> section. Therefore, you must replicate the <tt>interaction-workspace</tt> section to the annex of the Transaction objects.</p> </li> | ||
<li>Configure the {{Optionslink|link=Options:Genesys_Web_Services:interaction-workspace:interaction-override-option-key}} option to define the key where the Transaction objects are to be listed in attached data.</li> | <li>Configure the {{Optionslink|link=Options:Genesys_Web_Services:interaction-workspace:interaction-override-option-key}} option to define the key where the Transaction objects are to be listed in attached data.</li> | ||
| − | <li>Using | + | <li>Using [[Documentation:Composer:Help:UserDataBlock:8.1.5|Composer]], edit your routing strategy by adding an "Attach" or "Multi-attach" block that attaches the key value pair that is defined below: |
* <tt>key</tt>: The name of the key that you defined in the option set in Step 2. | * <tt>key</tt>: The name of the key that you defined in the option set in Step 2. | ||
* <tt>value</tt>: One or several comma-separated Transaction objects, as defined in Step 1. | * <tt>value</tt>: One or several comma-separated Transaction objects, as defined in Step 1. | ||
Revision as of 15:06, December 4, 2019
Overriding Workspace Options
You can override a Workspace option by using a routing strategy that overrides the configuration option based on attached data and Transaction objects. This enables you to change the appearance of interactions for each line of business based on a key-value pair that is defined in the annex of Transaction objects.
Workspace Agent Desktop uses Transaction objects of the object list type. Attach a transaction name or list of transaction names to the interaction in your strategy. The transaction names in the list must be separated by commas. Workspace Agent Desktop reads the transaction objects at rendering time to override the static options.
Before you begin, ensure that Genesys Web Services is deployed and you have a strategy that routes to your agent workstations.
- Configure one or more Transaction objects, of list type, in Genesys Administrator Extension, by using the standard approach that is used for other object types in the hierarchy.
Transaction objects rely on the option reference to determine if a particular option can be overridden in a Transaction. You can only override options in the interaction-workspace section. Therefore, you must replicate the interaction-workspace section to the annex of the Transaction objects.
- Configure the interaction.override-option-key option to define the key where the Transaction objects are to be listed in attached data.
- Using Composer, edit your routing strategy by adding an "Attach" or "Multi-attach" block that attaches the key value pair that is defined below:
- key: The name of the key that you defined in the option set in Step 2.
- value: One or several comma-separated Transaction objects, as defined in Step 1.