You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 30 Next »

Want this feature?

Deploy Content is a CV multisite feature. It can also be used with Content Lock. Implementation requires consultation with Commerce Vision and all sites must be on the same version (min. 2022.3).

CV: 105298

Overview

The Deploy Content feature allows the CMS Administrator and Content Administrator roles to 'copy over' content from one CV website to destination CV websites in their organisation's network. The CMS Administrator can enable/disable the feature for specific content types as needed. For a destination site to be selectable, it must be on the same version as the deploying site. 

What can be deployed?

  • Lockable content objects in locked status (available only for objects that can be used with Content Lock)
    • Pages and templates
    • Layouts
    • Articles, Article Types 
    • Banners / Banner Types
    • Widgets
    • Campaigns
  • Unlocked object status
  • Non-locking content objects


For more on locking, see: Content Lock.


TypeWhat is deployable?Conditions
Pages & Templates
  • whole page or specific objects in existing pages
  • whole page or specific objects in new pages
  • whole page or specific objects in draft pages (if Page Preview on)

Note - when a whole page is deployed, any deleted objects will also be deleted on destination sites. 

  • saved
  • locked 
Widgets
  • changes to existing widgets
  • new widgets added to a zone
  • draft widgets (if Page Preview on) 
  • saved
  • locked
Zones
  • all content and objects in a zone
  • locked
Layouts
  • changes to existing layouts including custom layouts   
  • saved
  • locked
Campaigns
  • new campaigns
  • updates to existing campaigns
  • saved
  • locked
Banner Types
  • changes to existing banner types
  • new banner types
  • locked
Article Types
  • changes to existing article types
  • new articles types
  • saved
  • locked
  • SEO information for both sites the same
Articles
  • changes to existing articles
  • new articles
  • saved
  • locked
Section Menus
  • changes to section menu items
  • new section menus
  • non-lockable
Roles
  • changes to role settings
  • new roles
  • non-lockable
  • saved
Menus
  • changes to menu settings and items
  • new menus
  • non-lockable
  • by Role
  • saved
Category
  • online-maintained details and settings only
    • changes to existing category information
    • new and existing sub-categories (only if top category exists on destination site)
    • category structure (only if top category exists on destination site)
    • category products (only if top category exists on destination site)
  • non-lockable
Product Details
  • Online-maintained product details
  • non-lockable
Product Features
  • Any new or existing features
  • non-lockable



What Can Be Deployed?

When Deploy Content is available for a page or content object, a Deploy button displays on the top right of the page and/or Deploy on the object's Options menu. In general, the top Deploy button allows multiple data types and items to be selected for a deployment instance. Deploy from an object's menu is usually limited to deployment of that object or item.


Example: deploying in Category Maintenance

   

Clicking the Deploy button (1) allows you to select more than one category for a deployment instance.

Clicking Deploy from a category's Options menu (2), e.g., 'Sports & Outdoors' will only allow deployment of that category's deployable data.  


On this page:

Deploy Rules

Deploy rules are there to maintain content integrity on linked sites. 

  1. Deployment is cancelled if edited object is not found.
  2. Deployment will fail if an object is in draft mode (if Page Preview is on).


The Deployment Process

No matter the content data type, the deployment process is completed through the Deploy modal. This popup opens when you click the Deploy button or the Deploy menu item. The process has four steps:



1 - Select the data type(s) and/or item(s) to deploy.
Step-by-step

1. Toggle ON each data type you want to deploy.

2. Toggle ON each item to deploy. (Not all content types have the item level.)

3. Click Next.


2 - Select destination site(s).

Step-by-step


1. Toggle ON one or more destination site(s) to deploy to.

2. Click Next.


3 - Check selected data and destination site(s) are correct.

Step-by-step

1. Review the data and destination site summary.

2. To proceed with deploytment, click Deploy

4 - Check deployment results.

Step-by-step

When deployment is successful, all four steps are completed.



Successful: Click the link to go to the Deployment Log. TIP: Even though the deployment instance is successful, the system may have detected other issues.

:

When deployment fails, step 4 is not completed.


(1)

(2)

(3)

(4)

(5)

1. Go to ContentAdvanced ContentContent Deployment Log.

2. Find the deployment instance. 

3. Click Edit for the failed deployment instance.

4. Scroll down, then click More Information

4. View error messages for the deployment.

                     

Deploy Rules and Result Messages


Result Messages

Successful

  • single linked site - all changes to selected data type(s) and items have been deployed on the destination site.
  • multiple linked sites - all changes to selected data type(s) and items have been deployed on all destination sites.

Failed

  • single linked site - at least one change to selected data type(s) and items cannot be deployed and the whole deployment instance was cancelled. Nothing was deployed to the selected linked site.
  • multiple linked sites - at least one change to selected data type(s) and items cannot be deployed on all sites and all deployment instances were cancelled. Nothing was deployed to all selected linked sites.

Partially successful 

  • multiple linked sites - all changes to data types of selected data type(s) and items were successfully deployed to at least one site but also failed for at least one site.   


Administrator Functions

Enable/disable Deploy Content

  1. In the CMS, go to Settings SettingsContent Deploy Content.
  2. Click Configure.

  3. Toggle ON/OFF Destination Sites.
  4. When enabled, Deploy buttons or links will display for deployable objects. (NOTE - For Role and menu deployment, see: Deploy Role and menus.) 

    Deploy disabled                                                                   Deploy enabled
     
  5. The Content Deployment Log will also be available on the Advanced Content menu. See: View Deployment Log.

Add linked sites

Sites that share an organisation Id are treated as in a network. You may not always want to deploy a set of changes to all available sites. What sites a deployment instance can select from is set in Feature Settings.


To add sites that content can be deployed to:

  1. Go to Settings SettingsContent Linked Sites.

  2. Click Configure.

  3. Scroll down to the Sites section.

  4. Toggle on one or more sites from the available sites.

  5. Click Save.


Deploying lockable objects

The contents of a lockable object must be in locked status to be deployable. if unlocked, only the unlock status is deployed. This is used to allow users on linked sites to edit content. You'll know when an object is deployable by the displayed Deploy button or link under Options. If your site uses Page Preview and an object is deployed before Publishing, it will be deployed in the Draft mode.

  1. Go to the locked object. 

  2. Locate the Deploy button and click it.


  3. In the Deploy modal, select individual objects to deploy or toggle Select All.


  4. Click the Next button.

  5. Select one or more available deployment sites.


  6. Click Next.

  7. Check the summary of items to be deployed.
  8. To confirm deployment, click Deploy.

  9. Check the deployment results. NOTE - The result for each individual site is displayed separately. 


  10. You can check the deployment details for more information. On the Results modal, click the link.


  11. Check the deployment details. You can enter notes about the deployment. 

  


Deploying non-lockable objects

Non-lockable objects need additional setting to be enabled for deployment.


To deploy a non-lockable object:

  1. In the CMS, go to  Settings SettingsContent Linked Sites.

  2. Click Configure.

  3. In Linked Sites Feature Settings, toggle ON the feature type(s) you want to deploy.  


  4. Click Save.


Deploying Role Settings

Role settings changes are deployed from the Deployment section of the Linked Site Feature Settings page.


To deploy Role changes:

  1. In the CMS, go to  Settings SettingsContent Linked Sites.

  2. Click Configure.

  3. In Linked Sites Feature Settings, toggle ON Enable Role Deployment.  
  4. Click the Deploy button displayed.
     
  5. In the Deploy modal, select one or more Roles to deploy.

  6. Click Next

  7. Select the linked sites for deployment. 


Viewing Deployment History & Results

To check deployment results:

  1. In the CMS, go to ContentAdvanced ContentContent Deployment Log.


  2. Use the Search tool to find the deployment instance. 


  3. Click Edit for the deployment instance you want to view.


Additional Information


Minimum Version Requirements


4.38

Prerequisites


Implementation by Commerce Vision

Self Configurable


No

Business Function


Content

BPD Only?


Yes

B2B/B2C/Both


Both

Third Party Costs


n/a

Related help



  • No labels