Pega OOTB Concepts
Hi,
I am looking some material around the Pega OOTB Concepts. I tried looking PDN but can't find any detail. Any power point or document with the details would be appericated
Thanks in advance
***Edited by Moderator Marije to add Capability tags***
Accepted Solution
Updated: 20 Apr 2022 10:06 EDT
Pegasystems Inc.
GB
Pegasystems Inc.
GB
@TAHIRMO could you expand on what you man when you refer to 'Concepts'? Which documentation did you already look at?
You can find a Glossary here.
Other concepts are also discussed on the Pega Community Wiki
There is a Discussion that exists on this forum where other users also asked for the definition of Pega terms.
For a more in-depth look at the product functionality we would direct you to our Pega Academy pages for training.
Accenture Inc.
CA
@MarijeSchillern , Thanks for the link to the material. I tried searching the PDN and also referred to Pega plateform help in dev studio.
From the concept perspective, i am looking summary/details on the below topics that covers Pega "OOTB rules, architecture, features"
- General, non-exhaustive list of Pega OOTB components or design
- Why we stick with OOTB versus customization?
- Tips to handle OOTB vs customization with the client
Again thanks for your help in providing direction to the right document for these topics.
Regards
Accepted Solution
Updated: 20 Apr 2022 10:06 EDT
Pegasystems Inc.
GB
@TAHIRMO I think the type of documentation of your requirements does not exist in the exact format you are after.
Pega OOTB rules, architecture and features are all discussed in documents that deal with the actual development side of business solutions.
We do not have a document that specifically goes into the proprietary design.
Your best approach would be to go through the following documents:
Introduction to application development
Getting started with low-code application development
With regards to sticking with OOTB vs customization, these types of discussions are covered in other forum posts, such as this one, and in our official documents such as:
Configuring applications for reuse
@TAHIRMO I think the type of documentation of your requirements does not exist in the exact format you are after.
Pega OOTB rules, architecture and features are all discussed in documents that deal with the actual development side of business solutions.
We do not have a document that specifically goes into the proprietary design.
Your best approach would be to go through the following documents:
Introduction to application development
Getting started with low-code application development
With regards to sticking with OOTB vs customization, these types of discussions are covered in other forum posts, such as this one, and in our official documents such as:
Configuring applications for reuse
Designing applications for reuse and extension
Hopefully these cover the questions you might have.
Accenture Inc.
CA
@MarijeSchillern Thank you very much for the details. I believe i got more details by going through these links. Very much appericated
Best Regards.
@TAHIRMO I think the type of documentation of your requirements does not exist in the exact format you are after.
Pega OOTB rules, architecture and features are all discussed in documents that deal with the actual development side of business solutions.
We do not have a document that specifically goes into the proprietary design.
Your best approach would be to go through the following documents:
Introduction to application development
Getting started with low-code application development
With regards to sticking with OOTB vs customization, these types of discussions are covered in other forum posts, such as this one, and in our official documents such as:
Ten Guardrails to Success
Configuring applications for reuse
@TAHIRMO I think the type of documentation of your requirements does not exist in the exact format you are after.
Pega OOTB rules, architecture and features are all discussed in documents that deal with the actual development side of business solutions.
We do not have a document that specifically goes into the proprietary design.
Your best approach would be to go through the following documents:
Introduction to application development
Getting started with low-code application development
With regards to sticking with OOTB vs customization, these types of discussions are covered in other forum posts, such as this one, and in our official documents such as:
Ten Guardrails to Success
Configuring applications for reuse
Designing applications for reuse and extension
Establishing your reuse layer
Hopefully these cover the questions you might have.