Skip to main content

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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Creating an External web component

Updated on April 5, 2022

You can add an external web component section to a layout, a region, another section, or a cell in a layout. At run time, this section allows you to connect to external applications and delegate access to OAuth 2.0-protected resources. For example, users can log on to Facebook from Pega Platform by using this section and access photographs in their Facebook account.

Do not add the External web component to repeating layouts because the system does not allow you to configure the section to perform different actions based on the data specific to each row. If you add this section to a repeating layout, all the sections inside the repeating layout use the same data at run time.

  1. On the Design tab, from the Data display list, drag External web component onto the work area.

  2. Click the View properties icon for the section to display the Cell Properties panel.

  3. Configure the section in the fields provided on the General , Presentation, and Parameters tabs.

  4. Click Submit to save your changes.

  • Harness and Section forms - Configuring an External web component section

    After adding an External web component section, you can configure the section with an OAuth 2.0 authentication profile, mashup section, and authorization section to connect to an external application at run time.

  • Authentication profiles

    Create an authentication profile to move messages securely to and from your application with a variety of connector and server rules.

  • OAuth 2.0 providers

    The OAuth 2.0 protocol provides your application with secure authentication in open networks with external applications, such as Facebook, and Google, over HTTPS. You define OAuth 2.0 provider data instances so that Pega Platform can access protected external resources by using access tokens.

  • Keystores

    A keystore is a file that contains keys and certificates that you use for encryption, authentication, and serving content over HTTPS. In Pega Platform, you create a keystore data instance that points to a keystore file.

  • harnesses

    Organize the content and structure of a portal by defining harnesses. By populating harnesses with sections, you can build a modular interface that promotes reuse and maintainability.

  • Sections

    Use sections in conjunction with harnesses to define the appearance of user forms, rule forms, or composite portals.

  • Previous topic Creating a navigational tree layout
  • Next topic Harness and Section forms - Configuring an External web component section

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