Backend Server service:wmsg Section
Contents
- 1 Backend Server service:wmsg Section
- 1.1 wmsg.connector.engagementExpirationTime
- 1.2 wmsg.connector.registrationFormExpirationTime
- 1.3 wmsg.connector.interactionServer.autoStopWebengagementIntr
- 1.4 wmsg.connector.interactionServer.queueAccepted
- 1.5 wmsg.connector.interactionServer.queueEngaged
- 1.6 wmsg.connector.interactionServer.queueFailed
- 1.7 wmsg.connector.interactionServer.queueQualified
- 1.8 wmsg.connector.interactionServer.queueRejected
- 1.9 wmsg.connector.interactionServer.queueTimeout
- 1.10 wmsg.connector.defaultEngagementChannel
- 1.11 wmsg.connector.userIdentifier
- 1.12 wmsg.connector.phoneNumber
wmsg.connector.engagementExpirationTime
Default Value: 30
Valid Values: 10 — 60
Changes Take Effect: Immediately
Specifies the time, in seconds, during which the webengagement interaction is considered to be valid. This time is applicable for the webengagement interaction from the time the interaction is created until the moment the enagagement invitation is displayed to the visitor.
wmsg.connector.registrationFormExpirationTime
Default Value: 120
Valid Values: 10—1800
Changes Take Effect: Immediately
Specifies the time, in seconds, during which the registration form is considered to be valid when waiting for the form to be completed by the visitor.
If the registration form is not completed before the expiration time, the engagement attempt is considered invalid. Note: Even after this period, the visitor is able to trigger a chat or voice interaction, but is also able to receive one more engagement invite.
wmsg.connector.interactionServer.autoStopWebengagementIntr
Default Value: true
Valid Values: true, false
Changes Take Effect: Immediately
A Boolean that configures whether or not a webengagement OM interaction is stopped right after being placed in a terminal queue (Accepted, Rejected, Timedout, Failed). If true, the interaction will be stopped after being placed in a terminal queue.
wmsg.connector.interactionServer.queueAccepted
Default Value: Webengagement_Accepted
Valid Values: Letters A to Z and a to z. Numbers 0 through 9. The underscore and space characters.
Note: The specified value must be the name of the the Interaction Queue object as provisioned in Configuration Manager.
Changes Take Effect: Immediately
A valid name of a queue used for accepted interactions. An interaction is placed in this queue if the visitor accepts the engagement proposal (the disposition code is set to acceptCall); Genesys Web Engagement then stops the interaction.
wmsg.connector.interactionServer.queueEngaged
Default Value: Webengagement_Engaged
Valid Values: Letters A to Z and a to z. Numbers 0 through 9. The underscore and space characters.
Changes Take Effect: Immediately
A valid name of a queue used for engagement interactions. An interaction is placed in this queue after a positive engagement decision is made in the Engagement Logic SCXML strategy. The interaction usually is not stopped until it is located in this queue.
wmsg.connector.interactionServer.queueFailed
Default Value: Webengagement_Failed
Valid Values: Letters A to Z and a to z. Numbers 0 through 9. The underscore and space characters.
Changes Take Effect: Immediately
A valid name of a queue used for failed engagement interactions. An interaction is placed in this queue in three cases:
- If its disposition code is set to timeout.
- If the interaction was cleaned from another queue.
- If the Orchestration Server strategy notified the Backend Server that the interaction should not be processed to the real engagement.
Web Engagement Backend Server stops the interaction as soon as it is placed in the Failed queue.
wmsg.connector.interactionServer.queueQualified
Default Value: Webengagement_Qualified
Valid Values: Letters A to Z and a to z. Numbers 0 through 9. The underscore and space characters.
Changes Take Effect: Immediately
A valid name of a queue used for creating engagement interactions. Each time Genesys Web Engagement creates an interaction, the new interaction is added to this queue. The interaction is not stopped until it is located in this queue.
wmsg.connector.interactionServer.queueRejected
Default Value: Webengagement_Rejected
Valid Values: Letters A to Z and a to z. Numbers 0 through 9. The underscore and space
Changes Take Effect: Immediately
A valid name of a queue used for rejected engagement interactions. An interaction is placed in this queue if the visitor rejects the engagement proposal (the disposition code is set to reject); Genesys Web Engagement then stops the interaction.
wmsg.connector.interactionServer.queueTimeout
Default Value: Webengagement_Timeout
Valid Values: Valid Values: Letters A to Z and a to z. Numbers 0 through 9. The underscore and space
Changes Take Effect: Immediately
Description: Specifies the name of the Interaction Queue where the webengagement iteraction is placed after a visitor's browser sends the Timeout disposition code for the engagement invitation.
wmsg.connector.defaultEngagementChannel
Default Value: N/A
Valid Values: proactiveChat, proactiveCallback
Changes Take Effect: Immediately
A valid name for the default Engagement Channel. When specified, this option turns off detection of an agent's availability by the pacing service. The specified value is selected for engagements by the out-of-the-box Engagement Logic SCXML strategy.
wmsg.connector.userIdentifier
Default Value: EmailAddress
Valid Values: A valid User Data key
Changes Take Effect: Immediately
Description: Specifies the name of the User Data key that is used by Contact Server as the key for the customer identification process. This is the primary key for the Identity object in Genesys Web Engagement.
wmsg.connector.phoneNumber
Default Value: PhoneNumber
Valid Values: A valid User Data key
Changes Take Effect: Immediately
Description: Specifies the name of the key that is used by Interaction Workspace to obtain the phone number from the interaction's User Data.