Page History

Introduction

At some point in the development process, a business engineer might want to copy a module. This is most likely the case with interaction modules, therefore the functionality to copy modules is only available for modules of this type. To demonstrate this functionality, the example project shown below is used. Only the four interaction module are relevant in this example.

...

In the example above the focus is on the module Permit, but since it is linked to Domain and vicariously to Base, these modules are in scope as well. In the example, the module Base has an element (in this case an entity) Customer with attributes A and B. In the module Domain, this entity is visible and in Permit it has been specialized. This specialization comprised an adjustment of attribute B and the addition of attribute C. Entity Address originates in module Domain and has not been specialized further. Entity Permit originates in module Permit.

Link to base module

The radio button Base has two options. When the option Link to base module is chosen, the copied module will be linked to the same module that the original module was linked to. In essence, Permit and AnotherPermit are exactly the same module.

...

The content of the example above is exactly the same as the original, except of course the name of the module.

Add everything from base module(s)

When the option Add everything from base module(s) from the radio button Base is chosen, the copied module will contain all elements from the original module and all modules that are directly and indirectly linked to the original module.

...