Skip to main content
Version: 8.1

Configuration elements of the Client module type

Level: beginner

A configuration element of the Client module type is a separate functionality block you can upload and run on demand. The purpose of the client module is front-end Creatio development.

Client modules have the following types:

Learn more: Client module types.

The items of the Add drop-down list in the toolbar of the Configuration section workspace represent the client module types you can add in Creatio IDE.

View the client module types in the figure below.

The Client module schema type in the Type drop-down list in the toolbar of the Configuration section workspace represents the client module. The client schema is the basis of Creatio configuration. As far as software implementation is concerned, a schema is a core class inherited from the base Schema class.

View the type of the client module schema in the figure below.

Implement a non-visual module

The Module schema type represents the non-visual module.

General procedure to implement a non-visual module:

  1. Open the Configuration section. Instructions: Open the Configuration section.

  2. Select a custom package to add the schema.

  3. Add a module schema. To do this, click AddModule on the section list toolbar. This opens the Module Designer.

  4. Fill out the schema properties.

    Property

    Property value

    Property description

    Code required

    The schema name

    Starts with the prefix. Learn more: Manage configuration elements. Can contain Latin characters and digits.

    Title required

    The localizable schema title

    The title of the configuration element schema is generated automatically and matches the value of the Code property without the prefix.

    Package

    The custom package where you create the schema

    The property is populated automatically and non-editable.

    Description

    The localizable schema description

  5. Apply the changes.

    If needed, use in the properties area to change the schema properties.

  6. Fill out the additional properties (optional). To do this, use in the properties area.

    View the additional properties in the figure below.

  7. Implement the functionality. The module name in the define() function must match the schema name in the Code property.

    Creatio displays the type of the error or warning – if any – to the left of the row number. Hover over the error type to view a tooltip with the error description.

  8. Save the changes.

Implement a visual module

Visual modules have the following types:

The Module schema type represents the visual module.

Freedom UI page schema

  1. Open the Configuration section. Instructions: Open the Configuration section.

  2. Select a custom package to add the schema.

  3. Add a Freedom UI page schema. To do this, click AddFreedom UI page on the section list toolbar.

  4. Select a template of the Freedom UI page to add based on your business goals. This opens the Freedom UI Designer.

  5. Open the schema properties area. To do this, click in the action panel.

  6. Fill out the schema properties.

    Property

    Property value

    Property description

    Page title

    The localizable schema title

    Code required

    The schema name

    Starts with the prefix. Learn more: Manage configuration elements. Can contain Latin characters and digits.

    Package

    The custom package where you create the schema

    The property is populated automatically and non-editable.

    Description

    The localizable schema description

  7. Set up the Freedom UI page using tools of Freedom UI Designer. Learn more: Element setup examples (user documentation).

  8. Customize the Freedom UI page using development tools (optional).

    1. Open the Module Designer. To do this, click Save.

    2. If needed, change the schema properties. To do this, use in the properties area.

      Property

      Property value

      Property description

      Code required

      The schema name

      Matches the Code properties specified in the Freedom UI Designer.

      Title required

      The localizable schema title

      Matches the Page title property specified in the Freedom UI Designer.

      Parent object

      The object whose properties the module inherits

      Creatio populates the property automatically based on the template selected when adding the Freedom UI page in the Configuration section. We do not recommend editing the Parent object property after you add elements to the schema. This can cause page malfunction.

      Package

      The custom package where you create the schema

      Matches the Package property specified in the Freedom UI Designer. The property is populated automatically and non-editable.

      Description

      The localizable schema description

      Matches the Description property specified in the Freedom UI Designer.

    3. Apply the changes.

    4. Fill out the additional properties (optional). To do this, use in the properties area.

      View the additional properties in the figure below.

    5. Implement the functionality. The module name in the define() function must match the schema name in the Code property.

      Creatio displays the type of the error or warning – if any – to the left of the row number. Hover over the error type to view a tooltip with the error description.

      You can use TypeScript to customize Freedom UI pages.

  9. Save the changes.

    If you set up the page using only tools of Freedom UI Designer , save the changes in Freedom UI Designer.

    If you customize the page using development tools , save the changes in Module Designer.

View model schema

View model schema has the following types:

  • Page view model
  • Section view model
  • Detail (list) view model
  • Detail (fields) view model

General procedure to implement the view model schema:

  1. Open the Configuration section. Instructions: Open the Configuration section.

  2. Select a custom package to add the schema.

  3. Add a module schema. To do this, click Add on the section list toolbar → select the type of the view model schema. This opens the Module Designer.

  4. Fill out the schema properties.

    Property

    Property value

    Property description

    Code required

    The schema name

    Starts with the prefix. Learn more: Manage configuration elements. Can contain Latin characters and digits.

    Title required

    The localizable schema title

    The title of the configuration element schema is generated automatically and matches the value of the Code property without the prefix.

    Package

    The custom package where you create the schema

    The property is populated automatically and non-editable.

    Parent object

    The object whose properties the module inherits

    Select the parent object in the drop-down list.

    Description

    The localizable schema description

  5. Apply the changes.

    If needed, use in the properties area to change the schema properties.

  6. Fill out the additional properties (optional). To do this, use in the properties area.

    View the additional properties in the figure below.

  7. Implement the functionality. The module name in the define() function must match the schema name in the Code property. The view model schema inherits from the BaseModulePageV2 base schema.

    Creatio displays the type of the error or warning – if any – to the left of the row number. Hover over the error type to view a tooltip with the error description.

  8. Save the changes.

Implement a replacing module

The Replacing view model schema type represents the replacing module. Learn more: Replace configuration elements.

General procedure to implement a replacing module:

  1. Open the Configuration section. Instructions: Open the Configuration section.

  2. Select a custom package to add the schema.

  3. Add a replacing module schema. To do this, click AddReplacing view model on the section list toolbar. This opens the Module Designer.

  4. Select the parent object.

    To replace a section or page with the module, specify the view model schema to replace in the drop-down list of the Parent object required property. For example, to create a replacing schema for the Contacts section, specify the ContactSectionV2 schema as the parent object. After you select the parent object, Creatio populates other module properties automatically.

  5. Apply the changes.

    If needed, use in the properties area to change the schema properties.

  6. Fill out the additional properties (optional). To do this, use in the properties area.

    View the additional properties in the figure below.

  7. Implement the functionality. The module name in the define() function must match the schema name in the Code property.

    Creatio displays the type of the error or warning – if any – to the left of the row number. Hover over the error type to view a tooltip with the error description.

  8. Save the changes.

Use hot keys

To display the index of available hot keys:

  1. Open the Module Designer.
  2. Click on the toolbar.

Hot key

Action

Ctrl+A

Select all

Ctrl+Z

Undo

Shift+Ctrl+Z

Redo

Ctrl+F

Find

F3

Find next

Shift+F3

Find previous

Shift+Ctrl+F

Replace

Shift+Ctrl+R

Replace all

Ctrl+Y

Delete line

Alt+Left

Go to line start

Alt+Right

Go to line end

Alt+G

Jump to line

F11

Fullscreen code editor

Esc

Exit fullscreen mode

Ctrl+Space

Call autocomplete

Ctrl+S

Save the changes.


See also

Module types

Creatio IDE

Operations in Creatio IDE

Replace configuration elements


Resources

Front-end development

Element setup examples (user documentation)


E-learning courses

Development on Creatio platform