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

upgrading from 7.3.1 - Is it worth It?

MikeMiracle

Anybody upgraded from 7.3.1 to a later version ? Our 7.3.1 installation is quite stable for last 1 & 1/2 years.But Management is keen on upgrading (probably to 7.4.1)to leverage 'new features' of latest software.

Our implementation is pretty basic a mixture of old style tpls & some site-publisher templates. We don't use LiveSite or any such goodies. Is an upgrade now worth the pain :-)

OS
RedHat 5.3

Thanks,
Mike

Find more posts tagged with

Comments

Adam Stoller

Given your scenario, the biggest gains from upgrading would probably be:

If your management is interested in upgrading - I'd suggest holding out a bit longer until 8.x (8.0 was supposed to be released Q1 of this year, still a couple of weeks to go until that deadline; and you might want to wait until 8.1 given the history of ".0" releases). 8.x is supposed to include a vast cleanup of the internal code, full 64-bit support (except, most likely, iwperl), and should include all the new features plus, perhaps, some additional ones.

nipper

The UI is different. I think it is worthwhile to go to 732, I like 741, but have not seen it in Prod that much yet. I think base TS functionality on 741 is pretty solid, but you would have to confirm that for yourself.

After that, as Adam mentioned, browser, DB and OS support are a big benefit.

RemoveDuplicates.rptdesign

Garth McMillan

We will be migrating to 7.4.1 within the coming few weeks. We are currently on 7.3.1.

Our primary (only) reason for the upgrade was browser support with IE9+. Latest versions of IE9+ (since the Microsoft security update around June 2013 - there's more information on the forums here and the support site about it) do not work with 7.3.1 and our organisation wants to upgrade.

Happy to answer questions though - particularly once we roll it out.

Just some quick points from our test environment:

Interface

The new interface is generally nicer looking, but incomplete/buggy (mostly CSS). They should've spent a bit more time time on it. Issues are things like difficult to read text (eg. grey text on grey background), lack of :hover :focus highlights - some areas don't change at all when you select items (eg. the Edit user panels) and buggy padding/margins on items. You can use custom CSS to override these problems if you want. The general display problems are present (though differ somewhat) in IE, Chrome and Firefox.

New parts of the interface are HTML5, but the bulk of it still uses the old quirks-mode HTML (with new CSS stuck on top). This is the cause of a lot of the bugs - due to pages not being rendered in standards mode.

Campaign management

The campaign management is meant to allow you to do email newsletters and such to users. This is incomplete and near useless for us - it shouldn't have been released in this state (for example, you can only have the same fields for all user lists, and you can't customise what fields they have (apart from 2 - helpfully called "custom1" and "custom2" (you can change the labels though). Autonomy said they'll improve it for TeamSite 8. We provided quite a bit of feedback to them on this.

Mobile device support

The free version is a bit of a hack (there's a paid version as well, but I've not seen it). Nothing special and we're not planning to make use of it ourselves.

General

Our biggest issues with 7.3.1 have not been resolved with 7.4.1. Though they have fixed a few things. I would've held off upgrading until TeamSite 8 if it weren't for our need to support newer versions of Internet Explorer.

DataSet Dynamic Filters.rptdesign

MikeMiracle

Thank you all for your valuable comments.

The plan is to upgrade the development server to 7.4.1 first to test the waters.

Hope the upgrade went fine for Zaarin.