Difference between revisions of "Draft: RN/AgentWorkspace/100.0.006.0471"
From Genesys Documentation
| Line 5: | Line 5: | ||
|ReleaseDate=2023-05-30 | |ReleaseDate=2023-05-30 | ||
|PrivateEditionReleaseDate=2023-05-30 | |PrivateEditionReleaseDate=2023-05-30 | ||
| − | |Highlight=Resolved | + | |Highlight=Resolved issues. |
}} | }} | ||
{{Issue | {{Issue | ||
| Line 11: | Line 11: | ||
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1 | |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1 | ||
|Content=[WWE][AWS] [Azure]:Agent can now see the consult calls which are not marked done from a previous session or after a refresh. So now when configured and when the agent receives a regular call and marks it done, Agent Workspace can cancel the After Call Work state. Previously in such configuration when consult calls which are not marked done from a previous session or after a refresh, Agent Desktop doesn’t display the consult calls blocking the mechanism to switch from After Call Work state to its former status on mark Done for subsequent calls.[Private]:When *voice.consultation.mark-done-on-release* is set to *false*, Agent can now see the consult calls which are not marked done from a previous session or after a refresh. So now when the agent receives a regular call and marks that done, Agent Workspace can cancel the After Call Work state by setting *voice.cancel-after-call-work-on-done* option to *true*. Previously in such configuration when consult calls which are not marked done from a previous session or after a refresh, Agent Desktop doesn’t display the consult calls blocking the mechanism to switch from After Call Work state to its former status on mark Done for subsequent calls. | |Content=[WWE][AWS] [Azure]:Agent can now see the consult calls which are not marked done from a previous session or after a refresh. So now when configured and when the agent receives a regular call and marks it done, Agent Workspace can cancel the After Call Work state. Previously in such configuration when consult calls which are not marked done from a previous session or after a refresh, Agent Desktop doesn’t display the consult calls blocking the mechanism to switch from After Call Work state to its former status on mark Done for subsequent calls.[Private]:When *voice.consultation.mark-done-on-release* is set to *false*, Agent can now see the consult calls which are not marked done from a previous session or after a refresh. So now when the agent receives a regular call and marks that done, Agent Workspace can cancel the After Call Work state by setting *voice.cancel-after-call-work-on-done* option to *true*. Previously in such configuration when consult calls which are not marked done from a previous session or after a refresh, Agent Desktop doesn’t display the consult calls blocking the mechanism to switch from After Call Work state to its former status on mark Done for subsequent calls. | ||
| − | |LocalContent= | + | |LocalContent=Agents can now see the consult calls that are not marked '''Done''' from a previous session or after a refresh. When this option is configured and when the agent receives a regular call and marks it '''Done''', Agent Workspace cancels the '''After Call Work''' state. Previously, in such configuration, calls that were not marked '''Done''' from a previous session or after a refresh, Agent Desktop did not display the consult calls blocking the mechanism to switch from '''After Call Work''' state to its former status when marked '''Done''' for subsequent calls. <br> |
| + | '''For Private Edition''', set the '''voice.consultation.mark-done-on-release''' option to '''false''' to view the consult calls which are not marked '''Done''' from a previous session or after a refresh. When the agent receives a regular call now and marks it '''Done''', Agent Workspace cancels the '''After Call Work''' state when the '''voice.cancel-after-call-work-on-done''' option is set to '''true'''. Previously, in such configuration, calls that were not marked '''Done''' from a previous session or after a refresh, Agent Desktop did not display the consult calls blocking the mechanism to switch from '''After Call Work''' state to its former status when marked '''Done''' for subsequent calls. | ||
}} | }} | ||
{{Issue | {{Issue | ||
| Line 17: | Line 18: | ||
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1 | |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1 | ||
|Content=[WWE][AWS] [Azure]:Before a phone number is matched with a Dial Plan rule, it will now be formatted to remove unsupported characters. Please contact Genesys to enable this behavior.[Private]:Before a phone number is matched with a Dial Plan rule, it will now be formatted to remove unsupported characters. Use the *voice.dial-plan.format-number-before-match.enable* option to enable this behavior. | |Content=[WWE][AWS] [Azure]:Before a phone number is matched with a Dial Plan rule, it will now be formatted to remove unsupported characters. Please contact Genesys to enable this behavior.[Private]:Before a phone number is matched with a Dial Plan rule, it will now be formatted to remove unsupported characters. Use the *voice.dial-plan.format-number-before-match.enable* option to enable this behavior. | ||
| − | |LocalContent= | + | |LocalContent=Phone number is now formatted to remove unsupported characters before it is matched with a Dial Plan rule. Please contact your Genesys representative to enable this behavior. |
| + | |||
| + | '''For Private Edition''', use the '''voice.dial-plan.format-number-before-match.enable''' option to format the phone number to remove unsupported characters before it is matched with a Dial Plan rule. | ||
}} | }} | ||
{{Issue | {{Issue | ||
| Line 23: | Line 26: | ||
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1 | |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1 | ||
|Content=[WWE]:[AWS] [Azure]:Agent Workspace an now consider the "ReplyToAddress" field from the parent inbound email to populate the "To" address field of the outbound reply email. Contact your Genesys Representative to enable this functionality.[Private]:Agent Workspace an now consider the "ReplyToAddress" field from the parent inbound email to populate the "To" address field of the outbound reply email. Use the *email.reply.use-reply-to-address* option to enable this behavior. | |Content=[WWE]:[AWS] [Azure]:Agent Workspace an now consider the "ReplyToAddress" field from the parent inbound email to populate the "To" address field of the outbound reply email. Contact your Genesys Representative to enable this functionality.[Private]:Agent Workspace an now consider the "ReplyToAddress" field from the parent inbound email to populate the "To" address field of the outbound reply email. Use the *email.reply.use-reply-to-address* option to enable this behavior. | ||
| − | |LocalContent= | + | |LocalContent=Agent Workspace can now consider the '''ReplyToAddress''' field from the parent inbound email to populate the '''To''' address field of the outbound reply email. Contact your Genesys Representative to enable this functionality. |
| + | |||
| + | '''For Private Edition''', use the '''email.reply.use-reply-to-address''' option to enable to consider the '''ReplyToAddress''' field from the parent inbound email to populate the '''To''' address field of the outbound reply email. | ||
}} | }} | ||
{{Issue | {{Issue | ||
| Line 29: | Line 34: | ||
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1 | |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1 | ||
|Content=[WWE][AWS] [Azure]:The *emergency* mode disabling Caller Id and most of all routing capabilities by the *Dial Plan of Agent Workspace* can now fully ignore all routing configurations to dial directly matching numbers. Please contact Genesys to enable this behavior.[Private]:Setting the '*emergency*' parameter in a Dial Plan rule of Agent Workspace can now fully ignore all routing configurations to dial directly matching numbers. Earlier, this parameter would ignore any routing points configurations but still consider targets and actions that have been configured for routing. Use the *voice.dial-plan.emergency.ignore-routing.enable* option to enable this behavior. | |Content=[WWE][AWS] [Azure]:The *emergency* mode disabling Caller Id and most of all routing capabilities by the *Dial Plan of Agent Workspace* can now fully ignore all routing configurations to dial directly matching numbers. Please contact Genesys to enable this behavior.[Private]:Setting the '*emergency*' parameter in a Dial Plan rule of Agent Workspace can now fully ignore all routing configurations to dial directly matching numbers. Earlier, this parameter would ignore any routing points configurations but still consider targets and actions that have been configured for routing. Use the *voice.dial-plan.emergency.ignore-routing.enable* option to enable this behavior. | ||
| − | |LocalContent=The '''emergency''' mode disabling Caller Id and most of all routing capabilities by the '''Dial Plan of Agent Workspace''' can now completely ignore all routing configurations to dial directly matching numbers. Contact Genesys to enable this behavior. | + | |LocalContent=The '''emergency''' mode disabling Caller Id and most of all routing capabilities by the '''Dial Plan of Agent Workspace''' can now completely ignore all routing configurations to dial directly matching numbers. Contact your Genesys Representative to enable this behavior. |
| − | For Private Edition, use the '''voice.dial-plan.emergency.ignore-routing.enable''' option Dial Plan rule of Agent Workspace to completely ignore all routing configurations to dial directly matching numbers. Previously, this parameter would ignore any routing points configurations but still considered targets and actions that were configured for routing. | + | '''For Private Edition''', use the '''voice.dial-plan.emergency.ignore-routing.enable''' option Dial Plan rule of Agent Workspace to completely ignore all routing configurations to dial directly matching numbers. Previously, this parameter would ignore any routing points configurations but still considered targets and actions that were configured for routing. |
}} | }} | ||
{{Issue | {{Issue | ||
| Line 37: | Line 42: | ||
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1 | |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1 | ||
|Content=[WWE]:[AWS][Azure][Private]:Now, the predefined sounds which can be configured in different options, are preloaded when starting the Agent Workspace. It will reduce the delay when a tone is played for the first time during the agent session. | |Content=[WWE]:[AWS][Azure][Private]:Now, the predefined sounds which can be configured in different options, are preloaded when starting the Agent Workspace. It will reduce the delay when a tone is played for the first time during the agent session. | ||
| − | |LocalContent=The predefined sounds which can be configured in different options | + | |LocalContent=The predefined sounds which can be configured in different options are now preloaded when starting the Agent Workspace. This reduces the delay when a tone is played for the first time during the agent session. |
}} | }} | ||
Revision as of 13:00, May 29, 2023
This is a draft page; it has not yet been published.
Component RN Definition[edit source]
| Component | Agent Workspace |
|---|---|
| Deployment Type | Genesys CX on AWS, Genesys CX on Azure, Private Edition |
| Release Number | 100.0.006.0471 (Change release number) |
| Release Type | |
| Highlight | Resolved issues. |
| Boilerplate(s) Used | |
| Release Date | 2023-05-30 |
| Private Edition Release Date | 2023-05-30 |
| Mixed Mode Release ReleaseDate | |
| Private Edition Containers List | |
| JQL | project = WWE AND labels = wwe-may-23 ORDER BY created DESC |
| Links | Links to customer-facing pages in use: |
| Test Links | Links to test pages (for RN Admins only) |
No results