BRIX 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:
- System apps.
- Workspaces that are part of system solutions such as CRM, Incoming Payments, Marketing, Live Chats. Access to these workspaces depends on the licensing of your BRIX delivery.
By default, built-in workspaces include built-in apps with preconfigured forms.
Export a built-in workspace
You can use built-in workspaces in other apps, for example, in their business processes or app item forms, then export your solution from one company to another.
Let’s look at various cases of export:
- 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 BRIX. If you use a custom app that does not belong to the Contracts workspace, an error will occur during export.
- Export an entire built-in workspace.
You can export the entire built-in workspace as a separate system component. When importing it to another company, all its components will be uploaded: apps, pages, custom widgets, business processes, etc.
- Export of the built-in workspace as part of a solution.
All built-in workspace components are exported only if the entire workspace is included in a solution.
Important: If a built-in workspace is added to a solution NOT with all components, the processes and widgets (both built-in and custom ones) that are associated with the workspace will NOT be exported when the solution is downloaded. The workspace apps included in the solution, as well as processes and widgets associated with these apps will be downloaded. After import, the system workspace in the company will be updated: structures from the imported solution will be added to it.
Please note that if the Namespace constant is used in a widget or process script used within an app, this built-in workspace can be exported:
- As a separate system component.
- As part of a solution if the entire built-in workspace is included in a solution.
начало внимание
Using the Global or Namespace constants in scripts restricts the export of system components. Read more about it in the Global constants in scripts article.
конец внимание
Built-in apps
The built-in apps located in built-in workspaces are preconfigured and ready for use. These are:
- In the System apps workspace: My legal entities and External users, Service schedule, and Employees.
- In the CRM workspace: Leads, Deals, Companies, and Contacts.
If you navigate to a built-in app page, the underscore prefix appears before its name in the address bar, for example, _clients/_contacts.
начало внимание
You cannot export a built-in app as an individual system component, nor is it possible to copy or delete it.
конец внимание
Export a built-in app
Export behavior:
- A built-in app can only be exported as part of a built-in workspace or a solution.
- If you export a built-in app together with a built-in workspace as part of a solution, all the structures (processes and widgets) associated with the app will also be exported.