The Library Concept

Using libraries has several advantages for developers:

You can provide additional data types and operations via libraries.
You can reuse implementations you have already developed with the Builder.
You can use libraries for modularization:
- Implementations can be recycled in various processes via libraries.
- Multiple developers can contribute to the same process implementation by working on different libraries.
You can add features to the Designer, for example access to backend systems, via libraries.
You can use different versions of the same library as the library administration supports versioning.

Library Usage in Designer

As libraries are developed with the Builder, you need to upload them to the Designer to make them accessible in your services.

In the Designer, you upload your libraries to a namespace. This is done in the Libraries section of the Designer administration. The uploaded libraries are then available in all services created in this namespace. How to upload your libraries to the Designer is explained in detail on page Administrating Libraries.

Once a library has been uploaded, you can add it to any service created in this namespace. To do so, open the service and go to the Libraries folder in the Service panel .

Go to page Adding and Updating Libraries for detailed information on how to add a library to a service. Refer to Modeling Execution pp. for further information about the usage of libraries during modeling.

The Service Panel

The libraries you have added to a service reside in the Service panel.

Designer > Working With Libraries > service_panel_default.png

If you use the panel preset of the BPMN editor, the Service panel is displayed in the upper left corner of the editor.

Designer > Working With Libraries > service_panel.png

The Service panel gives you direct access to all libraries of your service, and thus to all of your predefined classes, interfaces, operations and parameters.

Open menu Libraries in the Designer administration to upload your own libraries.

A library can contain the following elements:

Icon	Name
	Package
	Class
	Property
	Interface
	Operation
	Parameter

To expand an element in the tree, click on Documentation Library > _designer_images > icon_expand.png .
Useif you want to collapse a tree below an element.

Designer > Working With Libraries > library_element_documentation.png

Each library element can have a documentation. Hover your mouse on a library element to see if documentation is available. This is indicated by the Documentation Library > _designer_images > icon_documentation.png

icon. The documentation is displayed as a tooltip.

For easier reading of longer documentation, you can click the icon to see the complete documentation in a pop-up window:

Designer > Working With Libraries > library_docu_popup.png

Designer > Working With Libraries > library_copy_content.png

You can also copy & paste content from a library to the data model of your service: packages, classes, properties, operations and parameters - including their subelements.
The implementation of a copied operation, however, will be empty.

In addition to imported libraries with predefined data types, you can use the provided Base Types, or you can create your own data model.

Documentation Library > _designer_images > bridge_base_types.png

Designer > Working With Libraries > adding_data_model.png

You can also define your own data types in folder Implementation. You can add your own packages, classes, interfaces, operations, properties and parameters.

Go to page Modeling Data Structures for more detailed information on how to work on your own data model and to page Modeling Data Mapping for further explanations on how to define mappings between data types.

BRIDGE
- Base Types
- Builder User Guide