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.

Extension points

Updated on April 5, 2022

An extension point is an activity or other rule that is designed and intended to be overridden to meet application needs. Many such rules are empty stubs that contain no steps. Typically, the overriding rule is in a derived class.

The Pega Platform itself includes a few dozen extension points. For example, the empty activity Code-Security.ApplicationProfileSetup is executed when an operator logs on. If your application requires special initialization processing for authenticated operators, you can override this application (in your application's ruleset) to perform such processing.

Extension points in frameworks

An extension point is a rule (typically a blank or empty rule) that is marked as an Extension in the Status field on the New or Save As dialog box. The corresponding property Rule-.pyMethodStatus does not appear on the rule form, does not affect rule resolution or execution of the rule, and cannot be changed.

For example, a flow in a framework may include an Integrator shape that connects to a customer master file database. In the framework ruleset, this can be an empty activity with an activity type of Connect, marked as an extension. When rulesets are an implementation of that framework, the developers must override the empty activity with a functioning interface to their customer master file.

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