Object types supported by continuous integration

Continuous integration supports the following types of Kentico objects:

General

Object type

CI folder name

Notes

Alternative forms

cms.alternativeform

Child object type with the following possible parent types: Custom tables, Forms, Page types

Countries

cms.country

Supported child objects:

  • States (cms.state)

CSS stylesheets

cms.cssstylesheet

Custom tables

cms.customtable

Only includes the definitions and settings of custom tables, not the data records stored within the tables.

Supported child objects:

Email templates

cms.emailtemplate

Forms

cms.form
cms.formclass

Only includes form definitions and settings, not the data records stored by individual forms.

The system uses multiple object types to store the definitions and settings of forms. See the Forms section in Continuous integration repository structure for more information.

Supported child objects:

Form controls

cms.formusercontrol

Meta files

cms.metafile

Includes files related to other objects. For example thumbnail images of page types or email template attachments.

Page layouts (shared)

cms.layout

Page template categories

cms.pagetemplatecategory

Page template scopes

cms.pagetemplatescope

Child object type of Page template objects.

Page templates

cms.pagetemplate

Supported child objects:

Page type scopes

cms.documenttypescope

Page types

cms.documenttype

Supported child objects:

Queries

cms.query

Child object type with the following possible parent types: Custom tablesPage types

Roles

cms.role

Settings

cms.settingskey

Settings are supported by continuous integration, but excluded by default in the repository.config file. Settings may contain sensitive data – only remove the exclusion if you agree to make all setting values available within the file system used by your application and any connected source control systems.

States

cms.state

Child object type of Country objects.

Transformations

cms.transformation

Child object type with the following possible parent types: Custom tablesPage types

Web part categories

cms.webpartcategory

Web part containers

cms.webpartcontainer

Web part layouts

cms.webpartlayout

Child object type of Web part objects.

Web parts

cms.webpart

Supported child objects:

Widget categories

cms.widgetcategory

Widgets

cms.widget

Unsupported development objects

The following object types commonly used during development are currently NOT supported by continuous integration:

  • Custom modules - to synchronize module database objects across your development environment, use the export and import feature. To leave the modules open for editing after import, disable the Seal the selected modules option when selecting modules in the export wizard.
  • Resource strings - create and edit resource strings within resx files in the Kentico project. Use your source control system to synchronize the files between developers.

Page content

Object type

CI folder name

Notes

ACL items

cms.aclitem

Child object type of Page-level permission (ACL) objects.

Attachments

cms.attachment

Child object type of Page objects.

Categories

cms.category

Only includes global and site categories. User categories are not supported.

Page-level permissions (ACLs)

cms.acl

Supported child objects:

  • ACL items (cms.aclitem)

Pages

cms.document

Only supported when not using workflow, as continuous integration is designed for use during the project’s development phase.

The system uses multiple files to store page data. See the Pages section in Continuous integration repository structure for more information.

Supported child objects:

Page relationship types

cms.relationshipname

Page tags and tag groups

cms.taggroup

Tag groups are represented as a separate object type (cms.taggroup). Tags are stored within the data of individual Page (cms.document) objects.

Unsupported page permission scenario

Continuous integration does not support scenarios where different page-level permissions (ACLs) are applied to the same page from different sources and then synchronized.

Developer A

  1. Sets permissions for a user or a role on a page.
  2. Pushes the changes to the source control system.

Developer B

  1. Sets different permissions for the same user or role on the same page.
  2. Downloads the latest version from the source control. No collisions occur, because the ACL items are represented by different files.
  3. Restores objects from the file system to the database. Both ACL item files are processed, but only one is kept in the database, depending on the order in which they are processed.

On-line marketing

Object type

CI folder name

Notes

Activity types

om.activitytype

Automation actions

ma.automationaction

Email campaign templates

newsletter.emailtemplate

MVT combinations

om.mvtcombination

Child object type of Page template objects.

MVT variants

om.mvtvariant

Child object type of Page template objects.

Personalization variants

om.personalizationvariant

Child object type of Page template objects.

E-commerce

Object type

CI folder name

Notes

Carriers

ecommerce.carrier

Currencies

ecommerce.currency

Departments

ecommerce.department

Exchange tables

ecommerce.exchangetable

Manufacturers

ecommerce.manufacturer

Order statuses

ecommerce.orderstatus

Payment options

ecommerce.paymentoption

Product internal statuses

ecommerce.internalstatus

Product option categories

ecommerce.optioncategory

Supported child objects:

  • Product options (ecommerce.skuoption)

Product options

ecommerce.skuoption

Child object type of Product option category objects.

Product public statuses

ecommerce.publicstatus

Product files

ecommerce.skufile

Child object type of Product objects.

Product variants

ecommerce.skuvariant

Child object type of Product objects.

Products

ecommerce.sku

Supported child objects:

  • Product files (ecommerce.skufile)
  • Product variants (ecommerce.skuvariant )

Shipping costs

ecommerce.shippingcost

Child object type of Shipping option objects.

Shipping options

ecommerce.shippingoption

Supported child objects:

  • Shipping costs (ecommerce.shippingcost)

Suppliers

ecommerce.supplier

Tax classes

ecommerce.taxclass

Binding object types

In addition to the standard object types, continuous integration also supports most related bindings (i.e. objects representing relationships between the supported objects and other objects). For example, the binding objects that store how page templates or page types are assigned to sites.

Binding

CI folder name

Main object type (parent)

Related object type

Allowed child page types

cms.allowedchildclass

Page type

Page type

Applications assigned to the default dashboard of roles

cms.roleapplication

Role

UI element

Categories assigned to pages

cms.documentcategory

Page

Category

Countries of tax classes

ecommerce.taxclasscountry

Tax class

Country

States of tax classes

ecommerce.taxclassstate

Tax class

State

Device profile layouts of page templates

cms.templatedevicelayout

Page template

Device profile
Page layout (optional)

Exchange rates

ecommerce.exchangerate

Exchange table

Currency

Managers (users) of departments

ecommerce.userdepartment

User

Department

Mapped page layouts of device profiles

cms.deviceprofilelayout

Device profile

Page layout (source)
Page layout (target)

Page relationships

cms.relationship

Page

Page
Page relationship type

Pages with fields containing other pages
(see Advanced content modeling)

cms.adhocrelationship

Page

Page
Page relationship type

Payment options of shipping options

ecommerce.paymentshipping

Shipping option

Payment option

Permissions assigned to roles

cms.rolepermission

Role

Permission

Product bundles

ecommerce.bundle

Product

Product

Product options allowed for products

ecommerce.skuallowedoption

Product

Product option

Product options of product variants

ecommerce.variantoption

Product variant

Product option

Product option categories of products

ecommerce.skuoptioncategory

Product

Product option category

Roles assigned to forms

cms.formrole

Form

Role

Roles assigned to widgets

cms.widgetrole

Role

Widget
Permission

Roles in memberships

cms.membershiprole

Membership

Role

Scopes assigned to page types

cms.documenttypescopeclass

Page type scope

Page type

Sites of CSS stylesheets

cms.cssstylesheetsite

CSS stylesheet

Site

Sites of data classes

cms.classsite

Page type
Custom table

Site

Sites of page templates

cms.pagetemplatesite

Page template

Site

Sites of page relationship types

cms.relationshipnamesite

Page relationship type

Site

Sites of web part containers

cms.webpartcontainersite

Web part container

Site

Tax classes of departments

ecommerce.departmenttaxclass

Department

Tax class

Tax classes of products

ecommerce.skutaxclass

Product

Tax class

Tax classes of shipping options

ecommerce.shippingoptiontaxclass

Shipping option

Tax class

UI elements allowed for roles (UI personalization)

cms.roleuielement

Role

UI element

Users in roles

cms.userrole

Role

User