Use the General information tab to define the name and description of the mission.
Mission titles should reflect your content. The titles should be either role-based, product-based, or competency-based.
Use the following best practices when naming your mission:
|Guardrails||Use This||Avoid This|
|Use headline case when naming missions|
Customer Decision Hub
Introduction to customer decision hub
|If the mission is capability-based, use a title that describes the capability using proper nouns|
Low-Code App Builder
Cross-Sell on the Web
Building low-code applications with Pega Platform
Cross-sell on the web
|If the mission is role-based, use a title that reflects the role using proper nouns|
Customer Service Developer
System Architect Essentials
Basics of Customer Service development
|If the mission is product-based, use a title that reflects the product name|
Pega Robot Manager
Customer Decision Hub
Introduction to Pega Robot Manager
Getting started with Customer Decision Hub
|Level labels (Foundation, Intermediate, and Advanced) are also capitalized|
Case Management Intermediate
Pega Customer Service Foundation
Case Management intermediate
Pega Email Bot foundation
|Do not include introductory labels such as About, Introduction to, Overview of, How to||Customer Decision Hub||Introduction to Customer Decision Hub|
|Do not add a year or version number in the mission title|
User Interface Foundation
Pega Platform Release Update
Introduction to Pega Sales 2019
Pega Platform 8.5 Release Update
|Do not include an audience label|
Pega Express Delivery
System Architect for Beginners
Pega Express Delivery for Product Teams
For more information about naming missions, see the article Naming your Pega Academy content.
In the Description field, enter a short description (2-3 lines) that describes the purpose of the mission. For example:
Begin your journey as a business architect with Pega technology by learning the capabilities of App Studio to develop applications on Pega Platform. Apply Design Thinking and the Pega Express methodology to define the right scope and yield faster business results. Influence the design of applications to support building for change, gain better business insight, and achieve greater user adoption.
Add terms from the Training Library to indicate if the mission is a specific type of training. For example, Sales training, Corporate training, or UAP training.
To add a term from the Training Library:
- Click Add term from Training Library
- Select one of the training categories.
Use Member-type access to determine who can view the mission.
Select one or more roles to restrict mission visibility.
For more information about member-type access settings, see the article Member-type access settings.
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.
Badge IDs are automatically associated to a mission.