Difference between revisions of "Portal:Platform Design Patterns"

From PegaWiki
Portal:Platform Design Patterns
Jump to navigation Jump to search
Tag: Visual edit: Switched
Tag: Visual edit: Switched
Line 40: Line 40:
 
|- style="vertical-align: top;background:white;"
 
|- style="vertical-align: top;background:white;"
 
|
 
|
* [[#case_man|Case Management]]               
+
* [[#case_man|Case Management]]
 +
* [[#low_code|Low-Code App Dev]]               
 
* [[#data_int| Data Integration]]  
 
* [[#data_int| Data Integration]]  
 
* [[#user_int| User Interface]]
 
* [[#user_int| User Interface]]
Line 75: Line 76:
 
|
 
|
 
{{#ask:[[Class::Design pattern]] [[Approval status::approve]] [[Application::Platform]] [[Capability/Industry Area::Case Management]]
 
{{#ask:[[Class::Design pattern]] [[Approval status::approve]] [[Application::Platform]] [[Capability/Industry Area::Case Management]]
 +
|mainlabel=Design Patterns |+width=54%
 +
|?Description |+width=40%
 +
|?Version as of=Version |+width=6%|+align=center
 +
|format=broadtable
 +
|headers=plain
 +
|class=wikitable sortable
 +
|limit=999
 +
}}
 +
|}
 +
{| class="wikitable"
 +
|+
 +
! style="width: 1680px;background:white;border-top-color: #127a80;;border-top-style:solid;border-top-width:10px;font-size:large;color:#00457c;" id="low_code" |Low-Code App Dev
 +
|- style="vertical-align: top;background:white;"
 +
|
 +
{{#ask:[[Class::Design pattern]] [[Approval status::approve]] [[Application::Platform]] [[Capability/Industry Area::Low-Code App Dev]]
 
|mainlabel=Design Patterns |+width=54%
 
|mainlabel=Design Patterns |+width=54%
 
|?Description |+width=40%
 
|?Description |+width=40%
Line 101: Line 117:
 
{| class="wikitable"
 
{| class="wikitable"
 
|+
 
|+
! style="width: 1680px;background:white;border-top-color: #127a80;;border-top-style:solid;border-top-width:10px;font-size:large;color:#00457c;" id="User_int" |User Interface
+
! style="width: 1680px;background:white;border-top-color: #127a80;;border-top-style:solid;border-top-width:10px;font-size:large;color:#00457c;" id="user_int" |User Interface
 
|- style="vertical-align: top;background:white;"
 
|- style="vertical-align: top;background:white;"
 
|
 
|

Revision as of 18:06, 4 December 2020

thumb text-top Pega Platform's model-driven, unified approach delivers an enterprise-grade, agile application with a no-code authoring experience. Pega Platform design patterns share best practices and insights, supporting the developer community to successfully deliver Pega projects using all the capabilities of Pega Platform.

Overview
Featured Patterns
Knowledgebase Links
Featured Capabilities
Design Patterns
Platform PatternsCapability/Industry AreaDescriptionVersion
Apply validations to ensure data integrityLow-Code Application DevelopmentApplying various types of validations in an application8.4
Best practices for non-functional aspects of the end-user experienceApplication developmentBest practices for non-functional aspects of the end-user experience8.5
Chatbot Engine extensionsConversational ChannelsA list of Pega Chatbot engine extension points which you can use to customize the conversational channels behavior.8.6
Define Authorization ModelSecurityDefining the authorization model.8.4
Defining and applying case statusesCase ManagementDefining case statuses8.4
Designing Pega unit testsLow-Code Application DevelopmentBest practices for designing Pega unit tests8.5
Editing file listener vs queuingData integrationBest practices for modifying the external system data intake process by editing the file listener and queuing8.1
Identify Case TypesCase ManagementIdentifying the case types for an application.8.4
Optimize an application's performanceLow-Code Application DevelopmentTesting and tuning an application during its application lifecycle to optimize performance.8.4
PDF document generation patternsCase managementMethods of creating PDF files in Pega Platform8.6
Securing a public facing applicationSecuritySecuring a public facing application8.4
Using email bots for Natural Language Processing and Machine LearningConversational ChannelsUsing Natural Language Processing and Machine Learning to optimize email bots8.4
When to use a dynamic caseCase ManagementDeciding when to use a dynamic case8.4
When to use a sub-caseCase ManagementWhen to use a sub-case to assist with processing work8.4
When to use sub-processesCase ManagementDeciding when to use a sub-process8.4
Case Management
Design PatternsDescriptionVersion
Defining and applying case statusesDefining case statuses8.4
Identify Case TypesIdentifying the case types for an application.8.4
When to use a dynamic caseDeciding when to use a dynamic case8.4
When to use a sub-caseWhen to use a sub-case to assist with processing work8.4
When to use sub-processesDeciding when to use a sub-process8.4
Low-Code App Dev
Data Integration
User Interface