Object types supported by continuous integration

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

Countries

cms.country

Supported child objects:

• States (cms.state)

Custom tables

cms.customtable
_______________________________

Includes the definitions and settings of custom tables. The data records stored within the tables are represented by a separate object type for each table, named in format customtableitem.<table code name>.

Note: If you change the code name of a custom table with existing data records, the system attempts to re-serialize all data under the new object type. If any problems occur, you may need to manually serialize all objects in the Continuous integration application to bring your CIRepository folder into the correct state.

Supported child objects:

• Alternative forms (cms.alternativeform)
• Queries (cms.query)
• Permissions (cms.classpermission)

Represents the data records stored within custom tables. Each custom table has a separate object type for its data, named in format customtableitem.<table code name>. For example: customtableitem.customtable.sampletable

Note: The continuous integration solution does not track the data of custom tables without an ItemGUID field. The GUID values are used to identify custom table records and in the names of the corresponding XML files. You can add a GUID field and generate identifier values for all records by clicking Create GUID on the Fields tab of the custom table's editing interface.

Supported child objects:

• Facebook pages (sm.facebookaccount)

Child object type of Facebook app objects.

The continuous integration data does not include individual Facebook posts or the statistical data (Insights) measured for Facebook pages.

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.

Form controls

Supported child objects:

• LinkedIn company profiles (sm.linkedinaccount)

Child object type of LinkedIn app objects.

The continuous integration data does not include individual company updates (posts) or the statistical data measured for LinkedIn company profiles.

Supported child objects:

• Media library files (media.file)

Child object type of Media library objects.

Only includes media file definitions, not the binary data of individual media files. Binary data is stored in the location configured for the media library.

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

Supported child objects:

• Module permissions (cms.permission)
• Libraries (DLLs) registered for custom modules (cms.resourcelibrary)
• UI elements (cms.uielement)

Includes the definitions and settings of module classes (object types).

If you wish to use continuous integration for the data stored by custom module classes, you need to enable continuous integration in the corresponding type information code. See: Enabling continuous integration for custom classes

Supported child objects:

• Alternative forms (cms.alternativeform)
• Queries (cms.query)

Module classes that have the Can be customized property enabled are represented by the separate cms.systemtable object type.

Supported child objects:

• Alternative forms (cms.alternativeform)
• Queries (cms.query)

cms.pagetemplate

Represents custom page templates created for MVC pages.

cms.documenttype

Supported child objects:

• Alternative forms (cms.alternativeform)
• Transformations (cms.transformation)
• Queries (cms.query)
• Permissions (cms.classpermission)

Child object type of Report objects. Report subscriptions are always site-related objects.

Supported child objects:

• Report graphs (reporting.reportgraph)
• Report subscriptions (reporting.reportsubscription)
• Report tables (reporting.reporttable)
• Report values (reporting.reportvalue)
• Reports - Saved views (reporting.savedreport)

Reports - Saved views

reporting.savedreport

Child object type of Report objects.

Supported child objects:

• Reports - Saved graph images (reporting.savedgraph)

Includes the basic definitions of resource strings that are stored in the database. For strings stored within resx files, use your source control system to synchronize the files directly.

The text values (translations) of individual strings are stored separately under the cms.resourcetranslation binding object type.

Does not include System tasks (dynamically created temporary tasks that the system uses internally).

When restoring data from the CIRepository folder, you can configure the restore utility to automatically log rebuild tasks for any new or modified search indexes. The index rebuilds are processed when the application starts up after the restore operation.

See Restoring continuous integration files to the database for more information.

The continuous integration data does not include the status of sites (running, stopped, etc.). When restoring data from the CIRepository folder, any new sites are stopped by default and need to be started manually in the Sites application.

Supported child objects:

• Site domain aliases (cms.sitedomainalias)

Supported child objects:

• Twitter channels (sm.twitteraccount)

Child object type of Twitter app objects.

The continuous integration data does not include individual Tweets or the statistical data (Analytics) measured for Twitter channels.

Child object type of Module objects.

Supported child objects:

• Help topics (cms.helptopic)

Users in Xperience are a composite object type. The basic properties are stored within cms.user objects, with additional settings within child cms.usersettings objects. See the Users section in Continuous integration repository structure for more information.

Supported child objects:

• Macro identities assigned to users (cms.usermacroidentity)
• User personal categories (cms.usercategory)
• Widget dashboard content (cms.dashboard)

Web parts

cms.webpart

Supported child objects:

• Web part layouts (cms.webpartlayout)

Widget categories

Widgets______

Includes the definitions of workflows. Continuous integration does not track the workflow status of pages. Pages under workflow are fully stored in the repository only after they are published.

Supported child objects:

• Workflow scopes (cms.workflowscope)
• Workflow steps (cms.workflowstep)

Child object type of Workflow objects.

Note: Unlike other workflow objects, scopes are always related to a specific site and are stored in the corresponding subfolder in CIRepository.

Child object type of Workflow objects.

Includes steps defined for both basic and advanced workflows.

cms.aclitem

Child object type of Page objects.

Supported child objects:

• Attachment image variants (cms.attachmentvariant)

Page-level permissions (ACLs)

cms.acl

Supported child objects:

• ACL items (cms.aclitem)

Pages

cms.document

When using the page workflow feature, the majority of workflow information is ignored. For more details, see Usage and relationship with other features.

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

Supported child objects:

• Attachment image variants (cms.attachmentvariant)
• Attachments (cms.attachment)
• Page alternative URLs (cms.alternativeurl)
• Page former URL paths (cms.pageformerurlpath)
• Page URL paths (cms.pageurlpath)

Page tags and tag groups

Includes the personal page categories created by individual users.

Child object type of User objects.

The continuous integration data does not include the start/end dates and status of A/B tests (not started, running, finished, etc.). When restoring data from the CIRepository folder, any new A/B tests are always created with the Not started status.

Information about A/B testing variants is stored within the data of individual tested pages.

Activity types

Automation actions

ma.automationaction

Only includes the general definitions of marketing automation processes. Process states for individual contacts are dynamic live site data and are not tracked by continuous integration.

Supported child objects:

• Automation process steps (ma.automationstep)
• Automation process triggers (cms.objectworkflowtrigger)

Child object type of Automation process objects.

Note: When restoring data from the CIRepository folder, process triggers of the "Contact scored X or more" type are created only if the related score exists in the given database. To reliably use continuous integration for these types of triggers, you need to manually ensure that the required scores are present on all instances in the environment (Scores are currently not supported by continuous integration).

The continuous integration data does not include the status of campaigns (draft, running, etc.). When restoring data from the CIRepository folder, any new campaigns are always created with the Draft status.

Supported child objects:

• Campaign assets (analytics.campaignasset)
• Campaign conversions (analytics.campaignconversion)

Child object type of Campaign objects. Represents pages or promotional emails assigned to a campaign's content inventory.

Supported child objects:

• Campaign asset URLs (analytics.campaignasseturl)

Child object type of Campaign objects.

The continuous integration data of campaign conversions does not include live site statistics (the number of logged conversion hits).

Only includes the definitions of contact groups, without information about the contacts or accounts assigned to the groups.

Additionally, the continuous integration data does not contain information about scheduled rebuilds for contact groups. After restoring a new condition-based contact group from the CIRepository folder, you need to manually rebuild the group in the Contact groups application.

Includes the definitions and configuration of both newsletters and email campaigns.

Supported child objects:

• Emails (newsletter.issue)

The continuous integration data does not include the send status of marketing emails or any live marketing data (the number of opened emails, clicked links, unsubscriptions, etc.). When restoring data from the CIRepository folder, any new emails are always created with the Draft status.

Supported child objects:

• Email A/B tests (newsletter.abtest)
• Email variants for A/B tests (newsletter.issuevariant)

Child object type of Email campaign email objects.

The continuous integration data of marketing email A/B tests does not include any data collected or specified after the emails are sent out (such as the selection of the test winner).

Child object type of Email campaign email objects.

The continuous integration data does not include the send status of marketing email variants or any live marketing data (the number of opened emails, clicked links, etc.).

personas.persona

If you want to use continuous integration for personas that use custom activities in their rule definitions, you need to make sure each custom activity has its Activity item object type configured in Contact management -> Configuration -> Activity types -> Edit -> Scoring rule configuration section.

The continuous integration data for personas also includes data for persona scores and rules, represented by the om.personascore and om.personarule CI folders.

Supported child objects:

• Buy X Get Y and Product coupon codes (ecommerce.multibuycouponcode)

Child object type of Buy X Get Y discount or Product coupon objects.

The continuous integration data of individual coupon codes does not include the current number of redemptions (coupon code uses). New coupon codes restored from the CIRepository folder are always unused.

Carriers

Discounts:

• Catalog discounts
• Order discounts
• Free shipping offers

Includes Catalog discounts, Order discounts and Free shipping offers. Volume discounts and Buy X Get Y discounts are stored as separate objects.

Supported child objects:

• Discount coupon codes (ecommerce.couponcode)

Child object type of Discount objects (Order discounts or Free shipping offers).

The continuous integration data of individual coupon codes does not include the current number of redemptions (coupon code uses). New coupon codes restored from the CIRepository folder are always unused.

Supported child objects:

• Gift card coupon codes (ecommerce.giftcardcouponcode)

Child object type of Gift card objects.

The continuous integration data of individual coupon codes does not include the current number of redemptions (coupon code uses). New coupon codes restored from the CIRepository folder are always unused.

Supported child objects:

• Buy X Get Y and Product coupon codes (ecommerce.multibuycouponcode)

Product option categories

ecommerce.optioncategory

Supported child objects:

• Product options (ecommerce.skuoption)

Products

ecommerce.sku

Supported child objects:

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

Shipping options

ecommerce.shippingoption

Supported child objects:

• Shipping costs (ecommerce.shippingcost)

Suppliers

Tax classes
__________________________

Buy X Get Y discount
- OR -
Product coupon

Buy X Get Y discount
- OR -
Product coupon

Workflow step (source)
- OR -
Automation process step (source)

Workflow step (target)
Workflow
- OR -
Automation process step (target)
Automation process

Buy X Get Y discount
- OR -
Product coupon

Role permissions assigned to media libraries

Role
Permission

Workflow step
- OR -
Automation process step

Page type
Custom table

Workflow step
- OR -
Automation process step