Klish Group has delivered highly successful solutions to our customers – providing measurable results and sustainable business value. Our approach to Autonomy Interwoven implementation projects is to not only draw upon our deep skills and expertise within the Enterprise Content Management area, and Autonomy Interwoven in particular, but also to leverage our unique and differentiating tools and assets. Over the years, we have developed these tools and assets to enable rapid deployment of solutions, provide demonstration environments, conduct employee training, simulate client environments, and improve product usability.
Klish Group Commons Library
Klish Group has extended the TeamSite and OpenDeploy platforms to improve product usability and provide common customizations virtually ‘out-of-the-box’. In many of our client engagements, we see the same types of customizations and extensions being needed for templates, workflows, database deployments, etc. This has led us to create a set of common libraries for TeamSite and OpenDeploy product extensions called the Klish Group Commons Library enabling rapid deployment of common customizations and extensions to the TeamSite and OpenDeploy platforms.
Translation Integration - Fluint®
Enabling translation capabilities within a content management environment can be complex and time-consuming. To facilitate development efforts and improve usability, we have developed Fluint®, a proprietary translation connector, which provides direct linkage between TeamSite and content translation providers.
Benchmarking TeamSite and SitePublisher Environment Performance
Klish Group has created a set of performance test cases using the open source OpenSTA software. The performance test cases can be run against TeamSite environments – much like a load test can be run against a web site – to discover and rectify system performance issues.
TeamSite Extensions
Klish Group was a pioneer in leveraging the Struts MVC framework (including Tiles) to extend the TeamSite UI. We have implemented this at customers using versions as far back as TeamSite 6.5. For example, all of the workflow CGI tasks that we develop as part of a TeamSite workflow template or model are controlled by an industry standard MVC framework (Struts, Spring MVC, etc.). TeamSite 7.1 now uses Struts MVC in the TeamSite architecture instead of the custom Interwoven MVC framework used in earlier versions.
Klish Group has developed an advanced MediaBin browsing application using the Ext JS framework for a customer who wanted more fine grained control than the out of the box TeamSite ECM connector had to offer.