With the release of ConcourseConnect and the recent announcement that it is also Open Source, I find very little reason to keep supporting Team Elements as it is. You can think of ConcourseConnect as Team Elements '2.0.' If you are using Team Elements, you can continue with it, grab the source and have some changes made, or spend some dollars and migrate to ConcourseConnect. Perhaps someone will even consider managing the Team Elements project. With ConcourseConnect you will find a much more powerful and elegant system, a larger support staff, and of course continued development.
If you are curious about why ConcourseConnect is important, please read 12 Rules For Bringing 'Social' To Your Business, by Dion Hinchcliffe, in which Dion explains social businesses.
Since many of you started with Team Elements because of its collaborative nature, you should find plenty of return if you make the leap to ConcourseConnect. If you have any questions about social business software, let us consult with you.
Here's to your business' success!
Matt Rajkowski
View Full Post and Comments
This is the final post in a four (4) part series exploring ConcourseConnect. The first three parts can be read here: Introducing ConcourseConnect to Team Elements Users, Major Functional Changes to Team Elements in making ConcourseConnect, and ConcourseConnect: Improving Upon the Team Elements Core Modules.
Now for the technical overview...
Team Elements is a web application, based on the Enterprise Edition of the Java Platform, and is designed to be portable and scalable. Early Team Elements work introduced an MVC framework for separating the visual appearance of the application and the underlying business rules. The MVC implementation allows for security constraints for all web requests, and over the years various components have been added to share database resources, integrate a rules engine, and perform background scheduling. Those are all great things for modern web applications.
So what could be better? Well, it depends on who you ask. At Concursive, we evaluated many options, but in the end, the need to drastically increase flexibility of the application, without sacrificing simplicity, performance and scalability, won hands down. We also wanted a better user experience.
So how did we do that?
Continue Reading
This is the third post in a four (4) part series exploring ConcourseConnect. Part 1 can be read here: Introducing ConcourseConnect to Team Elements Users. Part 2 can be read here: Major Functional Changes to Team Elements in making ConcourseConnect.
ConcourseConnect improves upon several of Team Elements' modules and adds many more... here's a rundown of all the modules...
Continue Reading
This is the second post in a four (4) part series exploring ConcourseConnect. Part 1 can be read here: Introducing ConcourseConnect to Team Elements Users.
The following summary of changes encompass the major shift from private project-managed data to open, community-driven data, without sacrificing the need for privacy...
Continue Reading
Concursive Corporation recently announced a new product called ConcourseConnect, which is built on the Team Elements platform. Since as of this writing, the free version of ConcourseConnect is yet to be publicly released, I'll explore the various improvements by focusing on fundamental differences, major functional changes, overall functionality and technological changes. Some of the information is subject to change, so for the most part I'll focus on high-level features that shouldn't.
ConcourseConnect is being touted as a business social software networking platform. As a testament to the Team Elements platform, building out a social networking application took the developers about 6 months. That was after a lot of product management responsibilities which helped orchestrate the desired capabilities. The ongoing plan is to review the ConcourseConnect code base and contribute back to the Team Elements project. Future blogs will discuss the direction of Team Elements, migration to ConcourseConnect for those that want to, and any other fundamental changes. Some of you may find that moving to ConcourseConnect is more desirable given the feature set, others may want to stick with the project management capabilities of Team Elements.
Now on to the fundamental differences...
Continue Reading
During the last few months we've added several talented team members. In this time, the development team have tackled updating the application at many levels.
Some of the improvement areas include...
Continue Reading
At the last Southeast Virginia Java Users Group (SEVAJUG) meeting I presented and demonstrated Team Elements. You can find a copy of the presentation under the documents tab and you can visit http://www.teamelements.com to see the last stable released version of Team Elements.
The user's group meeting was good as usual and the feedback was great. If you live in southeast virginia and you have an interest in Java, you should catch one of the meetings. See their website for upcoming topics and dates.
View Full Post and Comments
View Full Post and Comments
Once again, a useable, but unstable, developer version is available in the trunk. You can generate a .war and test on PostgreSQL 8+ and Microsoft SQL Server. This release has many new features including a WYSIWYG Wiki, Search improvements, plus stats gathering.
View Full Post and Comments
An alpha version of Team Elements is now available in the subversion trunk:
This version compiles and installs, and possibly upgrades a production installation. Please test and report your findings.
What's new...
Continue Reading
;){kind=logo}
