Changing the Document version

Hi,

When we create a new document for the first time, it gets checked in aas version 1.0 into the repository and other version options 1.1(next minor) and 2.0(next major) are disabled by default.

I want to know that is there a possibility to change the version of the document to 1.1 or 2.0 even when the document is getting created for the first time and checked in to the repository.

If yes, please let me know what configurations/settings need to be changed.

Howvere it doesn't look like a recommendataion to me not to create the first version of document as 1.0 and create some other version, but want to confirm that is that possible or not so that I can provide a justification to the client.

Thanks for your help.

Find more posts tagged with

Comments

RakeshHK

It is possible. However it is not advisable

API> create,c,dm_document

...

0900110f8000396c

API> set,c,l,r_version_label

SET> 2.0

...

API> save,c,l

...

API> dump,c,l

...

USER ATTRIBUTES

object_name :

title :

subject :

authors []: <none>

keywords []: <none>

resolution_label :

owner_name : Administrator

owner_permit : 7

group_name : docu

group_permit : 5

world_permit : 3

log_entry :

acl_domain : Administrator

acl_name : dm_4500110f80000101

language_code :

SYSTEM ATTRIBUTES

r_object_type : dm_document

r_creation_date : 4/21/2010 12:13:19 PM

r_modify_date : 4/21/2010 12:13:19 PM

r_modifier : Administrator

r_access_date : nulldate

r_composite_id []: <none>

r_composite_label []: <none>

r_component_label []: <none>

r_order_no []: <none>

r_link_cnt : 0

r_link_high_cnt : 0

r_assembled_from_id : 0000000000000000

r_frzn_assembly_cnt : 0

r_has_frzn_assembly : F

r_is_virtual_doc : 0

r_page_cnt : 0

r_content_size : 0

r_lock_owner :

r_lock_date : nulldate

r_lock_machine :

r_version_label [0]: 2.0

[1]: CURRENT

r_immutable_flag : F

r_frozen_flag : F

r_has_events : F

r_creator_name : Administrator

r_is_public : T

r_policy_id : 0000000000000000

r_resume_state : 0

r_current_state : 0

r_alias_set_id : 0000000000000000

r_full_content_size : 0

r_aspect_name []: <none>

r_object_id : 0900110f8000396c

APPLICATION ATTRIBUTES

a_application_type :

a_status :

a_is_hidden : F

a_retention_date : nulldate

a_archive : F

a_compound_architecture :

a_link_resolved : F

a_content_type :

a_full_text : T

a_storage_type :

a_special_app :

a_effective_date []: <none>

a_expiration_date []: <none>

a_publish_formats []: <none>

a_effective_label []: <none>

a_effective_flag []: <none>

a_category :

a_is_template : F

a_controlling_app :

a_extended_properties []: <none>

a_is_signed : F

a_last_review_date : nulldate

INTERNAL ATTRIBUTES

i_is_deleted : F

i_reference_cnt : 1

i_has_folder : T

i_folder_id [0]: 0c00110f80000105

i_contents_id : 0000000000000000

i_cabinet_id : 0c00110f80000105

i_antecedent_id : 0000000000000000

i_chronicle_id : 0900110f8000396c

i_latest_flag : T

i_branch_cnt : 0

i_direct_dsc : F

i_is_reference : F

i_retain_until : nulldate

i_retainer_id []: <none>

i_partition : 0

i_is_replica : F

i_vstamp : 0

kcvipin

Thanks for the quick response but this seems to be using tha IAPI command. I am looking for the changes at DA/Content server side which can be made one time and these other version option should be made available to the user whenever they create a new document using the UI client.

Any ideas?

lastnitescurry

some Documentum Clients and versions of clients would allow what you want and in other clients it has been disabled. Have not tried it in WDK land (DA/Webtop)...

Have you tried adding say "2.0" or "0.1" into the version label text box of the checkin dialog?

Changing read only attributes, i.e. starting with "r_", is not recommended.... That IAPI probably worked as the user did it as a super user.

PK4D

You can do it through DFC so it can be done in WDK and BOF. But the real issue is that once you replace the versioning scheme with a custom one you probably need to take it over for all sorts of features that rely on version labels.

My suggestion would be to come up with an alphanumeric symbolic labeling scheme (say A0.1, A0.2, etc.) and then use the standard way of adding version labels to achieve your goal. That way you will let Content Server manage the implicit labeling (index 0, number based) and can be assured that you are not messing anything up.

Hope this helps,

Pawan