Skip to main content

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

Using the revision log

Updated on November 22, 2021

For each edit you make to a topic, module, challenge, or mission, provide a message about that change in the Revision log message box.

Revision log example

You can reuse content across the Pega Academy environment. As a best practice, let authors know what changed and why in the event that a change impacts content usage and meaning. The log message can be a high-level note about the changes.

For example, you make an update to an image in a challenge after a UI hotfix.

  • Fixed image in the section 2 task

Other examples include:

  • Fixed typo in Section 1
  • Fixed typo or configuration setting in H5P interaction
  • Modified/updated image 1
  • Q2: Selected the correct answer check boxes so that question can score properly
  • Step 2 of Task 4 is missing

To add a revision log message, enter your comment in the Revision log message box, and then click Save.

You can also enter text and log it in the Revision log message box when work is in-progress. Enter your message, and then click Save and continue editing.

To view the list of content revisions, on the content page, in the Pega Academy header, click Revisions. The revision log shows the revisions in chronological order along with the author ID of the user that made the change.

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us