Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Using revision, release, or clone

Updated on November 22, 2021

Review the following use cases and recommended actions to take when making changes to your content in Pega Academy.

Note: If your content is not changing, and you want to reuse it as-is in a new mission or module, see Release versus Revision
I want to...ActionResult
  • Modify existing content to fix typos or grammatical errors in text or images
  • Edit text or swap media (images, videos, interactions) that do not change scope*
Revision
  • Modifies existing new content
  • Does not create new content
  • Does not create new content ID
  • Does not modify existing content ID
  • Reuse content and retain the link to user progress in the previous rendition. (Optionally, determine if students need to consume the content to remain current)
  • Make updates to content but do not want to change the title
  • Update the learning objectives, which have significantly changed
  • Update the scope* of the content (mission/module) by adding/removing content pieces, which impacts user progress
  • Edit text or swap media (images, videos, interactions) that change scope*
Release
  • Links to the original content and user progress
  • Maintains and appends the existing content ID
  • The body of content is modifiable
  • Title change (if applicable) impacts all releases
  • Copy existing topics or challenges that only need to address a product or feature name change
  • Create a new topic or challenge, but I do not want to start from the beginning.
Clone
  • Creates a new copy of the content
  • Net new content ID is created
  • No linkage to the original content is copied
  • No previous user progress is associated with this new copy
  • The title is modifiable without impacting the original content
    • Example: Feature name changed from one product version to another: Data Types to Data Objects; both are valid for the version they support.

Revision - A revision is a change that corrects or improves an existing topic, module, mission, challenge, or certification exam page.

Release - A release contains new or updated information (for example, user interface changes from product version 8.5 to 8.6) but retains the content title and connection to previous iterations.

*Scope - If you answer yes to any of the following questions, then your scope has changed:

  • Have the learning objectives changed?
  • Has the content structure changed?
  • Has the overall mission duration changed?
"When to use clone, release, or revision"

Release versus Revision

Scenario: A content author has an existing piece of content that is intended for use or reuse for one of the following reasons:

  • A new product version has come out and the mission (or content within the mission) needs to be updated
  • Content is still part of an existing product version but requires adding the new product version tag
  • Scope* of content has changed significantly 
Release versus Revision

*Scope - If you answer yes to any of the following questions, then your scope has changed:

  • Have the learning objectives changed?
  • Has the content structure changed?
  • Has the overall mission duration changed?

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us