Low-code designer > Workspace / Built-in workspaces

Built-in workspaces

ELMA365 comes with a set of ready-made workspaces installed by default. The apps and item pages within these workspaces are pre-configured. These workspaces are referred to as built-in workspaces.

These are:

 

The CRM, Live Chats, and Projects workspaces are part of the ELMA365 CRM, ELMA365 Service, and ELMA365 Projects built-in solutions. Access to these workspaces depends on the licensing scheme of your ELMA365 delivery.

Default apps included in the built-in workspaces are referred to as built-in apps.

Export a built-in workspace

You can use built-in workspaces in other apps, for example, in business processes, or on app item pages, and export your solution from one company to another.

Let’s look at two cases of export:

  1. Export a component associated with a built-in workspace.

Let’s say you want to export the Contracts workspace. It includes the contract approval business process linked to the Companies built-in app. When exporting and further importing the workspace, no problems will occur, as any company has the same built-in app in ELMA365. If you use a custom app that does not belong to the Contracts workspace, an error will occur during export.

  1. Export an entire built-in workspace.

Important: A built-in workspace within the solution is not exported entirely. When exporting the solution, all apps included in this workspace and all structures (processes and widgets) at the level of these apps will be exported. At the same time, any processes and widgets (system and custom) that are at the workspace level will not be exported. That is, the built-in workspace in the solution is only exported at the level of its apps.

After importing the solution, you will see the built-in workspace in the left menu, as well as the processes and widgets at the workspace level that were in it before the import.

Please note, that if a Namespace constant is used in a widget or process script at the app level, this built-in workspace:

  • Can be exported as a separate system component.
  • Cannot be exported as part of a solution.

начало внимание

Using Global or Namespace constants in scripts restricts the export of system components. Read more about it in the Global constants in scripts article.  

конец внимание 

Found a typo? Highlight the text, press ctrl + enter and notify us