Ring tone in Interaction Workspace

[Adam_W]

I see them too, in 8.1.200.25 and 8.1.3.

Are you just seeing this issue in 8.1.3?

[PFCCWA]

By giving administrator rights?

[Adam_W]

No, I've basically created a role for IWS with most privileges enabled and have assigned the role to the "Users" access group.

Does your access group definitely have the required access to agent logins, agent groups etc as per the IWS Deployment Guide (section "Configuring System-Access Permissions")?

[PFCCWA]

thanks guys.
I added the access group as read only to the host of the statserver and can now view the tabs.
In addition read only permissions was enabled on the statserver itself.

[Adam_W]

Going back to the ClickOnce deployment issues I'm having with IWS 8.1.3, I've received a response from Genesys:

[quote]
The root cause is that Interaction Workspace 8.1.3 is now built in 32-bit mode only, which broke binary compatibility with universal 32/64 bit 8.1.2. This was done to limit memory consumption on 64-bit platforms. However, it is not possible to directly upgrade from 8.1.2 to 8.1.3. For now the only solution is to uninstall 8.1.2 before installing 8.1.3.
However, ER is still with Engineering, maybe they'll reconsider their decision.
[/quote]

So basically I have to uninstall and reinstall the application on every PC, making the ClickOnce functionality pointless 

[PFCCWA]

Ive done a direct upgrade from 8.1.2 to 8.1.3 on a pc without having to uninstall the older version first...

Are you sure they dont mean uninstall through clickdeployment first then install?
ive not tried this functionality yet but looks like genesys are releasing too fast without full testing...

[Adam_W]

Yeah it works OK if I upgrade locally on the PC, but not via the ClickOnce server.

What should happen is:

1.  I upgrade the ClickOnce deployment package on the server
2.  Agent clicks the icon on their desktop
3.  Application detects the new version and deploys it to their PC

It fails to detect the new version though because it thinks the package on the server is corrupt, for the reasons that Genesys have given.

You're right about lack of testing unfortunately.  I think I'll be advising customers to wait until a x.5 release in future rather than x.1.