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; } } }

Differences between TS 6.5 and 6.7?

JessicaD

Question for anyone who has upgraded from TS 6.5 to TS 6.7: Are there any major differences or advantages to using TS 6.7?

Find more posts tagged with

Comments

nipper

User configurable roles are a pretty nice piece of functionality. That, however will not be a quick change to use.

I have it in a dev environment and it is pretty stable, a few bugs but pretty solid.

I do not see a huge quick win in functionality that would make it a slam dunk to push an upgrade. I had thought that search was cross branch, but that is only available in the CSDK and not out of the TS GUI. I really wanted that functionality

HTH

ANdy

gzevin

Question for anyone who has upgraded from TS 6.5 to TS 6.7: Are there any major differences or advantages to using TS 6.7?

I'd say wait till .1, with a hope that new unified tagging/form UI+FormAPI will be there, with the search.

Adam Stoller

I'd say wait till .1, with a hope that new unified tagging/form UI+FormAPI will be there, with the search.

The new workflow UI should be in 6.7.1 (which is my #1 reason for waiting for 6.7.1 instead of upgrading anyone to 6.7.0)

The new tagging UI wasn't given a projected release during GearUp, so while it would be really nice to see it in 6.7.1, I don't think it's coming until a later release (this is one of those cases where I'd love to be proven wrong ;-))

Migrateduser

They've also added the ability to tweak file permissions directly through the GUI. I expect most of us use submit.cfg to automatically set permissions, so there's no great benefit to it, but I reckon it's nice for those people who don't.

nipper

They've also added the ability to tweak file permissions directly through the GUI. I expect most of us use submit.cfg to automatically set permissions, so there's no great benefit to it, but I reckon it's nice for those people who don't.

someone who needs a gui to change permissions should not be working on my system.

Migrateduser

I would guess that they had a requirement from someone to allow end users to change permissions on content through the GUI. I think I could count the number of end users I've met who understand their company's security strategy well enough to manage permissions themselves on one hand.

Johnny

The new workflow UI should be in 6.7.1 (which is my #1 reason for waiting for 6.7.1 instead of upgrading anyone to 6.7.0)

The new tagging UI wasn't given a projected release during GearUp, so while it would be really nice to see it in 6.7.1, I don't think it's coming until a later release (this is one of those cases where I'd love to be proven wrong ;-))

At one point I thought I heard here that 6.7.1 also had the option of TeamSite only user accounts (no need for OS user ID's), but I've since learnt that most probably won't be there until 7.0. That would be a major enhancement.

Adam Stoller

I would guess that they had a requirement from someone to allow end users to change permissions on content through the GUI. I think I could count the number of end users I've met who understand their company's security strategy well enough to manage permissions themselves on one hand.

I'm not sure about the file-by-file change permissions, but the management of roles, groups, and changing permissions on branches and/or workareas is something that often gets bottlenecked in IT departments - case in point, I have a customer who's IT department is outsourced and who's servers are hosted by yet another company -- the TS customer lead knows what he wants done but currently has to go through all sorts of red-tape to get it done (with the exception of adding users to the role files which he can do via the Admin GUI in 6.5) - so these increases in ability to manage roles/groups/permissions/etc through the GUI are useful (though like many of us here, I'd rarely use them unless I had to ;-)

Bhargav Coca

I was wondering if any one have Installed Search 2.0.0 with 6.7? Please let me know if this is compatable?
Thanks

JessicaD

Thanks for the info. Very helpful.

Migrateduser

>>I was wondering if any one have Installed Search 2.0.0 with 6.7? Please let me know if this is compatable?

Yes, Search 2.0.0 is copmatible with TS 6.7

smenon

TS 6.7.1 that is slated for release in Sept. will contain the following features

1) Linux Support (Red Hat ES and AS 4.0 on Intel x86)
2) Localization Support
3) SSO Enhancements
4) SOAP Server Upgrade (and support for SOAP in TS 6.7.0)
5) New Workflow Modeler

Some of the server work around support for TeamSite Users and Running as non-Root for Solaris systems will be done for TS 6.7.1, but the real support for this will be completed as part of the TS 6.7.1 SP1 due in January. The new Tag UI will also be part of the TS 6.7.1 SP1 release. We are also investigating a TPL (PT Compile) alternative for TeamSite Users and when you run as non-root. Because the PT Compilation on TPLs get executed as an OS user (in a shell), this will not be possible to support with impersonation for TeamSite Users (non-OS users). We will continue to support TPLs and PTCompile for OS users as we do today, but for non-OS users, you will have to use the alternative methodology (the current proposal is for a true XSLT based solution run through our servlet container). Also, WF external tasks cannot be run from the command line for non-OS users or if you run the utility daemon as non-root. You will have to use the new URL External Tasks feature that was introduced in TS 6.7.0 for these users.

thanks

boskovuk

Also, WF external tasks cannot be run from the command line for non-OS users or if you run the utility daemon as non-root. You will have to use the new URL External Tasks feature that was introduced in TS 6.7.0 for these users.

Sunil,
could you further elaborate on a relationship between WF external tasks and 'impersonation failure' problem that we are currently experiencing?

This is the error, taken from iwutild.log file:
[Mon Oct 30 15:14:31 2006] Error: Impersonation failure user= SIGNET\WCMSAuthor; argcount=5; errCode=1385; cmd=D:\iw-home/iw-perl/bin/iwperl

\iw-home/local/config/wft/custom/scripts/generate_files.ipl 874 880 \dfait-maeci\main\internet-internet\international-international\international-international\WORKAREA\content-contenu templatedata\pages-pages\generic-generique\data\a

This is our environment:
Windows 2003 Enterprise
TS 6.7.1
MetaTagger 4.1.1

dtheimer

Boskovuk,

I came across your posting when searching for more information on "Impersonation failure" regarding the same error you presented below. Can you provide any additional information on this cause and solution?

Thanks in advance,
%david

Sunil,
could you further elaborate on a relationship between WF external tasks and 'impersonation failure' problem that we are currently experiencing?

This is the error, taken from iwutild.log file:
[Mon Oct 30 15:14:31 2006] Error: Impersonation failure user= SIGNET\WCMSAuthor; argcount=5; errCode=1385; cmd=D:\iw-home/iw-perl/bin/iwperl \iw-home/local/config/wft/custom/scripts/generate_files.ipl 874 880 \dfait-maeci\main\internet-internet\international-international\international-international\WORKAREA\content-contenu templatedata\pages-pages\generic-generique\data\a

This is our environment:
Windows 2003 Enterprise
TS 6.7.1
MetaTagger 4.1.1

boskovuk

Boskovuk,

I came across your posting when searching for more information on "Impersonation failure" regarding the same error you presented below. Can you provide any additional information on this cause and solution?

David,
Our custom workflow, while executing, would trigger this error. This was stopping the workflow execution as well.

The solution we used on our TeamSite was to give the "Log on Locally" user right to TeamSite users (those who need to trigger and use the workflow).

Hope this helps ...

Stacktrace.txt