Yes. I'm not on the administrative end so I'm not sure how cumbersome it is to setup and maintain, but it seems to work fine as a user. Promoting a document locks down the model in PDMLink and uploads our documentation (PDF of the drawing and XML file for the BOM; these files are generated when we check-in to PDMLink). Release of an ECO then Releases the model in PDMLink requiring a new rev to be generated if further changes to the design are required. I know we do a lot of tailoring to our processes so I believe it's pretty flexible. Not sure how the out-of-box functionality works though.

If you have specific questions, I'll be glad to talk to our admin and get you some feedback.
-tg

http://xternal.me

I have some questions.
Did you ever use PDMLink?
PDMlink works buy storing data in a workspace which is linked with commonspace(database). Certain data management tools are disabled in proe when using PDMLink. This is because renaming and deleting of objects can only be done in the workspace browser. Also your working directory is in fact the workspace. Does Enovia work this way?
I saw a small demo and was told that you only use Enovia if you want to actually checkin, otherwise it is as if you are saving in windows folders/directory structure.

We use PDMLink in between ProE & Enovia. PDMLink manages all the ProE intricacies. It deals with relationships between parts, assemblies, drawings, family tables, etc.

Enovia is just used for our part number assignment and engineering change processes. The PDF output from our ProE/PDMLink checkin process is stored in Enovia but not the actual ProE models.

-tg

http://xternal.me