Question about Composer "artefact import" function

Hello!

I'm trying to create a Composer project from existing TaskSpace application. I'm using version 6.6 of taskspace and composer. Composer successfully imports Documentum artefacts from repository into new project. But I found that some artefacts are missing: some form templates, object types and cabinets. They exist in repository but absent in project! Of course I can add this objects manualy, but this is very difficult for large application.

Am I doing something wrong? Or it's a Composer bug?

Find more posts tagged with

Comments

Miller-zzMST

Hi Nikitozzy,

Please, make sure that those objects are included in taskspace application. For example, all Forms must be present in Component node (Configuration tab), Process must be included in Processes node, etc.

But cabinets wouldn't imported in Composer project automatically. You will need to create them manually or by Installation parameters.

~ Konstantin

Nikitozzy

Thank you for reply, Konstantin!

Yes I know that components must be attached to application. And this is the main point of my confusion: all of this objects are in my taskspace application!

lastnitescurry

I recently migrated a taskspace application from DEV to UAT.... I was not the orginal developer and was tasked to bring order to chaos and make the migration process repeatable. I broke the application up into 4 Composer projects, and a few DQL scripts to do things that Composer does not.... For example groups.... not all groups would be migrated and group structure would not be maintained

XX_1_AclsAndFolders

XX_2_TypesAndLifecycles

XX_3_BofAndMethods

where XX is the name of the taskspace application

Nikitozzy

Thank you, Brian!

Looks like that causes of my troubles lies in a wired import algorithm of Composer application.

lastnitescurry

there are definately some strange oddites with Composer.... I used the "new project from Taskspace app" option. I selected my other projects as references but stuff was still imported, for example types which I had in the Types and Lifecycles project.

Was working on the philosiphy that the taskspace app will change hence the best way to deal with that is to repeat "new project from Taskspace app" and delete the previous composer project. Types, lifecycls, folders, acls, .... should not change so often

Miller-zzMST

What version of Composer are you using? And can you check it's log after importing application?

~ Konstantin

Nikitozzy

Brian Dinneen wrote:I selected my other projects as references but stuff was still imported, for example types which I had in the Types and Lifecycles project.

Yes, I saw that to.

Konstantin Melnik wrote:What version of Composer are you using? And can you check it's log after importing application?

As I said, I'm using Composer 6.6. And there is no error messages after Composer project creation from taskspace application.

Miller-zzMST

As I said, I'm using Composer 6.6

Oh, sorry.. where is my eyes was

May be the best way is to create a support request? May be support team could find out the cause of such issue.

~ Konstantin

Nikitozzy

Konstantin Melnik wrote:
May be the best way is to create a support request? May be support team could find out the cause of such issue.

Yes, I still thinking about that. Anyway it's a good idea, but general obstacle is in bug repeatability - sometimes I have such problems and somtimes not. Right now I'm not ready to formulate support request.

Miller-zzMST

BTW,

there is Composer patch 06. May be it can some ease the situation.

Nikitozzy

I'm using patch 07