Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
6.1 WebDeskPro NOT identical to 5.5.2 version
Bill Klish
Not sure if anyone else has experienced this but we are in the process of planning for a TeamSite 6.1 upgrade and were counting on keeping all existing users on WebDeskPro until they can schedule training on 6.1, and have new users use 6.1.
In some informal testing, as noted in some of my other posts, things really aren't identical.
For instance, the New Data Record menu choice has been replaced by New Form Entry. This causes the 6.1 templating window to come up, not the familiar 5.5.2 interface everyone is accustomed to. Also, the templating window is now controlled by the wizard driven actions used in CC Std. Is the 5.5.2 Templating Interface no longer provided?
Similarly, the Metadata Capture window that appears is not the familiar 5.5.2 version, but the 6.1 Tagger GUI is loaded.
This is going to cause confusion for our existing user community.
Has anyone else experienced this or know a way around this?
Test Server = Windows 2003, TeamSite 6.1 SP1
Find more posts tagged with
Comments
Adam Stoller
Nope - they're not identical because the underlying system changed.
You only have access to the 6.x Forms Entry interface - there is no more pre-6 TeamSite Templating interface.
You only have access to the Tagger GUI - the old OOTB metadata capture UI is no longer there (as far as I know).
Basically, the WDP interface is there for *familiar* but not *identical* UI - to move towards the transition.... (I won't claim whether this is a good or bad thing, well thought out or not thought out - just that it's what's there for better or worse)
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com
B80116
We recently upgraded from 5.5.2 to 6.1, and most of our users are still using the WebDeskPro interface. There was some initial confusion and grumbling regarding the new Forms Entry interface, but they seemed to get the hang of it quickly. I think the transition from WebDeskPro to ccStandard is going be a lot more confusing for our users.
gzevin
yes, this is how we are planning to do as well.
We have prepared a 'difference' document that otlines changes in the UI, and, fingers crossed, everything should be fine.
one thing is, as I might have mentioned in a different topic, one HAS to check every DCT as they could some issues with rendering/behaviour of elements - and also, CGI callouts need to be modified....
Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU