Skip to main content


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

General information

Updated on March 2, 2023

Use the General Information tab to define the name, description, and learning objectives of the module.

Title

Module titles should reflect the content — they should be either role-based, product-based, task-based, or conceptual.

Important: Module titles are limited to a maximum of 70 characters.

Use the following best practices when naming a module:

GuardrailsUse ThisAvoid This
If the topic content is product-based, follow the product naming conventionIntegration Designer

Integration Designers for beginners

Advanced Integration Designer

If the topic content is task-based, follow the task naming convention ("-ing" verb)Troubleshooting decision management componentsHow to troubleshoot decision management components
If the topic content is conceptual, follow the concept naming convention (noun)Case management

Introduction to case management

Case Management overview

For more information, see the article Naming your Pega Academy content.

Description

In the Description field, enter a short description that describes the purpose of the module. For example:

This module introduces you to the core concepts of Pega's Center-out Business Architecture. Employees and customers have a very different relationship with technology today. No longer passive consumers, they actively participate in shaping the tech experience and demand that it adapts in real-time with them. You need agility to react and change this quickly, across all channels and systems. And you need to maintain the ability to scale enterprise-wide.

Attention: Do not include learning objectives in the description. Learning objectives are listed separately in the Learning objectives section.
Note: As a best practice for UX, do not include a Note tag or similar at the beginning of a description. The first 144 characters of the description are displayed on the content card in search results to provide users with a quick preview of the content.

Duration

The Duration field is automatically calculated based on the total duration of all the topics and the module quiz.

Learning objectives

Use learning objectives to communicate specifically what students should be able to do after completing the module. Learning objectives can be based on knowledge, skills, and attitudes. Learning objectives define learning outcomes, and help to clarify, organize, and prioritize learning. Learning objectives are measurable and quantifiable.

Note: For help with action verbs and learning objectives, see: Bloom's Taxonomy in the Content Contributor Getting Started packet.

To add learning objectives:

  1. In the first Learning objective field, enter the learning objective. For example, Configure Pega Call to use a Computer Telephony Integration (CTI) or Map CTI properties to Pega Call properties.
    Note: Include closing punctuation at the end of the objective even if the list items are a mixture of fragments and complete sentences. For more information, see Lists in Pega Academy.
  2. Click Add another item to add additional learning objectives.
Note: There should be as many outcomes as needed to clearly reflect what students will learn from the module. Typically a module will contain 1-3 learning objectives.

Close with a period as the objectives are technically clauses. Include regardless of content (whether the objectives are sentence fragments or full clauses).

Training library

Add terms from Training Library to indicate if the module is a specific type of training. For example, Sales training, Corporate training, or UAP training.

Note: Training Library terms are used on Pega Academy as a filter.

To add a term from the Training Library:

  1. Click Add term from Training Library
  2. Select one of the training categories.
    "Training Type"

Member-type access

Use Member-type access to determine who can view the module.

Note: Leaving the Member-type access check boxes clear behaves the same as if you checked all options and provides access to all.

Select one or more member-types.

Attention: A mission can only contain modules whose member-type access settings are equal to or less restrictive than the member-type access settings of the mission. For example, if the member-type access setting in the module is Pega only, the module can only be included in a mission whose member-type access setting is Pega. If the member-type access setting in the mission is All, you cannot include the Pega-only module in the mission.

For more information about member-type access settings, see the article Member-type access settings.

Organization access

The Organization Accessfield automatically populates to restrict viewing access of unpublished content to only members of your organization; the content is searchable from the Master Content list but is unable to be opened and edited.

Select the Bypass Organization Access to Allow members of other organizations check box to allow members outside your organization to edit the unpublished content.

Organization access field and bypass organization access check box
Note: Member-access settings override the organization bypass functionality. For example, if content is set to Pega-only, using the Bypass Organization check box does not work to allow Partner view or edit access.

Related Challenges

Associate up to 3 challenges that relate to the module content and learning objectives.  Begin typing the title of the challenge and autocomplete provides possible matches to select. 

Adding related challenges to module landing page

When added, associated challenges appear on the module landing page as clickable links.

Challenges appear on module landing page

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