Imagine we create a page with the name "Home". In most of the workbenches there exists a @WorkbenchScreen named "HomeScreen".

For every page created, the system creates automatically an screen named <pageName> + "Screen". This means an screen named "HomeScreen" is created for the page "Home". This causes some undesirable side effects, as it clashes with any existing predefined screen in the system:

• Javascript error displayed in the browser's console:

16:33:41 SEVERE [LogConfiguration] Conflict detected: Activity already exists with id HomeScreen
Error: RuntimeException: Conflict detected: Activity already exists with id HomeScreen
    at Object.ESb_g$ [as createError_0_g$] (org.dashbuilder.DashbuilderShowcase-0.js:33739:10)
    at Object.OSb_g$ [as initializeBackingError_0_g$] (org.dashbuilder.DashbuilderShowcase-0.js:33794:44)

• Page not listed in the page selector dropdowns. Both in the security UI and the navigation tree editor.

A feasible solution must ensure a proper naming procedure to avoid any name clashing between user created pages and existing developer created artifacts.