BPMN Import Tool Window

The BPMN Import tool window can be used for viewing and editing model-wide and user-specific application configurations when importing BPMN files.

Purpose

The BPMN Import tool window can be used for viewing and editing model-wide and user-specific application configurations when importing BPMN files.

Call

Open the BPMN Import tool window with  Import/Export>Import>BPMN>Configure.

Structure

The BPMN Import tool window consists of the following sections:

  • Determine storage location in the model

    You can define whether the BPMN model elements are placed in the currently-selected or in a certain structure element of the model.

  • Import options

    You have various options available when importing.

    • Use sequence flow name as condition

      If set, the name of a sequence flow is used as local condition, if there is no condition set and if the sequence flow comes from a gateway or an activity. The direction of the gateway must be diverging or there have to be several outgoing flows.

    • Name event definition only

      If set, an event with an event definition is unnamed. A newly created event definition is always named according to the associated event.

    • Create event definition

      For an event without event definition a new event definition is created.

    • Create business object

      For a data object without business object a new business object with the same name is created.

    • Use global state

      At a data object a global state is used if there is a business object.

    • Reuse global elements

      A global element (business object, data store, definition of a logical expression, error, escalation, event definition, global condition, global task, message, service operation, service interface, signal) is reused if there is an element of the same name. The elements are searched in the system model in which you import.

    • Import empty sub-process as call activity

      A sub-process without content is imported as call activity. Hints: A sub-process with lanes is always imported as process and call activity calling it. A sub-process which is triggered by an event is always imported as sub-process. A sub-process which has incoming or outgoing message flows is always imported as sub-process.

    • Import sub-process as call activity

      A sub-process is imported as call activity. A new process is created from its content and the call activity calls the process. Hints: A sub-process with lanes is always imported as process and call activity calling it. A sub-process which is triggered by an event is always imported as sub-process. A sub-process which has incoming or outgoing message flows is always imported as sub-process.

    • Complete call activity

      In the importing system model an already imported call activity without a called element is completed by setting the imported process as called element.

      Activating the option modifies Innovator diagrams upon import.

    • Scaling (from 100% to 300%)

      The imported diagram is enlarged. The distances between nodes are enlarged.

  • Stereotype selection

    Multiple create templates for model element types to be imported can exist in the importing model when BPMN elements are adopted. You can select which create template should be used in the Stereotype selection section for all element types with more than one create template in the model that you have the execution right for.

    Note

    Template selection depends on the execution rights of the current role. Use precisely the role which should also import when setting-up and saving as user-specific configuration.

    Only create templates with a stereotype that has a stereotype of a BPMN diagram as assigned element for the package element type.

    You can set which create template should be used for the event definition, task, gateway, data object and definition of a logical expression element types, depending on the respective type of the element type.

    The stereotype’s name is exported when exporting from Innovator into a BPMN file and used when possible upon import, independently from the stereotype selected here. Creating process elements in the original state is supported here.

  • After Import

    Activate the Open diagrams after import check box to open the imported diagrams in the model editor afterwards. Ensure that the number of diagrams listed is not too large.

How to proceed

Set the options you want to reuse for BPMN import in the BPMN Import tool window.

Save the configuration in the BPMN>Import>Configuration ribbon group as a user-defined configuration and add a suitable name in the dialog with  Save.

Check the successful import using the stored options.

  • If your import configuration requires it, then select the storage location in the model.

  • Select Import/Export>Import>BPMN><User-Defined Configuration>. The standard dialog for selecting one or more import files appears.

  • Select the import files and click on Open.

  • Check the import result.

Open the Saved Configurations dialog with  Manage; you can provide the import configuration as a model-wide configuration for other users upon successful check.

Your user-defined and all model-wide configurations can be accessed in all models under Import/Export>Import>BPMN.

Related Topics Link IconRelated Topics

Further Information

https://www.omg.org/spec/BPMN/