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

Difference in Teamsite 5.5.2 and Teamsite 6.7.1

azhagi

Can anyone please list out the new feature of Teamsite 6.7.1 when compared to TS 552?
Like any new functionalites in DCT or Form API or TPL or Open Deploy or Data Deploy or New Teamsite Perl Modules .....................

thanks in advance.

Find more posts tagged with

Comments

kaalraa

Can anyone list out the new feature of Teamsite 6.7.1 when compared to
TS 552?
Like any new functionaliteies in DCT or Form API or TPL or Open Deploy or Data Deploy or New Teamsite Perl Modules .....................

thanks in advance.

You are asking to provide differences between Windows 95 and XP. Smiley Very Happy

azhagi

good joke Sir....

Actually we want to do a migration .
Need to know whether all the code in TS 552 will work in TS 671 with out giving any issue at any point of time.

My previous post is to fine tune the existing TS 552 code.Still the answer for my fisrt post is very much appriciated.

thanks in advance.

DhirajJha

Can anyone list out the new feature of Teamsite 6.7.1 when compared to
TS 552?
Like any new functionaliteies in DCT or Form API or TPL or Open Deploy or Data Deploy or New Teamsite Perl Modules .....................

thanks in advance.

Hi Azhagi,
You have to take pain of reading all the release notes post TS 5.5 release and then you might get your answer as nobody will take this pain for you and nobody remembers all the changes on the finger tips as there are intermediate releases.

Thanks,
DJ

kaalraa

good joke Sir....

Actually we want to do a migration .
Need to know whether all the code in TS 552 will work in TS 671 with out giving any issue at any point of time.

My previous post is to fine tune the existing TS 552 code.Still the answer for my fisrt post is very much appriciated.

thanks in advance.

The biggest change within your TS versions is the format change of the backing store.

Moreover, what comes to the top of my mind:
1. Instead of Upgrade, you need to do a fresh installation.
2. Fresh Installation requires more manual copy and migration steps
3. Should not be platform change. i.e. Unix to Windows or Vice-versa
4. It has many changes related to Templating, Workflows and TS GUI.

Last, the most important... Contact Interwoven Support for an impact and upgrade planning analysis. Better to go with a reviewed plan. Smiley Happy

azhagi

Thanks a lot kaalraa....

Consider that the data (store) migration is done properly.
Need to know whether all the code and Interwoven functionalities available in TS 552 will work in TS 671 with out giving any issue.

Thanks in advance.

CreateScriptedDataSetForChart.zip

Adam Stoller

Thanks a lot kaalraa....

Consider that the data (store) migration is done properly.
Need to know whether all the code and Interwoven functionalities available in TS 552 will work in TS 671 with out giving any issue.

Thanks in advance.

There are, as one would expect in an N-year gap, a considerable amount of changes - Some code will continue to work as-is, some code won't. There are a number of enhancements that you will not be able to take advantage of without re-writing some code or configuration files.

This is why you should start out with a fresh server and expect it to be in "dev" mode for at least 1 month in order to figure out what needs to be fixed in order to work with the newer system.

Among the things I can think of off the top of my head - any code that relies or queries roles (what used to be in conf/roles/*.uid files) will need to be rewritten; any CCI URIs used should probably be replaced with the new CCI URIs; the configuration of custom menu items is completely changed and will need to be configured according to the new paradigm.

WFTs should continue to work as-is, though some of the externaltask or cgitask code may need to be re-visited.

DCTs and PTs should continue to work as-is (unless you're planning to use non-OS users) - but you won't be able to take advantage of enhancements that may have been made since they were written unless you change them too.

I'd look at it as an opportunity to "clean up" - and plan for a 3-6 month transition (you've waited this long to upgrade, what's another 3-6 months?)

azhagi

Hi,

Thanks a lot for mentioning the particular aspects where we have to be careful during updation.

Adam Stoller

Hi,

Thanks a lot for mentioning the particular aspects where we have to be careful during updation.

Note - those aren't necessarily all the things you have to be careful about - just the ones I could think of off the top of my head. Assume the worst and hope for the best.

azhagi

Hi,

In your reply have a doubt.

you gave a statement like "any CCI URIs used should probably be replaced with the new CCI URIs".

Please tell exactly what URIs we have to take care.

thanks in advance.

azhagi

Adam Stoller

Hi,

In your reply have a doubt.

you gave a statement like "any CCI URIs used should probably be replaced with the new CCI URIs".

Please tell exactly what URIs we have to take care.

thanks in advance.

In your questions I have doubt - please read the manuals - ALL OF THEM. Or hire someone who's been through this kind of thing and will be able to get you through the process of upgrading with more ease than you obviously will by yourself.