There were no responses.  I am interested as to whether this indicates 0 support for a Visual Studio IDE or whether, like me, people don’t really read the questions once there has been more than one response.

I guess I’m looking for comments regarding my original 5 questions either way…

On Wednesday 17th June 2008 I attended the Open Text UK Web Solutions Community Day - completing my trifecta of RedDot CMS conferences for this year. Unlike my previous reviews, I won’t be going into as much detail - the contents of the presentations (powerpoint plus audio) are available (well, the powerpoints are so far) on the UK WCM Community Site. For those of you without access to this site, each presentation could probably merit its own article - so I’ll just stick to the highlights for now. At the moment, I just want to get this out before the release of Version 10 on June 30th… Leave comments for anything you would like in more detail.

The conference was held at the Madejski Stadium in Reading, just a short and convenient hop from my place of residence. The day was broken up into four tracks - technical, partner, customer and Obtree. I stuck to the technical track and will be going through the audio and powerpoints of the other tracks as time permits (well, except for the Obtree track that is!)

The day started with the obligatory welcome and introduction - the main points of interest being the above mentioned launch of the UK WCM Community site (a replacement for the previous RedDot Community site) and that all sessions would be available there as powerpoints and audio. The obvious advantages being less note taking required and less concerns about missing the content of the other tracks.

Enhanced Template Design

First up on the technical track, enhanced template design - which showed how to use Render Tags and Pre-Execute scripting to create enhanced and multi-functional templates - ie single templates that handle what you may have previously considered implementing multiple templates for. Examples included alternative page headlines, styling the first item in a list differently, laying content out in different column configurations, pulling content up from pages nested below, detecting whether a list or container contains pages, using a single template for page links, documents or external URLs, splitting a list into two or more columns and A-Z listings.

If you haven’t done anything like the examples above, and/or you are not sure how to, then I would imagine this session (and the code samples) would have been beneficial for you. If the above sounds easy to you - well the benefits would have been limited. One thing to note - due to the limited scope and the introductory nature of the session, there are a number of issues not touched upon in the code samples, including placeholder escaping and code efficiency (one, you will probably want to use functions, two beware large amounts of logic in list processing - you can easily start creating Pre-executing script in the size of megabytes). Oh - and the Render Tag examples, while not requiring Navigation Manager, do require version 7+.

Two of the more advanced items to come out of this session - while you can use RQL in your Pre-Executing script - you should limit it to read options only, as write options during the page build are unpredictable and may cause issues. Also, you can switch from Pre-Executing script to RDExecute for debugging - though be aware that this will be easier if you use only a single Pre-Execute tag pair, and that the error and line numbers returned are specific to the generated script…

Implementing Web 2.0 Tagging & Voting using Delivery Server Web Components

An introduction to tagging and voting and how Open Text delivers them in Delivery Server, you can probably skip straight to page 17 of the presentation for the technical overview. Interestingly, you don’t need a license for the Tagging and Voting Web Components - but you do need the Delivery Server “RMVT” module license. In fact, the Tagging and Voting Web Components use standard Delivery Server functionality - you could write them yourself (though I am not sure whether this would include the integration into Delivery Server?) - they exist to get you off the ground quickly.

Tags exist in their own project so that you may share them between projects. Tagging can be assigned to pages or components of pages, and from Delivery Server or Management Server. A blacklist of unacceptable tags (including regular expressions) and a white list of suggested tags can be maintained. Future functionality (when?) includes managing tags from Management Server and utilisation of the BIRT chart engine for graphical views.

Having not implemented tagging, voting or Delivery Server recently - its not immediately obvious to me how good the implementation is - it will be interesting to hear some feedback in this regard. One note brought up was that there is no magic in the voting system that stops multiple anonymous votes. You can however limit votes for logged in users. In the meantime, the community site is using these components - so keep an eye on it to see how these pan out (its a bit barren to really test these components at the moment)

Navigation Manager - The Next Steps

Continuing on from last year’s Community Day Navigation Manager session (which I missed), this session goes into what has been learnt in the last year in terms of lessons learnt and best practice. If, like me, you have been through these “lessons” personally, then probably the explanation of Navigation Manager caching was the most interesting part of the session. For those that are yet to experience the fun of Navigation Manager - take heed - I can personally vouch for most of this session!

Some specific comments on some of the dos and don’ts:

• Use as few navigation areas as possible - 1 - 3 is okay, 7+ is not (on a single template that is)
• Use RenderTags for generating breadcrumbs and sitemap - the placeholder functionality may be deprecated in the future.
• Make use of detailed authorisations on navigation lists - restrict the users who can connect pages to the navigation system, reduce likelihood of connecting duplicate pages etc.

The only “Don’t” I would question is the “Do not use Pre-execute or RDExecute in the Navigation Templates.” - though I would certainly caution against it - especially if you are planning to execute RQL as well. I would suspect that this is more an issue with code efficiency (as mentioned in Enhanced Template Design above) - you need to be aware that your code size and complexity will be multiplied out by the number of navigation items rendered - which can easily increase you Pre-execute or RDExecute script size to unmanageable levels - especially if you have ignored some of the other best practices.

Code samples included recognising first and last links in a list, differences in Rendertag and page info element GUID representations and how to successfully compare them, for each loops (including counters), changing site colours and/or footers per section, global project values and the CurrentMasterPage rendertag.

Unfortunately I think this session did a better job of highlighting the restrictions, limitations, inconsistencies and hacks required to utilise Navigation Manager rather than showcasing the progress that has been made. My recommendation still holds - the most important best practice is to keep your site navigation as simple as possible!

I missed picking up the updated cheat sheet - and I haven’t seen a copy on the community site - yet.

Delivery Server and User Generated Content

A worked through example of an events management system using Delivery Server. As always - skip straight to the implementation for the “meat” of the presentation. I imagine this would make a good next step after the Delivery Server training.

Again, the example is bare bones due to the introductory nature and time constraints - but basically should give a good example of moving data in and out (ie CRUD operations) of Delivery Server - regardless of whether it is an events management system or even user generated. I don’t know if I would go as far as to tag Delivery Server as a rapid application development platform though (comments?) It should be noted that the session was Delivery Server focused, so there was no mention of integration with Management Server. Perhaps next Community Day (or perhaps here) an example of User Generated Content and integration with Management server would be useful (rather than replicating user and workflow management in Delivery Server)

Developing a Sharing Strategy

This session covered every (and I do mean every) sharing possibility in Management Server, from page instances sharing content classes to inter-project content sharing. For those who are no longer beginners I think you can safely skip to slide 10 - inter-project sharing techniques. The actual sharing strategy decision graph from slide 18 is probably the most helpful element - but it won’t be anything new to advanced practitioners.

Probably the only hole is that the session doesn’t specifically mention sharing of content classes via project or language variants - but these pretty much come under multi-sites - the decision is still whether the information architecture is shared or not. For language variant projects I have been on, I would suggest you want over 80% shared information architecture if you want to use language variants over master/child projects.

Version 10 Preview

The version 10 preview was not too different from the one I wrote about in the 4th European RedDot Usergroup Conference Review - Part 1 so I will only mention the differences here. This preview was running off of the servers back in Germany, rather than on a virtual server. Hence it was even closer to being the finished version. The obligatory apology for speed was changed from virtual server to network speed We thankfully didn’t have any long winded introductory powerpoint presentation though - so we got straight into the live demo.

The major drivers for the new version are usability and cross browser compatibility - the goal being to provide a “groundbreaking” step in Web Content Management. I guess we will all be the judge of that soon… Consequently, except for the PageBuilder improvement - don’t expect any developer enhancements this time around Instead, expect your users to have more convenient, faster, quicker, less clicks, less popups and more direct access to features, functionality and completing tasks (ie replacing all that RQL you have been writing…) I sense the Open Text sales team will be very excited - lets hope our users are (which will come down to stability and robustness of the final product in the wild I think) and us (who still have to develop for and support it).

The latest version of Telerik’s RAD Editor will be included - lets hope Open Text have integrated it more successfully (fully and bug free) this time - giving cross browser support, more options and pure XHTML code generation.

Search by page id directly in the search box. Management Server will remember recent searches and will show both the search results and a selected page - allowing users to update each page in the search results in turn without popups or having to re-search.

The changes are all in SmartEdit, so no SmartTree updates. Also, not all dialog boxes have been converted to the new look and feel - so expect some “flashbacks” occasionally. Other future items not yet implemented include combining tasks across projects.

I missed the recent webinar on Version 10 - so leave comments on anything last minute I’ve missed.

Conclusions

While I can’t speak for the partner or client tracks (yet) - the technical track was good, but not excellent. On the plus side, most of the presentations included real problems and solutions with code samples. On the minus side, most also included a lot of introductory waffle before getting to the technical meat of the session. All were limited by the time allocated and were necessarily simplistic in order to get the concepts across in the time frame. It is my experience that the real problems surface when trying to fill out the last 20%, not the first 80%.

The venue and catering were good. The main room (registration, lunch, partners, socialising) was pretty small, so there were a limited number of partner stands - but there were plenty of Web Solutions and partners floating about - including the Web Solutions support team. We got another Open Text branded netbook bag (similiar to the Content Day) with another pad, pen, pencil and partner parenphenalia (including a red dot stress ball from one of the partners).

In conclusion it was a good day - though I personally could have used the content of the presentations a year or so ago, better late than never! It was a good opportunity to catch up with past clients, Web Solutions consultants and RedDot Usergroup members in a much cosier setting than the Content Day. I would certainly recommend it over the Content Day if your dealings with Open Text are limited to their Web Solutions arm (and you can only get to one)

Frank’s work is Java/JSP based so to use it you will need to install and configure Tomcat. Thankfully he thought of this and has provided a pre-configured installation of Tomcat and full setup instructions which we have included in the download along with all the plugins and documentation.

There are a few things to mention before you go running off to install it all.

1) This needs Tomcat and a JAVA JDK installed on your system
2) It has been designed for an English interface/data format
3) It has only been tested against RedDot 7.5.2.16 and JDK 1.5. Please leave a note if you test it against another version and let us know how it gets on.
4) As it is Java based and we (Paul, Frederic, Markus and Adrian) are not all that familiar with what the code is up to and we’ve not had the chance to run through these ourselves yet, so they are supplied as-is with no guarantees.
5) None of us accept any responsibility for anything that may go askew when installing or running the library or it’s plugins. It’s up to you to test them somewhere safe first!

Even the plugins use JAVA technology, which, while you may be unfamiliar with, you can still use it! All the required software is Open Source and the step-by-step installation instructions will guide you. To make it as easy as possible for you I provide a pre-configured Tomcat package, which is needed to run these plugins.

Here is a description of all the provided plugins.

Plugin cancelWaitingJobs cancels all waiting publishing jobs in a project to get the publishing queue free for an important page needs to be published.

Plugin collectUserAddresses can be used to inform authors via normal Outlook e-mail over server outages or changes in project.
You can select one or more projects. The plugin

• Builds a Set of all users linked to these projects
• shows all e-mail address from User profile separated by ; (ready for use in MS Outlook)

Plugin deleteJobReports clears old Job Reports you don’t need anymore. If you have hundreds of job reports it take very long to open it in Smart Tree. Use this plugin to delete them before! It lets you choose a number of days, you want to keep the reports.

Plugin findTemplateElement scans all content classes in all folders for a given content class element type and element name. Often the same template code has to be repeated in several content classes. If a change is needed in such an area, you could use this plugin to find all content classes you have to adjust by an element used in this repeated template code.
It ends up with a table with columns:

• Content class folder name
• Content class name
• Content class element type
• Content class element name

Plugin resetAllDraftPages helps you and authors as well to get rid of all your pages saved as draft. Reason for creation was, that authors often create pages again and again. From my experience they have often many pages in state draft which are not needed anymore.
Newly created pages will be deleted and for changed pages an undo is triggered. After end of plugin your list of draft pages would be empty.
I offer this plugin for authors by patching the Tasks dialog and inserted a link beside “12 pages in draft”.

Plugin showChildDetails gives you an details overview of all pages linked on a List or Container.
It comes up with a table for all pages linked on selected List or Container with the following columns:

• Page Id
• Page headline
• Content class name
• Created by user name
• Created on date
• Last changed by user
• Last changed on date
• State (draft, released)
• Released on date

Plugin showPageByGuid shows you basic information (page ID, headline and content class name) for an entered page GUID. Helpful for RQL developers sometimes.

Plugin showTemplateElementsUsage help to identify unused elements in a content class for deletion. Gives an overview which element is used in which Template Variant source code.
It shows a table of all elements by name and type and checks every Template Variant source code of content class if the element is used (element value itself of red dot for this element).
The  interpretation is up to the admin. Even an element is not used in any Template Variant, it may be could not be deleted.

Plugin showTemplateGuids is useful for RQL developers who needs to refer to a content class in a program by GUID of content class.

Plugin showTemplateLanguageVariantDependency helps to decide if a page of a content class will appear in the translation editor’s list of pages needing translation.  It gives an overview of the checkbox “language-variant independent” of all content elements of selected content class.
It shows a table with following columns:

• Element name
• Element type
• One value for all LVs
• Different values per LV

It marks elements green, if a red dot in Smart Edit is included in the Template Variant of project’s display Project Varant.
And it marks elements in red, where no red dot is found. This is often wrong, because a translator will get this page for translation, but cannot do it.

Plugin showTemplatePreassignmentReference offers the backward functionality of Preassign Content class on a List or Container. For the selected content class it shows, where it is preassigned. It helps to make the preassignment definitions consistent in a project.

It searches all content classes in all folders per default, but let you choose one Template Folder to speed up search too. It goes through all content classes and checks on all Lists and Containers the preassignment definition. Displays all template elements the selected content class is preassigned in a table with these columns:

• Content class folder name
• Content class name
• Element name

Plugin showUsersInGroup helps to analyses authorization setup directly in Smart Tree. Authorisation is often done via User Groups. This PlugIn displays all Users of a group directly, without the need to to switch to Server Manager.
It shows a table with following user properties:

• User name
• User full name
• User e-mail address (linked for easy contact)
• Description

If you find some of these plugins interesting,

Download the 12 Plugins and the RQL API

and open the installation.txt for further instructions. If you have questions or need help, drop me a line I will try to answer.

About the RQL API, interesting for JAVA developers

All plugins use functions implemented in the RQL API. It hides the XML handling from the plugins and make it more handy to request actions within CMS.

The classes are provided without source code, but still can be used for own programs.

In addition it implements more functionality from the following areas:

• creation of pages and receiving and changing of  StandardField*-, Text-, Image- and Media-Elements
• navigating through project structure (page - MultiLink - page) as you need
• configuring and  starting of publishing jobs
• retrieving and assigning of authorization pages

Here is an example Java code snippet showing how to find a template element in all content classes of a project and the check, if it will be shown in Edit form dialog or not. It looks like this:

String loginGuid = "your current login guid";
String sessionKey = "your current session key";

String elementName = "element name to check";

// open project
CmsClient client = new CmsClient(logonGuid);
Project project = client.getProject(sessionKey);

for (TemplateFolder folder : project.getAllTemplateFolders()) {
  for (Template template : folder.getTemplates()) {

    // skip template without this elem
    if (!template.contains(elemName)) {
      continue;
    }

    // change elem
    TemplateElement element = template.getTemplateElementByName(elemName);
    System.out.println(template.getName() + " " + element.isUsedInForm());
  }
}

Further usage of the RQL API can be found in the JSPs in apache-tomcat-6.0.10\webapps\rql_rdug.
If you find the API interesting and need help, drop my a line.

You’ll find the latest news of other sites on the web dealing with Open Text Web Solutions – if we missed one, just drop us a note and we’ll add it to the list. What do you think of this new feature?

All you need is half an hour of preparation, some definitions for the Excel format, and that’s it!

Step 1: Defining Excel as a database connection

1. Switch to Server Manager and open the node “Administer Database Servers”.
2. Select “Database Access Modes” and choose “Add Access Mode” from the Action Menu.
3. Enter the following into the dialog:
   Name: XLS
   Description: Microsoft Excel
   Provider Template: Provider=”Microsoft.Jet.OLEDB.4.0″;Data Source=”<%Database|database|xls%>”;Extended Properties=”Excel 8.0″;
   Category: Jet4

Step 2: Accessing the data from your project

1. Save your Excel file on the RedDot server. A good idea would be to upload it using the Asset Manager, since then you can offer your editors to upload newer versions at any time. The Asset Manager’s data storage must be in the file system.
2. Switch to SmartTree view of your project and select “Administer Project Settings” - “Database Connection” and choose “Create Database Connection” from the Action Menu.
3. Name it as desired, then select “Product” and choose “XLS” from the list. Then click “Next”.
4. Choose your Excel from the file system.

Step 3: Publishing the content

1. In your template, create a new database element for every column of the Excel that you want to publish. You will need to set the following:
   Database: Choose your Excel (step 2, item 3) from the list of all your database connections.
   Table: By default, an Excel document contains three tables. So it’s a good idea to delete the unused and to name the remaining uniquely.
   Field: This is the column. Line 1 will be used here.
2. The way you output these data is up to you. RedDot offers two ways: All on one page, or one page for every fieldset (which is one line in Excel).

Definitions and Settings for the Excel

As RedDot on the one hand expects a “real” database, and on the other hand, Excel is not a “real” one, your Excel file must comply with some rules to make the whole thing run:

1. All tables must only be named with ASCII characters,  must be named uniquely and must be “simple” tables containing just data (no formula etc.)
2. The first line will be used as identifier of the field. No data must be written here. These names must be unique, too.
3. Every line below will be considered as one fieldset. So there should be no empty line, all lines must follow the scheme from line 1. No extra formatting (e.g. chapter headlines) is allowed.
4. No changes must be made with the table and column names. If that happens RedDot will lose the connection to the data field.

Senior Account Manager (m/f) Web Content Management – ID.12301

Location: Home Office Germany (preferably Munich or Frankfurt a Main)

Your Responsibilities:

• Focus on achieving the annual sales targets by winning new customers as well as identifying sales possibilities at existing customers in Germany and Austria
• Expand our client`s market share through winning new and especially international clients
• Establish and maintain relationship with our client`s technology partners, with key consultancy organizations, system integrators and application providers
• Organize and deliver product demonstrations and presentations for prospects and customers with the assistance of product specialists

Your Qualifications:

• MBA or equivalent
• At least 5 years of success in direct sales of Content Management or Digital Asset Management software technology
• Experienced in selling to large international accounts and in working in a competitive and target oriented environment
• Track record of previous quota over achievement
• A valuable network in the field of potential clients; a valuable multi-level personal network in Germany and Austria
• Able to work independently as well as within a team
• Excellent verbal and written communication skills
• Very good command of English and German; Spanish or Eastern European language skills are an advantage

Could we inspire you for this most interesting and challenging position?
Then contact us for more information or send your application to Daniela Molle at jobs@3ccc.de !

The technical teams within Open Text UK will also be participating in the site, so you may be able to get some useful information from them, though it’s not intended to replace the support desk, so don’t go venting your problems at them. Play nice!

For UK customers, you can join the site at http://wcmcommunity-uk.opentext.com
Nice memorable URL there; even the OT staff at the UK community day couldn’t all remember it

Disclaimer: I am a contract Management Server (nee RedDot CMS) / web developer currently working for the Legal Services Commission in London. However, I was at the conference on my own time and dime. I also blog for the Unofficial RedDot CMS Blog, for whom I gave a promotional presentation, and volunteer at Friends of the Earth, UK. However, all my views are my own and in no way represent the views of any of my affiliations, except by coincidence or accident

Welcome

The conference got off to a bit of a late start, what with some of the organisers, Open Text, partners and clients flying in from Germany. Of course it was someone from the UK that was truly late - London traffic and all. The welcome included a brief introduction to the RedDot Usergroup as well as current activities. Apparently a name change to the Web Solutions Usergroup is being investigated.

Unofficial RedDot CMS Blog

This was an awesome and thankfully very short presentation given by yours truly. I can’t take credit for the powerpoint presentation - that was all Frederic’s work - but the spoken content was all me, for better or worse. Contrary to popular opinion at the conference, its not *my* blog - I am merely one of the eight contributing authors. Perhaps if the stats rise significantly due to my presentation I might be able to join the coveted inner circle

Open Text Artesia Digital Asset Management

This was my first look at Artesia, having missed the presentations at the Open Text Content Day UK. Or maybe I should rephrase that as my first glimpse. One of the issues I have with a lot of vendor and partner presentations is that from a technical point of view, the content is minimal. Between the marketing spiel and the high level nature of the presentations - well maybe I am just not the right audience. The reality for me is the coal face of actually making things work in real life. Still, there were a couple of interesting points to come out of this. With the current move away from documents towards video I have to agree with the presenter that it is a bit unfortunate that Open Text has the word text in its name. Perhaps Open Video or Open Media would be more appropriate looking forward? Oh, and general consensus amongst clients was that no one was happy with the inbuilt Asset Manager in Management Server

Coffee Break

Had a great conversation with Ulrich Weiss about performance issues with Navigation Manager and 700+ instances of the master page templates - before I realised he is on the RDUG management board and also an accomplished RedDot developer at Karlsruhe Institute of Technology - as would be proven in a later session.

Roadmap and Version 10 Preview / Live Demo

After another lengthy marketing spiel (including slides from the Open Text Content Day UK and the previous Artesia presentation - well I can’t say Open Text don’t know a thing or two about content reuse!) and some buzzword bingo worthy rhetoric (We care, provide a compelling user experience, agility and innovation) - finally got some information on the roadmap and my first view of version 10 - mostly in Powerpoint slides, but with some live demo.

Nothing is final with dates, but we can apparently expect version 10 to drop in June 2009 (hey - that’s now!), with a smaller service pack or upgrade codenamed “Falcon” in December 2009. The next major version after that (codenamed “Orca” - not a good sign) is scheduled for April 2010, and is likely to be a major update of the backend to .Net.

Version 10 would seem to include a new version of the PageBuilder written in .Net, which supposedly could increase PageBuilder performance by up to 70% (depending on project implementation / complexity) and an overhaul to the SmartEdit interface - slicker, with drag and drop. The PageBuilder enhancements also have multi-processor support - which should allow publishing and editing at the same time - yay! It will also be released as an upgrade to version 9 separate from version 10.

The new SmartEdit will work across Firefox, Safari and Chrome (and IE of course!). SmartTree is planned for all four browsers, but it is not certain yet (it may contain an IE only tree). The clipboard comes to the new version of SmartEdit, as well as a read only Navigation Manager tree to help navigate the site, drag and drop content classes, a right mouse button menu to replace the Action Menu and a number of other common information / actions are promoted in the interface - project switching, views (SmartEdit, redlining - though still no structural redlining, form view, preview and Delivery Server preview - though no preview by date - you will have to do that the old fashioned way for now) and the current page identifier.

Search and tasks have been improved. You can now access recent searches and also save customised searches for later. The results may be grouped by your choice of search criteria. The excessive clicks, pages and popups required for tasks has been simplified - replaced with a new home page, fully customisable iGoogle style with “widgets”. For example, a custom search showing recently modified content. Presentation can be customised by group, but you can still only see information relating to the current project.

Last bits - should support 64 bit, should run on VMWare, while RQL should still be supported you will need to test as their is no 100% guarantee. There are no changes to SmartTree.

Discussion centred around the upgrade from 9 to 10 - basically play it safe - ideally upgrade on a separate box and migrate across (with all the fun that this entails). If there are going to be upgrade problems, this is going to be it. Of course, you always have the option of staying on 9 and upgrading the PageBuilder only - which should garner significant performance improvements by itself. Also - no date on version 10 service pack 2 (the first “usable” version, as one of the members joked).

My thoughts? It looks promising - but the proof will be on the ground in real projects, not in presentational demos. It has certainly been a long time coming. While I think most of the interface improvements will be for the better (and remove some RQL plugin requirements) the question is - is it enough? That will become even more pertinent if the upgrade process turns into a nightmare. I will add one personal note on the user interface - the drag and drop content classes. From the demonstration (which wasn’t perfect) - you can drag the content class from a pop out menu on the right. Apparently this will only show those content classes that are available on the page. The red dots you can place that content class on will remain red (others will be greyed out). Does this seem backwards to anyone? Wouldn’t it be better to present the available content classes from a context menu on the red dot itself? Also, there doesn’t appear to be any visual representation of content classes - which would have been a nice addition too.

I still have plenty more to cover, but that is a post for another time (soon!). On Wednesday I am off to the UK Web Solutions Community Day 2009 in Reading - which should hopefully shed some more light on version 10.

Until next time,
Adrian

• Starting with the presentation of SMS Siemag AG - they are running their intranet on RedDot for ten years now! (Remember the times, when RedDot still was called Info Office?) It was really fascinating to see a project running for such a long time, being refactored and updated on a regular basis.
• A roundup on authorization structures (Management Server) and personalization (Delivery Server)
• An introduction to Product Information Management systems: How to manage your product data with all meta information for different channels (print, web - and the integration into the Management Server, CD-ROM, etc.). This was really interesting, as there are some “strange constructs” around in customer projects with multiple sources of data (and sometimes contradicting content) - If this sounds familiar, a PIM system might be a good consideration for you.
• An insight about customer support structures at Open Text which are now applied to the former RedDot customer care. A new ticket system is on it’s way and about to be launched in July/August, so you have one single support portal for all of your Open Text products. More on this topic soon.
• Digital Asset Management by Open Text (formerly known as Artesia DAM). A new alternative to the traditional Asset Manager and external solutions like Canto Cumulus. Though it’s not cheap (around 60.000+ € was mumbled), it has a lot under the hood and might be interesting for company with lots of multimedia assets.
• The Deutsche Bank presented two of their intranet tools “Forms & Games” (form editor, voting, polls, etc) and “Sales Professional” a web-based training creator.
• and finally: The long awaited presentation of the new Management Server 10 (and this time it wasn’t a PowerPoint presentation). We’ll give you a closer look on what’s fresh and hot soon in a separate article.

All the presentations are available on the RedDot Usergroup website (presentations only available in German).

Minimum 6 weeks engagement.
Immediate start.
Attractive client.
RSVP.

Contact: Dan Swan
E-Mail: daniel.swan@itchdigital.com