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

What are the differences between TS6.7.1 and TS7.3.1?

kkumar

What are the differences between TS6.7.1 and TS7.3.1.

Am I correct that:
1)Live site included
2)WFM used in place of classic workflow
3)Two stores used one for teamsite and one for SP

Find more posts tagged with

Comments

Garth McMillan

We are currently upgrading from 6.7.2 SP2 to 7.3.1.

LiveSite is included, though we had it with 6.7.2 as well
WFM is now web based, though pretty much the same as in 6.7.2
There are not separate stores, by default. The SitePublisher/LiveSite sites reside in the same store.

kkumar

Thanks for response Zaarin.

mart2001

I wouldn't say that LiveSite is included. You would need to distinguish between LiveSite Content Services Authoring(LSCS) and LiveSite Display Services (LSDS).
LSCS will require you get another license in order to make use of the LSCS. You can use LSDS out of the box (no need for an extra license).

They don't call Content Standard Interface Content Standard anymore. They renamed it to TeamSite Interface. The Professional Interface still remains. The Administration tab is removed, now make into a link onto the top right hand corner. You can do more with the new Admin Interface, view logs, rotate logs, update config files, view opendeploy deployments, schedule deployment, etc...

As mention earlier, Workflow Modeler is now web based.. So if you didn't save your workflow changes and your browser crash.... Also makes it harder to edit workflows since it is contained within the browser instead of an external application...

Still basic stores.. Your default to hold your content unless you renamed that store. iwadmin to store workflow modeler files, sitepublisher components and templates, workflow modeler instantiation files, workflow modeler config files... iwadmin store will not count against your license for number of content stores...

But you do get a new interface!

Adam Stoller

[...]
As mention earlier, Workflow Modeler is now web based.. So if you didn't save your workflow changes and your browser crash.... Also makes it harder to edit workflows since it is contained within the browser instead of an external application...
[...]

The new (7.3.1) WFM uses JSON files rather than IPM files (though it still creates the latter and apparently, from the server-side, can still process them). When you save-to-disk a WFM, it creates a ZIP file that contains the IPM, JSON, and default.cfg files - but if you want to open a file that was saved-to-disk, you need to crack open the zip file and reference the JSON file only.

There are a number of aspects of the new WFM that are nicer than the old WFM, but there appear to be some issues as well (some may be specific to the browser / browser-version being used - unclear).

On the whole, I think the new WFM is better than the old WFM - but I still like WFTs with TeamSite::WFconstructor personally ;-)

Rick Poulin

I wouldn't say that LiveSite is included. You would need to distinguish between LiveSite Content Services Authoring(LSCS) and LiveSite Display Services (LSDS).

To clarify, neither of those is provided unless you've paid for them. SitePub may be in there for free though, since they're pushing it, but it's hard to keep track.

They don't call Content Standard Interface Content Standard anymore. They renamed it to TeamSite Interface.

They didn't rename CCStd. They added a new interface which is intended as the 'preferred' interface for authors. There are no plans to remove CCStd anytime soon because some clients have customized it quite a bit. They just won't be adding any new functionality to it.

One more important change is that Tomcat has been replaced with JBoss under the hood. Doesn't change functionality, but it changes your troubleshooting and administrative processes w.r.t. application monitoring and support.

Adam Stoller

They didn't rename CCStd. They added a new interface which is intended as the 'preferred' interface for authors. There are no plans to remove CCStd anytime soon because some clients have customized it quite a bit. They just won't be adding any new functionality to it..

They may not have removed it, but they seem to have removed / replaced the link for it in the UI.

When I login to CCpro, I have an option / link in the upper-right hand side to switch to the "TeamSite" view, where I used to have an option to switch to the "CCStd" view - but the latter option no longer exists.

It's still listed as an option in the Admin UI when you add a User (I even have it checked for "User interface access" on my account) - but it doesn't show up as an option in the UI anymore (not that I really care, personally I never liked CCStd)

Rick Poulin

Strange.. The CCStd link shows up just fine for me in the top right, for all users and from both the Admin console and CCPro (doesn't show up in the iw-teamsite UI though).

TS 7.3.1 both unpatched and Patch1 servers on Win2k8 x64.

Sailesh

Hi,

Apart from 6.7.1 to 7.3.1 there are also key changes from 7.1 to 7.3.1 like Smiley Tongue

1. Better dependency management
2. Branch specific LSCS deployment.

By the way I totally agree with Adam that WFT was really good, not sure what benefits we are getting out of WFM.

nico

Also VisualFormat is completely gone, its all TinyMCE from what I've read. We tried to move to TinyMCE in the past and it hosed all the formatting when someone tried to edit a page so the end user had to reformat everything so this worries me.

I'm still not clear about the SitePublisher cost, in the recent upgrade webinar they said it was included now with TS.

Programmatically is there a big difference in creating basic dct's or pt's?

We have a very tiny site with a handful of content contributors and are weighing how quick and easy an upgrade would be from 675 to 7.x on win.

Bowker

What version of TinyMCE comes with TS 7.3.1? The version with 7.2.1 was/is really old and was causing us some issues.

nipper

SitePub is installed automatically but your license key must activate it. That has to be purchased from A/I. Migration may not be that hard but it is different.

Rick Poulin

What version of TinyMCE comes with TS 7.3.1? The version with 7.2.1 was/is really old and was causing us some issues.

3.1.2, same as in TS7.2.1.

nico

Can I assume vanilla non fancy customized super basic dct's and pts will work out of the box after the upgrade? Or is there a diff to config or ts code?

nipper

Can I assume vanilla non fancy customized super basic dct's and pts will work out of the box after the upgrade? Or is there a diff to config or ts code?

99% should work OOTB, I have not had to make changes, but I imagine it happens.