Importing models

I imported a workflow model from ProVision into M3. I then deleted it and tried to re-import another model. This failed because of name conflicts with existing objects.

I have tried to delete all the objects that were imported with the first model but this fails for several objects because it says they have associations to other objects. How can I discover what the associations are that are preventing these objects from being deleted?

I have also tried to re-import the first model but it is also fails because of object name conflicts, even though these are the same objects that are in the model. Is there a way round this?

Find more posts tagged with

BPM

Comments

Nate_Kindt

Alison,

Thanks for reporting this issue.

We've identified the problem as being specific to Workflow models. If an object is placed within a workflow lane and then excluded, when you attempt to delete it from the object inventory you will receive the error message indicating that the object still contains associations and cannot be deleted.

We've escalated the issue to development. Until this is resolved in the application, we've found the following workarounds that should allow you fully delete the objects and re-import:

Create a new workflow model and, using the Add Entity functionality, re-add each workflow lane and activity to the model. Ensure that none of the activities are present in the workflow lanes and exclude them again. Save the model and you should now be able to delete each of the activities and workflow lane objects.
For each object you cannot delete, open the object from the Object Inventory, switch to the Associations tab, and click OK to close the object again. You should now be able to delete the activities. Once the activities are deleted you can proceed with attempting to delete the workflow lane objects.

We will update this thread again when we have fully resolved your issue.

Thank you,

Nathan Kindt

Metastorm M3, Quality Assurance

Nate_Kindt

Additionally, to ensure that you don't have to deal with this problem in the short term, if you move the objects from within the workflow lane to below the model (outside of the workflow lanes), then you should be able to delete them without using the two workarounds we have provided.