BlueDolphin Release May 2018

Posted on

BlueDolphin en AVG

Release BlueDolphin May 2018

May 8th 2018, Development Team ValueBlue

  1. The AMEFF export
  2. The AMEFF Import
  3. Define a landingpage per user-role
  4. Legenda included in printout
  5. Filter and search in Legenda
  6. Search for views in the menu

* Showstopper Bug-Fixes

1. The AMEFF export

Thanks to the AMEFF export you can download views as a file. In this file the complete visualization can be found including all subjacent relationships that belong to objects on the view. Even when relationships are invisible, they are included in the export.

  1. The export consists of:
    1. The objects of the view;
    2. The subjacent relationships;
    3. Blocks of Content;
    4. The view
  2. The export does not contain:
    1. View objects to navigate;
    2. Graphical shapes.


  • Select the view you would like to export;
  • Select “Download” in the menu at the right side of the screen, below the three dots
    see figure
  • Choose “AMEFF” when BlueDolphin asks you for the type of file that needs to be exported;
  • Click OK.
    see figure

* The file will be saved in the regular download folder,  just like when downloading PNG, SVG and PDF.
** The name of the file will have the same name as the title of the view, carrying the extension “.xml”.

2. The AMEFF import

Using the AMEFF import you are able to import complete AMEFF files into BlueDolphin. Think of files that are created in Archimate 2.1 applications or an AMEFF file that was exported from BlueDolphin earlier.

The import consists of:

  • Objects;
  • Relationships;
  • Views;
  • Blocks of content;
  • Graphical shapes.

Please note: only those components included in BlueDolphin are imported.

The import does not yet support:

  • ArchiMate 3.0. Throughout this year BlueDolphin will be ArchiMate 3.0 compliant;
  • Junctions;
  • BPMN views and objects.

Step 1

Carrying out imports requires administration rights.

  • After navigating to the admin-screen, you click the option“Admin”,  “System” followed by “Import”;
  • Click “Upload Ameff file
    see figure
  • Select the specific AMEFF file from the “Open” dialogue
    see figure
  • Just wait a second before the three buttons at the right side of your screen are clickable. Then, click  “Map and Import Objects”. This is the first out of three options that needs to be clicked on;
    see figure
  • If the name of an object-definition in an export does not correspond to the object definitions in BlueDolphin, this definition should be mapped. This is realized by  selecting the object-definition from the environment that suits the object-definition in the export-file.
    see figure 
  • If the  object-definitions are mapped, you are free to choose your type of import. The following options are displayed:
    • BlueDolphin maps the imported objects automatically;
    • I want to decide to which BlueDolphin object the imported items are mapped;
      As soon as the import setting are selected you can press “Start” to create objects in BlueDolphin.
      see figure

Step 2

After a successful import, the second checkbox “Map and import relationships” can be ticked. (The first checkbox already contains one).
see figure

Now, a  new field appears on the right. Just like the object-definitions, it could be that the name of a relationship-definition form an export does not correspond one of the relationship-definitions in BlueDolphin. In that case you carry out just the same: map the relationship-definition. Mapping is easily carried out by selecting the relationship-definition when you find yourself in the environment that suits the relationship-definition in the export file; see figure.
Now click the button “Validate Mappings” to check if the relationships can be created indeed. Afterwards, press “Start” to create relationships in BlueDolphin.

Step 3

A third check mark has appeared. Now click “Import Views” to start importing.
see figure

It may happen that an export file contains a wider variety of object-definitions and relationship-definitions than the amount that is present in BlueDolphin. If so, this screen appears. This could enhold that views are not imported completely. When you want to ensure the specific file is imported completely, object- and relationship-definitions should be created. These definitions need to match the definitions in the export.

Please note: be careful, seen the fact a conventionmodel in BlueDolphin is mostly well thought out and as efficient as possible. Do think twice before enlarging the existing conventionmodel. Once a change is made, a reverse is quite challenging.

Import succeeded

When the import is a success, the objects, relationships and views are created. They can be found in the section object and views in BlueDolphin.

3. Define a landingpage per user-role

Defining a landingpage per user-role especially benefits user-efficiency. Users directly enter a location/view within BlueDolphin containing all relevant information. This view does not neet to be publishes, which makes maintaining the navigation structure a lot easier. The so called landingpage-view can be adjusted as often you want to, without interrupting the navigation to other views (seen the fact the URL stays the same).


Any administrator is able to carry out the following:

  • Navigate to Admin;
  • Select “Roles” in the menu “Identity and access”;
  • Select the user-role you aim to design the landingpage for and navigate to te field “Default startpage” , as shown here. Note that the URL is pre-filled and cannot be changed ( https://<sitenaam>

Please note: When a user has diverse roles, he or she will enter BlueDolphin finding the landingpage that belongs to his or hermost important post/role:

  1. Administrator;
  2. Regular users;
  3. Read Only;
  4. Manually created new roles.

Tip: whenever you need to navigate to a landingpage fast, this can be realized by one click only. Click“BLUEDOLPHIN” in the blue area and your landingpage will appear. See figure

  • Enter the desired URL in the text block and press “Save”
  • The landingpage now is active for users that belong to your the role you created the page for. Users that are already logged in, need to logout and -in once again to activate their new landingpage. See figure
4. Legenda included in printout

The following view in BlueDolphin will be printed in PNG, SVG or PDF like this. From now on the legenda is part of the printout. The location of the agenda depends on the position of the legenda in the view in BlueDolphin.

5. Filter and search in the legenda

The functions filtering and search  within the legenda make it a lot easier to create impact analyses and imply diverse insights. Thanks to this new feature you visualize  information on objects in BlueDolphin in no time: as it were you create a dynamic focus on views. Think of ‘blurring’ object-definitions as well as switching off colors in a conditional layout. Objects can be filtered based om type, properties or relationships. Like this other objects are moved to the background. Imagine the new dimension you will be creating using colors, when knowing these can be switched on and off.


  • Navigate to views and open a new view;
  • Select “Legenda” to activate the legenda;
  • Here you find an example in which a search area is included that searches for all content that matched the entered criteria.
  • When this search is completen, you have several options. You can for instance choose to “blur” or “light up” selected items, by clicking the “eye” behind the item. Searching in the legenda goes for:
    • Objects;
    • Relationships;
    • Conditional layouts.

Blur and light up

Each item in the legenda  has the option of clicking on the “eye”. By clicking “Obects”, “Relationships” and “Color-condition-title” all items are blurred or lightened up in one go. You can also choose to highlight or blur individual items.
See figure

When individual items are selected, you may want to delete the blurred items from the legenda. In that case you select the option “Remove hidden entries” in the legenda-menu at the righthand corner. And the other way around it works the same, but than the option “Show hidden entries” is displayed.
See figure
In case all filters and searches should be deleted, click “Reset Legend” in the menu. When a legenda-filter is activated this will be shown on the right at the legenda menu option, even when the legenda is not visible in the view. The red sign, disappears as soon as all filters are switched off.

Good to know: While discovering the options of blurring, lightening up and searching, you easily create diverse perspectives like:

  • The “route” of a roadmap, in which the  lifecycles of a view can be displayed, without having to display the end-result;
  • Where it is in a procesview that a singular application makes a connection;
  • Where it is in an architecture view that connected operating systems are present, without showing all software systems;
  • The connection of a specific department while looking at a view of applications.

6. Search for views in the menu

In the “Open View” menu, you now search for specific views while entering their name or content of which the desired view consists of. Here an example is to be found. In the open dialogue, the search area can be found in the lefthand corner. This saves you a lot of time seen the fact you do not have to scroll a list any longer.

Your search browses all views you have access to:

  • My views
  • Shared views
  • Published views

Showstopper Bug-Fixes

A large variety of bug-fixes were rolled out. Fixes that, in our point of view, may be classed as ‘Showstopper bugs’. These fixes raise the added value for many end-users.

  1. Relationships are updated when changes are made to data in a source;
  2. Relationship-labels are taken when carrying out an import;
  3. ‘Select all’ and ‘delete’ both perform as they should;
  4. The object-viewer only shows the alert ‘occupied’ when necessary;
  5. Dragging the anchor point of a relationship has been improved;
  6. Whereas relationships were sometimes not shown in a view, they are now displayed at all times;
  7. Stability-improvements related to front-end javascript errors were carried out;
  8. Stability-improvements related to refreshing complex BPMN views were carried out;
  9. PNG files are exported containing the contents of the view;
  10. When an actor is moved to a ‘pool’ in a BPMN view, while this actor is present in a swimming lane, inconsistency is no longer occurring;
  11. The export of logging activities works as it should;
  12. The object-viewer stays visible when a view is opened for a second time;
  13. Endles questionnaires can be created, whereas only 25 could be added to an object;
  14. In some cases scrolling resulted in visual duplications of the last item in the list of objects. This problem is solved;
  15. Thanks to improvements in terms of positioning objects in the BPMN views, objects are aligned nicely everywhere;
  16. The little black boxes that appeared in places of a relationship-description in a SVG export do not longer appear;
  17. Thanks to stability-improvement in ArchiMate views, little black boxes in views are a thing of the past;
  18. It is possible to delete relationship-definitions using ‘multiselect’;
  19. When duplicated objects, in a shared view, are deleted, all versions of the specific object are safeguarded in stead of deleted; 
  20. When adding multiple objects on a view, these objects are distributed among the view in stead of overlapping each other;
  21. Diverse language- and translation mistakes were solved;
  22. The browser stay stable, even when using hyperlinks in a BPMN task-description;
  23. The dragging of objects from the objects-browser was improved which makes dragging less prone to error;
  24. When duplicating BPMN views via ‘save as’, task-descriptions are correctly saved, whereas instabilities used to occur;
  25. Errors when creating relationship-definitions are solved;
  26. The layout and size of several buttons in the admin- and processing module now is in balance;
  27. When resizing the browser, the diagram in the objects-page always stay visible;

Security and stability improvement

  1. HTTP Strict Transport Security was switched on in all webserver endpoints. This is a BlueDolphin security-upgrade;
  2. The certificate of the BlueDolphin testenvironment is renewed;

We thank every user for his or her feedback over the last months. Thanks to your attentiveness, communication and creative thinking, we were able to make the contributions above.


Team ValueBlue