Documentum D2 4.1 Extended creation matrix, how to use?

Hi,

I see with 4.1 a new feature Extended creation matrix is introduced which can be context based creation profile. Is it just for dm_folder? Don't find proper documentation for its usage?

Do I need to have at least 1 non-context based creation matrix anyways?

How to apply it and how is it useful if I can apply based on groups + content object type to have different default value parameters?

Regards,

Anurag

Find more posts tagged with

Comments

anuragjain

Not working. Any ideas

hetalvdoctor

Hi Anurag

Did you figure out how to achieve this?

Regards

Hetal

EktaVegad

Hi Anurag,

How to apply it and how is it useful if I can apply based on groups + content object type to have different default value parameters?

Whatever type you configured in context (either document or folder) its working.

If you have assigned type as Folder & condition as folder('<folder name>',descend) in D2-Config then in D2 when user selects that folder & import the document then extended creation matrix will apply.

For different default values means? default values for different types can be configured in Extended matrix.

Do I need to have at least 1 non-context based creation matrix anyways?

No, its not necessary

hetalvdoctor

Hi Ekta,

I have created a very simple extended creation profile

Name = dm_folder

Folder Properties used for creation = r_object_type

Label = General Import

I have created a context with selection = dm_folder

I have not put any condition

I have marked it appropriately in creation matrix as well

Still when i am trying to create new document, i dont get the "General Import" choice

Regards

Hetal

AsishaKumar

Hi All,

Here are the exact difference between Creation Profile and Extended Creation Profile.

Creation Profile:

It tell us what one group of users can create in D2
Creation Profile is group based, i.e if we are creating normal creation profile we can assign it to a specific group only.
There are no option to apply normal creation profile to a specific context

Extended Creation Profile:

It tell us what can be created based on context
Extended Creation Profile is context based, i.e if we are creating extended creation profile we can assign it to any context.
Since its context based, it can be assigned to groups, types, folder locations.

Business Scenario:

I have one Cabinet called 'Contracts' and it contains below 2 folders.

/Contracts/Own Contracts
/Contracts/Third Party Contracts

The requirement is, I have to apply Creation Profile based on folder location. If user creating documents under /Contracts/Own Contracts folder or its sub folders, Own Creation Profile will be applied. If user creating documents inside /Contracts/Third Party Contracts folder or its sub folders, TP Creation Profile will be applied. If user creating documents any locations other than these 2 folder locations General Contract Creation Profile will be applied.

Solution:

Create normal creation profile General Contract Creation Profile using on the user's group.
Create extended creation profile Own Creation Profile.
Create extended creation profile TP Creation Profile.
Create Own Contract Context for type dm_folder and condition=FOLDER('/Contracts/Own Contracts',DESCEND).
Create Third Party Contract Context for type dm_folder and condition=FOLDER('/Contracts/Third Party Contracts',DESCEND)
Now in matrix assign Own Creation Profile extended creation profile to Own Contract Context and TP Creation Profile extended creation profile to Third Party Contract Context.

After changing the configuration if changes are not reflecting restart the app server and check.

Tips and Tricks while using extended creation profile:

Since extended creation profiles are context based if we have created context using types only(i.e either Folder type or Document type) and applying extended creation profile for it then we should select the object first then create the new document or create the version. This is because until and unless object is not selected exclusive type based context can not be resolved and default normal creation profile will be applied.