Skip to main content

Creating landing pages

4 タスク

30 分

表示の対象:All users Applies to: Pega Platform '25
上級
英語

シナリオ

MDC offers three membership types: Bronze, Silver, and Gold. The registration cost varies depending on the membership type. Registration requests are routed to the executive manager for approval.

The executive manager can update the membership type and pricing models.

The following table provides the credentials you need to complete the challenge:

Role User name Password
Admin admin@deliveryservice rules
Executive Manager executivemanager@mdc rules

このチャレンジを完了するには、Pegaインスタンスを起動する必要があります。

起動には5分ほどかかることがありますので、しばらくお待ちください。

詳細なタスク

1 Identify design options

There are two options to implement the given requirement:

  • Option 1: Add a landing page on the Executive Manager Portal to add or update the membership types and pricing model.
  • Option 2: Delegate the Data Object to the Executive Manager role to add or update the membership types and pricing model.

2 Evaluate design options

The following table outlines the pros and cons of two design options for implementing the given requirement:

Design Pros Cons
Landing page
  • User interaction and navigation.
  • Access controlled by roles and permissions.
  • Configured by using low-code tools.
  • Integration with Pega GenAI Coach™ for list-based pages to assist users.
  • AI Designer landing page available for managing GenAI Connect Rules
  • Supports ready-to-use custom pages (Home, Teams, Explore Data).
  • Supports list-based pages only.
  • Performance considerations for large Data Sets (pagination recommended).
Delegate a Data object
  • Empowers business users to manage data.
  • Supports business Rules, decision tables, and data tables.
  • Delegation is controlled by developers.
  • No default way to display the Data Object in the user Portal.

3 Recommend the best design option

Adding a landing page to the Executive Manager Portal is the recommended approach because it is easy to configure and does not require customization.

Guidelines for using Landing Pages and alternative approaches

Landing pages are ideal when:

  • You must provide role-based access to data management functionality.
  • Users require intuitive, low-code interfaces for data maintenance.
  • You want to use default templates and minimize custom development.
  • The data can be displayed in a tabular or tile format effectively.

Consider alternatives when:

  • Complex data relationships require custom UI logic.
  • You need highly specialized data entry workflows.
  • The data structure does not align with a list-based presentation.
  • Integration with external systems requires custom API development.

4 Implement solution details

  1. In the Pega Platform instance for the challenge, enter the following credentials:
    1. In the User name field, enter admin@deliveryservice.
    2. In the Password field, enter rules.
  2. In the header of Dev Studio, click Application: Delivery Service > Definition.
  3. On the Cases & data tab, in the Data section, search for Membership Type, and then click Add.
  4. Click Save.
  5. In the header of Dev Studio, click Dev Studio > App Studio.
  6. In the navigation pane of App Studio, click Data and then click Membership Type.
  7. On the Data Model tab of the Membership Type Data Object, click Primary fields.
    1. In the Primary field configuration dialog box, click Add, and then select the existing fields that you want to make primary.
    2. Click Add, and then click Submit. 
Configure primary fields to data object
  1. Click Save
  2. On the Data Pages tab of the Membership Type Data Object, click Savable Membership Type, and then click Open in Dev Studio.
Data Pages tab of Data object
  1. In Dev Studio, set the availability of the D_MembershipTypeSavable Data Page to Available, API
Rule availability status
  1. Log out and log back in by using the credentials provided in Step 1.
  2. In App Studio, in the navigation pane, click Data, and then click Membership Type:
    1. On the Settings tab, click Default data sources.
    2. In the Default record lookup data page list, select Savable Membership Type.
    3. Click Save
Default data sources tab.
  1. In the navigation pane of App Studio, click Channels.
  2. In the Current channel interfaces section, click Executive Manager Portal.
  3. On the Portal page, on the Content tab, click Landing pages.
  4. In the Landing pages pane, click Add, and then configure the page:
    1. In the Name field, enter Membership Type.
    2. In the Template list, select Default page.
    3. Click Submit.
The configuration to add a landing page to a Portal.
  1. In the Edit landing page area, in the Region A section, click Add.
Configure to add a view to landing page portal.
  1. In the Views field, select Membership Type, and then click Add.
Configure to add a Membership Type view.
  1. In the Edit landing page area, in the Region A section, click Membership Type.
  2. In the Edit view area, in the Data page list, select List Membership Type.
  3. In the Columns section, click Add, and then enter Primary fields.
  4. Select the Primary fields checkbox, and then click Add.
Edit view landing page.
  1. In the Editing section, allow user edits by selecting the Allow edit, delete and create checkbox to enable the create, read, update, and delete (CRUD) operations of records of the Data Object from landing pages.
The Allow edit, delete and create checkbox.
  1. In the Landing pages pane, click the back arrow to return to the Main navigation section.
  2. In the Landing pages section, click Add item to add the newly created Membership Type landing page to the Executive Manager Portal, and then save the configuration details.
Main navigation.
  1. Click Save


このモジュールは、下記のミッションにも含まれています。

トレーニングを実施中に問題が発生した場合は、Pega Academy Support FAQsをご確認ください。

このコンテンツは役に立ちましたか?

改善できるところはありますか?

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

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice