Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Nikhil Agarwal (Nikhil_Agarwal94)
Sun Life Financial Company
Nikhil Agarwal
Sun Life Financial Company
CA
Nikhil_Agarwal94 Member since 2019 16 posts
Sun Life Financial Company
Posted: Aug 12, 2019
Last activity: Aug 14, 2019
Posted: 12 Aug 2019 14:14 EDT
Last activity: 14 Aug 2019 23:17 EDT
Closed

What is the use of Build on Application?

Hi,

I need to understand the use of Build on applications (not MBO)? Is it just there to enable inheritance from the Application used as Built on?

Thanks

***Edited by Moderator Marissa to update platform capability tags****

To see attachments, please log in.
Pega Platform
Low-Code App Development

  • Ramsurendar Govindarajan
Posted: 5 years ago
Posted: 12 Aug 2019 15:11 EDT
Nirmalya Sen Sharma (Nirmalya.SenSharma)
Ernst & Young LLP
Program Manager
Ernst & Young LLP
MT

Application A is built on Application B - Application A now inherits 'every rule' that is in Application B.

Example: Application B has a custom case search gadget. You can either create the same gadget in Application A (if it's stand-alone application and not built on Application B), or you can build your application A on B, and start using that functionality (and even can override it in Application A ruleset).

To see attachments, please log in.
Posted: 5 years ago
Posted: 13 Aug 2019 0:08 EDT
Nikhil Agarwal (Nikhil_Agarwal94)
Sun Life Financial Company
Nikhil Agarwal
Sun Life Financial Company
CA

@N.SenSharma Correct me if I am wrong - inheritance happens through either Pattern or Direct both of which don't need Build on Application. If I want to use reuse an existing capability, e.g. search gadget, can I just not import the rulesets containing that functionality?

To see attachments, please log in.
Posted: 5 years ago
Posted: 13 Aug 2019 8:16 EDT
Nirmalya Sen Sharma (Nirmalya.SenSharma)
Ernst & Young LLP
Program Manager
Ernst & Young LLP
MT

Inheriting functionality is not same as class inheritance; class inheritance is needed when you need to extend/customize any of the functionality/rule of built on application.

A good example would be the following -

Any application that you create is built on PegaRULES applcaution. You create your work classes by inheriting from work-cover- as you need to create your functionalities by reusing the rules from Work-Cover-. Had you not built your application on PegaRULES (the otherwise is actually not possible), you could not be able to establish the class inheritance at the first place.

In some scenario you might not even to setup class inheritance as you will (in most of the cases) reuse the same functionality of built on application as is. As an example, think about the OOTB search gadget the appears on the top of your user portal. It is defined in your built on application (PegaRULES)

 

To see attachments, please log in.

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

Pega Collaboration Center 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