Can Rename be controlled to follow any rules ?

[NickD]

There is quite a lot of information about setting up OIRs and preferences to control the first-time naming and numbering of CAD files and their CAD documents in PDMLink, but there is nothing similar to control how Rename works (only the option to remove Rename permissions).

The fundamental problem with this, in our opinion, is that the original filename used for a 'new' CAD file is not necessariliy the one you want to use when it is first checked in - so a rename is needed in the Workspace, and the user has to deal with CAD Doc Name & Number manually. What means are there, if any, to control Rename behaviour on new files & documents in a Workspace ?

Like many other long-term Intralink v3.4 users, we are accostomed to allowing our users to start work on new CAD files and save them in their Workspaces, whilst they develop the initial geometry and decide what to use as the most appropriate 'Desciption/Tilte' - which is stored in a text string parameter/attribute/file-property. Once they have the 'Description/Title' they can copy and paste this into our seperate document numbering system, and it gives out a unique number to use as the filename in exchange - it acutally copies it onto the PC clipboard so it is ready to paste into a rename dialogue box. As Intralink v3.4 preserves all file dependancies during file renaming in the Workspace, it is a simple matter for our users to ensure that all new files are correctly named before the first check-in, and after than they are never renamed (and duplication simply makes more new files...). Any files that are purely temporary and are not needed can be easily distinguished and discarded whilst they are still marked as new, and that saves numbering and accumulating lots of files that are immeadiately marked obsolete.

Whilst files are new and have never been checked in, it should be just as easy to rename them as to name them (within company rules set in OIRs and preferences), but once checked-in and made available for other users to see and reference then renaming can/should be restricted.

Do you agree ?

Have you solved this problem / If so, how ?

[DanielReid]

Agreed. Having some restrictions or rules will also reduce confusion and frustration for users.

[NickD]

A little bit of testing (as no doubt, many others have already done...) shows :

(a) new CAD files that have never been checked in can be renamed in a workspace, but the rename action is disabled once the file is checked in - and we think that is OK

(b) if the new CAD file is renamed in the workspace before the first time it is uploaded, then the OIRs take effect and they set the CAD Doc Name & Number based on the filename (with / without extension)

(c) if the new CAD file is renamed after it is uploaded (upload being done either manually, or automatically upon save by setting the config.pro option dm_upload_objects to automatic), then the OIRs are not applied and the previous values of CAD Doc Name & Number derived from the initial temporary filename remain unchanged.

This behaviour is clearly not appropriate if you want to apply a Name Driven policy consistently.

To limit the degree of customisation that might be required, would it be possible to write a Macro or Wizard that appears in the Rename screen (on a menu or with with a toolbar icon) that will "re-apply CAD Doc Name & Number rules" based on the new filename(s), even if these rules have to be coded again in another seperate java or XML file ? ie. surely we need some OURs (Object Update Rules) as well as OIRs ?

Also, can the table display be configured or customised for the Rename screen, eg. to show an Attribute (eg. Description/Title) in an extra column, or on the assumption that the desired Macro can be built, to show only the old & new filenames ?

[Hozaibergen]

@NickD @DanielReid 

Good afternoon, there is no solution yet?

[avillanueva]

This is a very old post. A lot of this is part of existing documentation and configuration. I suggest creating a new post with your specific issues or questions.