allow_delimiter_in_name

Set Option: Model object or type-specific attribute

Controls whether the delimiter is a restricted character.

When set to TRUE, the current delimiter is no longer a restricted character for non-project object names. The delimiter is still restricted for versions, types, instances, and projects.

With this feature enabled, object parsing is done from right to left in the sense that the right-most delimiter character is taken to be the delimiter. As a practical matter, object identification is done by first attempting to identify a given string as a name, and if that fails, it is identified as name<delimiter>version. This capability is particularly an issue with create, move, and use.

Note: All databases in the same DCM cluster must use the same value for this attribute. Failure to synchronize this value may result in undesirable behavior similar to having objects with "~" in them, and changing the delimiter to a "~."

With the feature enabled, you can also create non-project objects with versions. However, you will also be unable to use ccm move to set a version on a renamed file. (You can work around this limitation by using the ccm attr command or the Properties dialog to change the version.)

This attribute can also exist on individual types. In this case, the database setting is overridden if the database setting is FALSE and the type-specific setting is TRUE.

These built-in types have allow_delimiter_in_name set to TRUE:

process_rule

processdef

saved_query

releasedef

project_grouping

folder_temp

The default is FALSE.

This option has these restrictions and effects:

For information about how to set model attribute options, see Setting model object attribute options.


Feedback