https://all.docs.genesys.com/index.php?action=history&feed=atom&title=RN%2FAgentWorkspace%2F100.0.001.0113 2026-04-21T12:32:40Z Revision history for this page on the wiki MediaWiki 1.31.1 https://all.docs.genesys.com/index.php?title=RN/AgentWorkspace/100.0.001.0113&diff=130786&oldid=prev 2022-11-30T12:00:35Z

<p>Created page with &quot;{{ComponentRN |ComponentId=acaca529-aedd-4820-8557-4966ab8490db |JQL=labels = &quot;wwe-december-22&quot; |DeploymentTypeId=8b480b3c-2733-433a-9166-eab2c2d0663a |ReleaseDate=2022-11-30...&quot;</p> <p><b>New page</b></p><div>{{ComponentRN<br /> |ComponentId=acaca529-aedd-4820-8557-4966ab8490db<br /> |JQL=labels = &quot;wwe-december-22&quot;<br /> |DeploymentTypeId=8b480b3c-2733-433a-9166-eab2c2d0663a<br /> |ReleaseDate=2022-11-30<br /> |PrivateEditionReleaseDate=2022-11-30<br /> |Highlight=Resolved issues and improvements.<br /> }}<br /> {{Issue<br /> |TicketNumber=WWE-2395<br /> |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1<br /> |Content=[WWE]:[Private]:[IX Text]: In Agent Workspace, WebRTC agents can now correctly retrieve a call in a ringing state. Previously, when the WebRTC agent tries to retrieve a call in a ringing state, the music in queue or ringback tone was not heard by the agent.[Dev Text]: Previously for WebRTC agents, when the agent tries to retrieve a call in ringing state, the music in queue or ringback tone was not heard by the agent.Now, Agent Workspace correctly handles such scenario.<br /> |LocalContent=In Agent Workspace, WebRTC agents can now correctly retrieve a call in a ringing state. Previously, when the WebRTC agent tries to retrieve a call in a ringing state, the music in queue or ringback tone was not heard by the agent.<br /> }}<br /> {{Issue<br /> |TicketNumber=WWE-2247<br /> |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1<br /> |Content=[WWE][Private]:[IX Text]: The *End call* button is now enabled when a call is placed back to the agent whose previous call wasn’t marked as *Done*. Previously, in such scenarios, the *End Call* button was disbaled.The *End call* button is now enabled when a call is back to the agent and it wasn’t marked as Done.<br /> |LocalContent=The '''End call''' button is now enabled when a call is placed back to the agent whose previous call wasn’t marked as '''Done'''. Previously, in such scenarios, the '''End Call''' button was disabled.<br /> }}<br /> {{Issue<br /> |TicketNumber=WWE-2155<br /> |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1<br /> |Content=[WWE][Private]:For an Outbound Campaign call, the disposition is now correctly saved in the outbound record when it is dialed again using the *Party Action* menu.<br /> |LocalContent=For an Outbound Campaign call, the disposition is now correctly saved in the outbound record when it is dialed again using the '''Party Action''' menu.<br /> }}<br /> {{Issue<br /> |TicketNumber=WWE-2126<br /> |IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72<br /> |Content=[WWE][Private]:[IX Text]:In SIP environments that use PSTN devices, the following options are no longer available to enforce call answering through PSTN devices instead of Agent Workspace.* Option for auto answer (voice.auto-answer)* Option to display the *Answer* button (privilege.voice.can-answer-call)[Dev Text]: In SIP environment using PSTN devices, answering the call must be done from the device and not from Agent Workspace. As a result, settings for auto answer(voice.auto-answer) and to display the *Answer* button(privilege.voice.can-answer-call) will not be applicable anymore.<br /> |LocalContent=In SIP environments that use PSTN devices, the following options are no longer available to enforce call answering through PSTN devices instead of Agent Workspace.<br /> <br /> *Option for auto answer (&lt;code&gt;voice.auto-answer&lt;/code&gt;)<br /> *Option to display the '''Answer''' button (&lt;code&gt;privilege.voice.can-answer-call&lt;/code&gt;)<br /> }}</div>

WikiSysop