nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

TeamSite 6.0 -- How's it going?!!!

rsearle

Hi, I'm considering upgrading from TeamSite 5.0 to 6.0

(I'm not migrating the backing store)

Should I wait 'till 6.1 comes out?!!!

Find more posts tagged with

Comments

Migrateduser

Should you wait till 6.1? YES!

There's no way we would put 6.0 into our production server. Definitely install 6.0 on a dev server, but I don't know of any company that has 6.0 in production.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

JeremyH

Has iwov given us a date for 6.1 yet? Out users are anxious for an upgrade; however, I've never seen a stable .0 release.

gzevin

frankly, TS 6 is stable enough as it still uses TS 5.5.2 server. As far as the UI is concerned, I'd wait till the major (pre-6.1) patch that will come soon.

However, if you have never used TS6 before, I'd put it on a development server and give your staff some time to get used to it. Docs need to be changed. Also, one would benefit from having everyting validated before going to production

In general, I'd say that the quality of the release this time was a bit better than I got used to.

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

ReggieRWalker

I was told by an IWOV salesman that 6.1 is not scheduled until March 2004. IWOV is however releasing a "6.0L" later in December, but that most of the changes were related to internationalization efforts.

Migrateduser

Just to give another perspective, we do have a few customers in production with TS 6.0. Just as with any .0 release, it does have some issues, but those issues have not been enough for these customers to go with TS 6.0 because of all of the benefits that it gives their users with the improved ease of use and performance improvements.

Just so you know, there has already been a patch issues for TS 6.0 that addresses the most serious issues found thus far with TS 6.0.

That being said, the vast majority of our customers have already begun playing with TS 6.0 in their development environments. The TS 6.0 user experience is vastly different than WebDesk Pro. Furthermore, we give you an extensible, flexible way to customize the user interfaces (but a completely new way of doing it) using the ContentServices UI Toolkit.

So this is what I would do if I were you.

1. Install TS 6.0 today on a development server.
2. Test out your templates, workflows, etc. to ensure that you dont have to make any tweaks. You shouldn't have to, but its always good to test.
3. Decide for yourself if it is production ready, if yes, then go live on TS 6.0, if not, then wait
4. Do user acceptance testing, strategize about how to take advantage of the customizable help, portlets, tabs, etc. These are all new tools available at your fingertips, you should make use of them to strengthen your TS implementation.
5. If you haven't gone in production by the time TS 6.1 comes out, do so.

The ETA for TS 6.1 is Q1.

Thanks,
David Yun

Product Manager, Client Tools
dyun@interwoven.com

nipper

>So this is what I would do if I were you.

>1. Install TS 6.0 today on a development server.
>2. Test out your templates, workflows, etc. to ensure that you dont have to make any tweaks. You shouldn't have to, but its always good to test.
>3. Decide for yourself if it is production ready, if yes, then go live on TS 6.0, if not, then wait
>4. Do user acceptance testing, strategize about how to take advantage of the customizable help, portlets, tabs, etc. These are all new tools available at your fingertips, you should make use of them to strengthen your TS implementation.
>5. If you haven't gone in production by the time TS 6.1 comes out, do so.

The problem with this approach is that we have continual deployment going on. THere is no way I can take my dev server out of commission to play with 6.0.

So I cannot even THINK about 6.0 without waiting until this summer when A. I think it will be stable and B. when there is a long enough gap in our schedule to allow this.

If IW really wants people to move to 6.0, you should allow 30 day test drive on another system.

#FLAME_OFF

Andy

gzevin

Andy,

I agree with you. At my present client we have an unlimited license and therefore I could afford to install 6 on a third box. However, for those of you guys who have a standard 2-host environment, I find it too dificult to proceed. And, as usual, Interwoven comes in asking to purchase a 'developer suite' that'll cost you around a few grand again. This is where the wind blows from Smiley Happy

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

msrich

Anyone have any further info on availability of W2K TS 6.1?

Has Interwoven said anything official about February or March of 2004 for the release of 6.1?

msrich

Dave -- what about W2K TS 6 + Jumbo Patch? Any more stable than TS 6.0 base?

Migrateduser

I don't know anything about Windows versions of TeamSite. All I know is that we have way too much at stake to risk moving to a dot zero version that is so drastically different and is still, in my opinion, in beta since the actual beta testers didn't have all the info they needed to test the thing out thoroughly. You may feel it's good enough to put into production. Not a chance for us.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Document.PNG

Story.PNG

msrich

Dave: Have you seen this?

https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=50852

What do you make out of this? Any idea why the old interface is there?

Migrateduser

Marc,

The WebDesk Pro interface was included in the 6.0 release of TeamSite so that users could make a gradual transition from WebDesk Pro to ContentCenter Pro. Some users can begin training and experimenting with CC Pro while other are still working with WDP.

It also reduces the risk of upgrading to the new UI. If users run into a show-stopper problem, they can retreat to the comparative safety of WebDesk Pro.

Brinko Kobrin
Interwoven Staff Engineer

Migrateduser

It was a smart move to keep the old interface available in 6.0 actually. Because the new interfaces are so drastically different, if they didn't keep the old UI available, it might disturb some people who need to gradually move people over. I can't imagine a lot of people would use it, but it's nice to know it's there.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

gzevin

Still, only the old grey screen has been retained.

If you do templating, etc, you will not get the old (from TS %) forms - the new ones!
so, if you used some button diablers, etc from FormAPI, you need to recheck it again...

lucky you Dave you don't use templating at all Smiley Happy

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

Migrateduser

We like to think of it as "forward thinking" - we knew Templating would bite us if we used it. Smiley Happy

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

gzevin

another thing actually taht I've noticed.

In a separate topic I asked about the search metadata screen in TS 6.

Guess what? this functionality does not exist in 6! That is, you can use the old CGI, if you use the grey screen (or probably one could use the adaptor to tie it up with TS 6 menus). That's it. No new screens yet.

We are now going to be in a damage control mode with some of our users as we move to TS 6. Lucky we, not that many people used metadata search....

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

Gregg Faus

My biggest challenge w/ TS 6.0 has been with templating too. The wizard approach is fine for corporate customers that use Content Center exclusively, but I use a combination of URL commands (CCI's) to interface with the templating.

I just think that the wizard lacks customization. I've put in 3 feature requests (tracked as 50618, 50619, 50621) that relate to extending the way templating forms can interact with workflow. I prefer the approach in 5.0+ where you just simply save/close and workflow handles all the page generation, workflow picking, etc...

gzevin

IWOV says the wizard customisation will come in 6.5

However, as usual, I'd prefer to either HAVE the tool, or don't have it at all. I mean the wizard. It lacks customisations, for sure. I.e. the simplest one would be the ability to add/remove some steps based on (at least) branch...

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

Gregg Faus

Yeah I could see that wizard customization options to be a major code endevour that would warrant a 6.5 release. I'm just crossing my fingers that IWOV implements some basic customizations (i.e. turn off wizard) in 6.1+.

AlanChu

We are a windows shop. The main reason that we are planning to go 6.0 is because CS2.0 requires it. The experience with 6.0 is so far so good. However, I am having hard time to find a thorough documentation for the CS 2.0 API.

Anyone have successful experience using CS2.0? What platform do you use? Java or .Net?

Alan

bradp

Hi,

We are using TeamCode 1.1 with IBM's WSAD 5.0. Are there any plans to develop a compatible version of TeamCode for TS 6 ?

Brad Pridgeon

Edited by bradp on 01/22/04 07:02 AM (server time).

Migrateduser

Hi Brad,

Sorry, there are no plans at this time for a TeamCode for TeamSite 6. Please contact Technical Support for more information.

Thanks,
Todd

Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

Migrateduser

>Yeah I could see that wizard customization options to be a >major code endevour that would warrant a 6.5 release. I'm >just crossing my fingers that IWOV implements some basic >customizations (i.e. turn off wizard) in 6.1+.

I filed a similiar feature request myself. I would like the option to at least disable the wizard from CC Std. and simply have a tt_data workflow launch.

Tom Wentworth
Interwoven Sales Engineer

Edited by twentworth22 on 01/30/04 05:47 AM (server time).

gzevin

Tom,

the best thing should be the ability to configure the wizard at least on the branch level. E.g. we have a couple of branches that do not use metadata capture, while for the rest it's compulsory.

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU