Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.

Image Modified

To copy a module, make sure you are in the Edit project structure mode.

...

Select the module by clicking left and then right click on a module to see the menu. Choose Copy module:

Image Modified

When Copy module is pressed, the following dialogue appears:

UI Text Box
typewarning

New screenprint will be available after new Copy module dialog.

Image Removed

Image Added

Type in the new name, this name has to be unique within the project. Choose whether the module is an implementation or not. By default each copied module is an implementation module, regardless of the fact whether the source module is an implementation module or not.

...

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.

Image Modified

The AnotherPermit module consists of the parts as depicted below after copying the module Permit to AnotherPermit and linking it to its base module Domain:

...

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.

Image Modified

The AnotherPermit module consists of the parts as depicted below after copying the module Permit to AnotherPermit and adding everything from its base modules:

...

In the example shown above, everything from the modules Base, Domain and Permit is combined into the module AnotherPermit. This principle of combining is sometimes referred to as flattening ("platslaan" in Dutch) or rolling up ("oprollen" in Dutch). The result is that the module AnotherPermit contains Customer, Address and Permit and all of these elements are available in their newest, i.e. most specialist, manner. This is visualized by B' as part of the Customer entity in the copied module. The fact that B' is shown in the Customer entity does not mean that B is specialized in the copied module however. It merely means that the specialized version of B from the source is copied to AnotherPermit. 


UI Expand
expandedtrue
titleRelated documentation

Reporting and sharing data with other systems

UI Expand
expandedtrue
titleRelated articles

Content by Label
showLabelsfalse
max5
spacesBKB
showSpacefalse
sortmodifiedshowSpacefalse
reversetrue
typepage
cqllabel in ("bq97","reporting") and type = "page" and space = "BKB"
labelsreporting bq97

 

...