Skip to main content
Version: 8.3

Regular package

Creatio includes the following types of regular packages:

Preinstalled packages​

Preinstalled packages are available in the workspace by default. They cannot be modified. Creatio marks preinstalled packages in the Configuration section using scr_Package_Blocked.png.

Creatio includes the following types of preinstalled packages:

  • Base packages. For example, CrtBase, CrtNUI.
  • Third-party packages. These packages are installed from *.zip archives using Creatio IDE or the WorkspaceConsole utility.

View base packages in the table below.

Package name

Description

CrtBase,
Base

Base schemas of the primary objects and Creatio sections, as well as connected objects, pages, process schemas, etc.

Platform,
CrtPlatform7x

Modules and pages of the List Designer, Dashboard Designer, etc.

Managers,
CrtManagers7x

Client modules of the schema managers.

CrtNUI,
NUI

Functionality connected to the Creatio UI.

CrtUIv2,
UIv2

CrtDesignerTools,
DesignerTools

Schemas of Designers and their elements.

CrtProcessDesigner,
ProcessDesigner

Process Designer schemas.

Users create various schemas that must be saved to a user-made package. A fresh Creatio installation has no packages open for modification except for the Custom preinstalled package. You can add schemas to this package manually using the Configuration section and the Advanced settings tab in No-Code Designer.

For Creatio 8.3.1 and earlier, the Custom package has the following specific features:

  • The Custom package cannot be added to the version control system. As such, you can transfer the package schemas between environments only using the export and import functionality. Learn more: Transfer packages.
  • Unlike other preinstalled packages, the Custom package cannot be exported to the file system via the WorkspaceConsole utility.
  • The Custom package has all of the other preinstalled packages as dependencies. If you create or install a user-made package, the new package becomes a dependency for the Custom package automatically. Therefore, always place the Custom package the last in the package hierarchy.
  • User-made packages cannot have the Custom package as a dependency.

For Creatio 8.3.1 and earlier, you can use the Custom package in the following cases:

  • You will not transfer changes to a different environment.

    The Custom package does not support the standard package import mechanism for delivering customizations. Therefore, if the Custom package is your current package, you can only transfer the bound data to another user-made package via database queries. We strongly recommend against this method as the changes can affect the database structure and render Creatio inoperable. If you have to modify Creatio functionality significantly, use a user-made package.

  • You customize Creatio either manually or using Freedom UI Designer, and the changes are minor.

  • You do not need to use a version control system.

Since version 8.3.2, Custom package is a regular package and has the following specific features:

  • The Custom package depends only on the CrtCore package instead of depending on all packages. In existing environments upgraded from earlier versions, the Custom package dependencies remain unchanged to ensure backward compatibility.
  • When you create or install a package, the Custom package no longer becomes dependent on it automatically.
  • The Custom package can be added to the version control system.
  • The Custom package can be exported to the file system using the WorkspaceConsole utility.
  • User-made packages can depend on the Custom package. You can add this dependency manually or it can be added automatically when Creatio adds the required dependencies.

User-made packages​

Use a user-made package to develop additional functionality or extend existing functionality.

Creatio includes the following types of user-made packages:

  • User-made packages created by other Creatio users. User-made packages are locked in the version control system. They cannot be modified. Creatio marks user-made packages in the Configuration section using scr_CustomPackage_Blocked.png.
  • User-made packages created by the current user or retrieved from the version control system. They can be modified. Creatio marks user-made packages in the Configuration section using scr_CustomPackage.png.

Before you start development, change the current package. To do this:

  1. Open the System settings section. To do this, click btn_system_designer_8_shell.png in the top right → System setup → System settings.

  2. Open the "Current package" (CurrentPackageId code) system setting.

  3. Change the properties of the system setting.

    Property

    Property description

    Default value

    The name of a user-made package

    To prevent system issues, since version 8.3.2, it is not possible to deactivate or delete a package if it, or any of its dependencies, is set as the value of the Current package (CurrentPackageId code) system setting. If you try to deactivate or delete such a package, Creatio displays a detailed error message.

  4. Save the changes.

As a result, Creatio will add all schemas to the specified user-made package.

See also​

Delivery using the Configuration section