Documentum Trusted Content Services missing from Product list

I will take this one back and work with Product Management.

Jay

TCS is no longer a separate product, the documentation has been rolled into Content Server Fundamentals and Admin Guide.

This is not exactly true, TCS is still being sold as an add-on product on top of Content Server and is licensed per CPU. It still deliveres additional functionalities such as (quote from January 07 license guide):

- Trusted Content Services is required for Documentum Compliance Manager for electronic signature capability.
- TCS is required for Retention Policy Services for digital shredding.
Notes
- All Content Servers accessing a common encrypted repository must be licensed for Trusted Content Services.

I can understand that you have bundled the documentation together with that of Content Server, but does that mean that you don't want us to specify tech support that a particular problem/question is related to Content Server as opposed to being more specific and saying it is a TCS issue?

Yes, you need a license to enable TCS functionality on content server. Once your enter the license key, you will be able to use TCS feature. Since the product features have been incorporated into the content server product, the product team should know about the features/issues, such that you dont need to create separate cases.

I'm not sure that I made myself clear during my initial question. The reason why I ask to list TCS as a seperate product in the product list is only for submitting service request and for look-up information in the Knowledge Base. Is there a reason why you would not want us to be able to specify problems in a more specific way for support purposes?

Also if I would follow your logic, the following products which are also part of the Content Server install and that need to be activated with license key's should also not be listed in the product list:
- Records Manager
- Retention Policy Services

I think for support cases there is a good case for letting users specify the issue a bit more precisely. The same goes for:
- Documentum Collaborative Services/Edition
- Content Storage Services (for EMC Centera)

Ideally I think you should match your official product list as this is what customers buy. For example, you can do an install of Content Server and never run into a Content Storage Services issue because you never bought this license, but when you do have this and you have issues with it, it helps to be able to specify this product seperately especially since the core Content Server functionality is already so vast that from a support point of view it really doesn't help to throw everything together under the name Content Server.