How do I specify default lifecycle for some custom type by Composer?

Hi everyone,

Is there way to specify default lifecycle for some custom type by Composer?

I've found that this functionality is missed in Composer, isn't?

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

foroor

Yes, you are correct; Composer does not expose this functionality. We do have a feature request for this but it is not currently planned for the next release.

All comments

Francois Dauberlieu

If you attach the lifecycle to your templates, then no problem, you'll have it when creating a new doc

Zakusov

What do you mean by "templates"?

Francois Dauberlieu

The templates for this document type in your /Templates cabinet

mszurap

I haven't seen the default lifecycle in Composer too... But probably you can assign the default one to the type within post-installation script.

Sergey, just to warn you, You have to be careful with default lifecycle. Once I had a misterious problem when I attached lifecycle by API (attach command) without specifying the policy id (so it assigns the default one). The problem was that I wasn't able to promote objects because of permission problems when I already have set up the proper lifecycle.

So the catch is that you pack your types and business policies in a DocApp (in my case that was it), install it to the target docbase.

I've set up everything, with ACLs on the dm_policy, it worked fine. After a time it just not worked as before. The problem came from the event when somebody installed an another DocApp to the Docbase with same object type. The docapp has overwritten the old object type, and brought it' piggy-back policy, so after that I had two different dm_policy objects with the same name, and the default became the one which was installed last time, containing a dumb ACL.

So, the best practice is to specify the policy id.

Maybe that's because this feature is removed from Composer?

Zakusov

Hi Miklos,

Yeah, in this case it is a good reason to remove (or do not implement) the functionality.

However there are guidelines (in some reference guides) to use dmi_dd_type_info to get default lifecycle and this method is not deprecated yet.

foroor

Yes, you are correct; Composer does not expose this functionality. We do have a feature request for this but it is not currently planned for the next release.