• In the class diagram, mask operations in a class using "Mask.../Content" right-click menu entry on the class element.
• In the UML explorer, reorder operations in the target class. To reorder an operation, select it and use "Move up" and "Move down" arrows present at the top of the UML explorer.
• In the class diagram, unmask operations using "Shift+O" shortcut on the target class (or Drag&Drop operations from explorer to the diagram).

Here's how to create several instances of the same kind of element:

• Instead of clicking on the element's creation button, double-click on it.

• Each time you click within the diagram, the relevant element will be created without having to re-select the element type.

• To exit the "repeat creation" mode, simply click on another element creation button or on the arrow button (cursor icon, top of the palette).

Modelio uses XMI for exchanging UML models to and from other tools (XMI 2.0).

The XMI Import feature enabling the import of a model from another tool is available in all editions of Modelio, including the Free Edition.

The XMI Export feature is only available in the Enterprise Edition of Modelio.

Please note that although XMI is an OMG standard, XMI files very often come in different flavors depending on the specific tool implementation. You  may therefore encounter some limitations when importing/exporting models to and from non-official variants of the XMI norm.

The reason is probably that the class hasn't been marked as being a “Java Element”. This can be done in the Java Property tab.

Modelio has a very elegant way of distinguishing between “analysis” elements that do not need code generation (typically PIM elements in MDA terminology) and model elements that are really Java elements and that require code generation (usually called PSM elements in MDA terminology). This enables the clear separation of model parts representing the business model or the application concepts for analysis purposes in non Java element dedicated packages, from Java generated elements in specific packages that have been set as “Java Element”.

Modelio Java Designer will therefore only manage those elements which are marked as being “Java Elements”. Note that this rule not only applies to code generation but also to other Modelio Java production and automatization features that will only be run on “Java Element” objects (example: accessor generation for class attributes).

Modelio Java Designer will automatically set the “Java Element” mark on each sub-element of a “Java Element” marked package. Therefore it's a good practice to create this kind of “Java Element” top level package and to create all the Java model elements in it.

Model components are used to package a set of model elements along with a set of additional files into a single archive file.

Model components are then deployed in a Modelio project where the UML model elements they contain become available in read-only mode (ie, they cannot be modified in the project where they are deployed).

The typical use of Modelio model component technology consists in providing model components for external libraries like the Java JDK. Once the JDK model component has been deployed, all the classes of the JDK become available for Java modeling. 

Typically only a simplified and reduced part of the model is contained in a model component (ie, packages and classes but no methods and no code). Therefore deploying a model component like the JDK preserves accurate modeling (all classes are present) while avoiding the burden of a huge model (the JDK is indeed a real piece of code!) and related potential performance issues.

Note that the Modelio Enterprise Edition enables you to create and package your own model components. This can be efficiently used to organize large team activities in a reliable process where each team can regularly deliver official revisions of the components it is responsible for to other teams. These deliveries are then based on the project schedule.

Both team independence and team synchronization can simultaneously be promoted when using the Modelio model component technology.

You can move from Modelio Free Edition to Modelio Enterprise Edition.

Modelio Enterprise Edition can read a project (.ofpx) from Modelio Free Edition, and you will be able to load modules from Modelio Enterprise within this project. The reverse is not possible.

Don’t use “CRTL C” or “Copy” in Modelio diagrams. These commands work in the explorer and copy the “semantics” (structure and definition) of an element or group of elements, but are not adapted to diagrams.

In Modelio diagrams, there is a specific command in the top right corner of the diagram (“Copy diagram into the clipboard”), which copies the entire diagram. You can then use the usual Windows “Paste” commands.

With Modelio, you can quickly browse and update your models in the explorer using your keyboard:

• You can navigate within your model in the explorer by using the arrow keys on your keyboard.
• To edit a selected element, press the "F2" key. This is far more practical than double-clicking with your mouse (mouse handling, context-sensitive interpretations, etc).
• To validate a name change, use the carriage return key.
• To expand a node, press the carriage return key.

And don't forget the “Clone” or “Create sibling” buttons in the explorer, both of which are very useful for fast creation.

For detailed editing (more than just the name), use the element's UML properties zone.

Yes. To create a qualifier, you have to use the explorer. The result will appear wherever the association is displayed in diagrams.
Right-click on the “association end” (where you want the qualifier to appear) in the explorer, and select “Create a UML element/Qualifier”.

In order to be able to resize a composite state, select the state by clicking in the upper part that contains the name. It will then be possible to resize the state as you wish.

Modelio provides a powerful and general purpose “trace” mechanism relying on the standard UML dependency.

The Fast Link editor provides a means of tracing two model elements. Select the task in the BPMN editor, put the Fast Link Editor in edit mode (using the “pen” icon), drag & drop the traced use case from the explorer to the Fast link Editor.

You can also drag & drop the use case in the BPMN diagram, and create a trace link in the BPMN diagram if you want to show it in the diagram.