Jump to: navigation, search
(Update with the copy of version: 8.5.2DRAFT)
(Update with the copy of version: 8.5.2DRAFT)
 
(One intermediate revision by one other user not shown)
Line 4: Line 4:
 
Each <tt>Not Ready Reason</tt> can be customized by creating a section named '''[interaction-workspace]''' in the annexes of <tt>Action Code</tt> objects that are used to define <tt>Not Ready Reason</tt> codes. Next, define and configure the options in that section to customize the way that not-ready reasons are sent to your T-Server.
 
Each <tt>Not Ready Reason</tt> can be customized by creating a section named '''[interaction-workspace]''' in the annexes of <tt>Action Code</tt> objects that are used to define <tt>Not Ready Reason</tt> codes. Next, define and configure the options in that section to customize the way that not-ready reasons are sent to your T-Server.
  
'''Example:''' Use ''either'' Configuration Manager or [[:Documentation/GA|Genesys Administrator]] for this procedure:
+
'''Example:''' Use ''either'' Configuration Manager or [[:Documentation/GA|Genesys Administrator Extension]] for this procedure:
  
 
<tabber>
 
<tabber>
Line 27: Line 27:
 
'''End'''
 
'''End'''
 
|-|
 
|-|
Genesys Administrator=
+
Genesys Administrator Extension=
'''Purpose:''' Create an ActionCode of type NotReady in [[:Documentation/GA|Genesys Administrator]].
+
'''Purpose:''' Create an ActionCode of type NotReady in [[:Documentation/GA|Genesys Administrator Extension]].
  
 
'''Start'''<br/>
 
'''Start'''<br/>
  
 
<ol type="a">
 
<ol type="a">
<li>Open [[:Documentation/GA|Genesys Administrator]]</li>
+
<li>Open [[:Documentation/GA|Genesys Administrator Extension]]</li>
 
<li>Navigate to Provisioning > Desktop</li>
 
<li>Navigate to Provisioning > Desktop</li>
 
<li>Click <tt>Action Codes</tt></li>
 
<li>Click <tt>Action Codes</tt></li>
Line 49: Line 49:
  
 
</tabber>
 
</tabber>
 
<!--
 
'''Next Steps'''<br/>
 
The NotReady reasons for each implementation can then be set as described in the Workspace <tt>[[Documentation:HTCC:IWWDep:ConfigurationOptions:8.5.1#agent-status.not-ready-status|agent-status.not-ready-status]]</tt> in the [[Documentation:HTCC:IWWDep:ConfigurationOptions:8.5.1|Configuration Guide]].
 
-->
 
 
 
<!-- TO DO: Insert Link to Config Manager PDF
 
 
CME Help File
 
http://docs.genesyslab.com/Special:Repository/fr_cme-help.zip?id=61e8cfa5-b64c-47f6-8827-fe7821cae44b
 
 
-->
 
 
<!---
 
==NotReady Action Codes - Cloud Implementation==
 
For a Cloud Implementation, NotReady Action Codes are set up as <tt>Action Code</tt> objects of type <tt>Not Ready</tt> in the Configuration Layer exactly as described in the [[#NotReady_Action_Codes_-_Premise_Implementation|Premise Implementation]], except they are required to be named with the domain name ahead of the <tt>Action Code</tt>,
 
'''Example:''' <tt>Domain_name.Appointment</tt>
 
 
NotReady Action Codes are set up as <tt>Action Code</tt> objects of type <tt>Not Ready</tt> in the Configuration Layer, using Configuration Manager or [[:Documentation/GA|Genesys Administrator]].
 
 
NotReady reasons can then be set for agents in the <tt>[[Documentation:HTCC:IWWDep:ConfigurationOptions:8.5.1#agent-status.not-ready-status|agent-status.not-ready-status]]</tt> configuration option, as described in the [[Documentation:HTCC:IWWDep:ConfigurationOptions:8.5.1|Workspace Configuration Guide]]
 
-->
 
  
 
[[Category:V:HTCC:8.5.2]]
 
[[Category:V:HTCC:8.5.2]]

Latest revision as of 15:54, July 14, 2021

Configuring Not Ready Reason Codes

Workspace Web Edition provides "reasons" with which agents can specify details about their NotReady status, for instance: Lunch, 15 minute break, Appointment, Meeting, and so on. These reasons are configured by creating Action Code objects of type Not Ready.

Each Not Ready Reason can be customized by creating a section named [interaction-workspace] in the annexes of Action Code objects that are used to define Not Ready Reason codes. Next, define and configure the options in that section to customize the way that not-ready reasons are sent to your T-Server.

Example: Use either Configuration Manager or Genesys Administrator Extension for this procedure:

Purpose: Create an ActionCode of type NotReady in Configuration Manager. Start

  1. Open Configuration Manager
  2. Go to the appropriate Tenant
  3. Navigate to Action Codes Folder
  4. Right-click > New > Action Code OR File > New > Action Code
  5. For Name, change it to an appropriate name (example: Lunch Break)
  6. Tenant should already be populated with the tenant name
  7. For Type, select Not Ready
  8. For Code, choose a relevant code for reporting purposes.
  9. Note that codes must be unique within each Type

  10. Click Apply or OK

End

Purpose: Create an ActionCode of type NotReady in Genesys Administrator Extension. Start

  1. Open Genesys Administrator Extension
  2. Navigate to Provisioning > Desktop
  3. Click Action Codes
  4. Click New
  5. For Name, change it to an appropriate name (example: Lunch Break)
  6. Tenant should already be populated with the tenant name
  7. For Type, select Not Ready
  8. For State, ensure it is clicked as Enabled
  9. For Code, choose a relevant code for reporting purposes.
  10. Note that codes must be unique within each Type

  11. Click Save & Close

End

This page was last edited on July 14, 2021, at 15:54.
Comments or questions about this documentation? Contact us for support!