Clone

• Cloning denotes the copy and creation of an all-new "node" of content without retaining its lineage to the content clone

• Clones can be viewed and created on the Release Select screen
• Clones can be published, unpublished, or archived independently of each other
• Clones create a new content ID (see below)
• Clones have no impact on user progress, badge currency, UI, URL, or other metrics
• Clones can be used to duplicate content, such as Topics or Challenges; you cannot use the cloning function to copy a mission or module container

When to use Clone

A clone is ideal when:

• You want to create new content but do not want to start from scratch
• The content is identical, but the title must be changed
• Content is product version-specific
• The URL does not need to stay the same

How to create a Clone

To create a clone:

1. From the Master content page, click a challenge or topic that you wish to clone
2. On the content page, under Operations select Clone from the drop-down list

3. In the text box, change the title of the cloned content 

4. Click Clone to create a new piece of content 

Producing net new content creates the initial, first release of the material. For example, behind the scenes this new topic is created with the content ID of: TOP123-1-EN.  Then, cloning existing content creates a new new ID.  For example, Cloned ID 2 has a separate content ID of TOP456-1-EN.

Examples

• You want to copy an existing topic or challenge that needs to address only a product or feature name change
• You want to create a new topic or challenge, but do not want to start from the beginning

Clone logistics per content type

Topics

• All cloned content is copied from the selected content

• Authors must update the title, content, and tags as necessary

Challenges

• All cloned content is copied from selected content

• Authors must update title, content, and tags as necessary

Modules

• Module containers cannot be cloned 

Missions

• Mission containers cannot be cloned

Impact of clone when content is shared

When content is shared across multiple missions in Pega Academy, creating a new clone of the content does not affect the content in all shared locations. Cloning does not propagate any changes to existing content.

For example, if you pull in a topic that is created for another mission, and the author of that mission creates a new copy of that topic, your topic is not impacted.  you share only the original content with the specific content ID.  The cloned content has a completely different ID.

Scenario:

A topic with a content ID, TOP123-1-EN is used in 5 separate missions throughout Pega Academy.  In this current state, the topic is about Data types.

However, in the next version of the product, the name has changed to Data objects.  Everything else is identical, only this term must change.  When the author clones this topic, a net new topic is created with a new content ID, TOP876-1-EN, and a new title, Data objects.

The author can now go into the new topic, Data objects, and change terms and images without impacting the original topic or starting from a blank page.  The original topic, in all its shared locations, with the content ID of TOP123-1-EN, is unaffected.