DES/Current/DESPEGuide/Provision - Revision history

WikiSysop at 17:00, June 10, 2022

2022-06-10T17:00:41Z

MPandian: Published

2022-03-25T12:31:48Z

Published

Marudhu.pandian@genesys.com: Published

2021-12-06T06:33:07Z

Published

Marudhu.pandian@genesys.com: Published

2021-06-30T11:11:05Z

Published

New page

{{Article
|Standalone=No
|DisplayName=Platform / Configuration Server and GWS settings for Designer
|TocName=Platform / Configuration Server and GWS settings for Designer
|Context=Learn about the Configuration Server objects and settings required for Designer.
|ComingSoon=No
|Role=Administrator
|Section={{Section
|sectionHeading=Create roles for Designer
|anchor=desroles
|alignment=Vertical
|structuredtext=Designer uses roles and access groups to determine permissions associated with the logged-in user. To enable this, you must make these changes in GAX or CME.

Designer supports a number of bundled roles suitable for various levels of users.

*'''Designer Developer''' - Most users fall into this category. These users can create Designer applications, upload audio, and create business controls. They have full access to Designer Analytics.

*'''Designer Business User''' - These users cannot create objects but they can manage them (for example, upload audio, change data tables, and view analytics).

*'''Designer Analytics''' - These users only have access to Designer Analytics.

*'''Designer Admin''' - These users can set up and manage partitions associated with users and Designer objects.
*'''Designer Operations''' - Users with this role have full access to all aspects of the Designer workspace. This includes the '''Operations''' menu (normally hidden), where they can perform advanced operational and maintenance tasks.

To create these roles, import the '''.conf''' files included in the '''Designer Deployment''' package. They are located in the '''packages/roles/''' folder.

In addition, ensure the following for user accounts that need access to Designer:

*The user must have read permissions on its own Person object.
*Users must be associated with one or more roles via access groups.
*The on-Premises user must have at least read access on the user, access group(s), and roles(s).
*The access groups must have read/write permissions to the Agent Setup folders - Scripts and Transactions.
|Status=No
}}{{Section
|sectionHeading=Create the DesignerEnv transaction list
|anchor=desenv
|alignment=Vertical
|structuredtext=Designer requires a transaction list for configuration purposes as described in other sections of this document. To set this up:

#Create a transaction list called '''DesignerEnv'''.
#Import the file '''configuration/DesignerEnv.conf''', located in the Designer Deployment Manifest package.
#Edit any values according to the descriptions provided in the '''Designer settings''' section.
#Save the list.
#Ensure Designer users have at least read access to the '''DesignerEnv''' transaction list.
|Status=No
}}{{Section
|sectionHeading=Platform settings
|anchor=platset
|alignment=Vertical
|structuredtext=The platform settings listed below must be configured if the Designer application is used for voice calls.
{{{!}} class="wikitable"
{{!}}Component
{{!}}Config Key
{{!}}Value
{{!}}Description
{{!}}-
{{!}}SIP Switch -> Voip Services -> msml service
{{!}}userdata-map-format
{{!}}sip-headers-encoded
{{!}}Option needs to set to pass JSON data as user data in SIPS.
{{!}}-
{{!}}SIP Switch -> Voip Services -> msml service
{{!}}userdata-map-filter
{{!}}*
{{!}}To allow userdata passing to MSML service.
{{!}}-
{{!}} rowspan="7"{{!}}SIPServer --> TServer
{{!}}divert-on-ringing
{{!}}false
{{!}}RONA is handled by the platform.
{{!}}-
{{!}}agent-no-answer-timeout
{{!}}12
{{!}}
{{!}}-
{{!}}agent-no-answer-action
{{!}}notready
{{!}}
{{!}}-
{{!}}agent-no-answeroverflow
{{!}}""
{{!}}No value, empty.
{{!}}-
{{!}}after-routing-timeout
{{!}}24
{{!}}
{{!}}-
{{!}}sip-treatments-continuous
{{!}}true
{{!}}
{{!}}-
{{!}}msml-record-support
{{!}}true
{{!}}To allow routed calls recording via the Media Server.
{{!}}-
{{!}}Switch object annex --> gts
{{!}}ring-divert
{{!}}1
{{!}}
{{!}}-
{{!}}ORS --> orchestration
{{!}}new-session-on-reroute
{{!}}false
{{!}}Required for SIPS Default Routing ([https://intranet.genesys.com/pages/viewpage.action?pageId=55813481 Default Routing handling (Voice)]).
{{!}}-
{{!}}MCP
{{!}}[vxmli] transfer.allowed
{{!}}TRUE
{{!}}Required for Transfer block (allows VXML Transfer in MCP).
{{!}}-
{{!}}MCP
{{!}}[cpa] outbound.method
{{!}}NATIVE
{{!}}Required for Transfer block (allow CPA detection for Transfer ).
{{!}}-
{{!}}UCS
{{!}}[cview] enabled
{{!}}TRUE
{{!}}Enables Customer Context Services.
{{!}}}
|Status=No
}}{{Section
|sectionHeading=GWS configuration
|anchor=gwsconfig
|alignment=Vertical
|structuredtext=Ensure that the following steps are performed in GWS.
====Create Contact Center====
Create a contact center in GWS if it is not already created. Refer to the [https://docs.genesys.com/Documentation/HTCC/8.5.2/API/Welcome GWS documentation] for more information on this.
====Create GWS Client====
Create new GWS client credentials if they are not already created . Refer to the [https://docs.genesys.com/Documentation/HTCC/8.5.2/API/Welcome GWS documentation] for more information on this.
|Status=No
}}
|PEPageType=55cef4ff-9306-4313-8fd8-377282a38478
}}

@@ Line 122: / Line 122: @@
 |anchor=gwsconfig
 |alignment=Vertical
-|structuredtext=Ensure that the following steps are performed in GWS.
+|structuredtext=Ensure that the following steps are performed in GWS:
-====Create Contact Center====
-Create a contact center in GWS if it is not already created. Refer to the [https://docs.genesys.com/Documentation/HTCC/8.5.2/API/Welcome GWS documentation] for more information on this.
+*'''Add Contact Center'''&mdash;Create a contact center in GWS, if it is not already created.
-====Create GWS Client====
+*'''Create API Client'''&mdash;Create new GWS client credentials, if they are not already created.
-Create new GWS client credentials if they are not already created . Refer to the [https://docs.genesys.com/Documentation/HTCC/8.5.2/API/Welcome GWS documentation] for more information on this.
 |Status=No
 }}
 |PEPageType=55cef4ff-9306-4313-8fd8-377282a38478
 }}

@@ Line 33: / Line 33: @@
 |Status=No
 }}{{Section
-|sectionHeading=Create the DesignerEnv transaction list
+|sectionHeading=Update the DesignerEnv transaction list
 |anchor=desenv
 |alignment=Vertical
-|structuredtext=Designer requires a transaction list for configuration purposes as described in other sections of this document. To set this up:
+|structuredtext=Designer requires a transaction list for configuration purposes as described in other sections of this document. The '''DesignerEnv''' transaction list is automatically created in on logging onto Designer.
 #Edit any values according to the descriptions provided in the {{Link-SomewhereInThisVersion|manual=DESPEGuide|topic=Configure|anchor=postdepconf|display text=Post deployment configuration settings reference table}}.
 #Save the list.

@@ Line 40: / Line 40: @@
 #Create a transaction list called '''DesignerEnv'''.
 #Import the file '''configuration/DesignerEnv.conf''', located in the Designer Deployment Manifest package.
-#Edit any values according to the descriptions provided in the '''Designer settings''' section.
+#Edit any values according to the descriptions provided in the {{Link-SomewhereInThisVersion|manual=DESPEGuide|topic=Configure|anchor=postdepconf|display text=Post deployment configuration settings reference table}}.
 #Save the list.
 #Ensure Designer users have at least read access to the '''DesignerEnv''' transaction list.