Difference between revisions of "Portal:Platform Design Patterns"

From PegaWiki
Portal:Platform Design Patterns
Jump to navigation Jump to search
Tag: Visual edit: Switched
(migration)
 
Line 1: Line 1:
 
{{DISPLAYTITLE:Pega Platform design patterns}}
 
{{DISPLAYTITLE:Pega Platform design patterns}}
 
__NOGLOSSARY__
 
__NOGLOSSARY__
 +
__NOCACHE__
 
{|  
 
{|  
 
|-  
 
|-  

Latest revision as of 13:04, 17 February 2021


thumb text-top Pega Platform™ model-driven, unified approach delivers enterprise-grade, agile applications with a no-code authoring experience. Pega Platform design patterns share best practices to successfully deliver Pega projects using all the capabilities of Pega Platform..

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

There are no design patterns for the capabilities

User Experience

There are no design patterns for the capabilities

DevOps

There are no design patterns for the capabilities

Security
Design PatternsDescription
Define Authorization ModelDefining the authorization model.
Securing a public facing applicationSecuring a public facing application
Conversational Channels
Design PatternsDescription
Chatbot Engine extensionsA list of Pega Chatbot engine extension points which you can use to customize the conversational channels behavior.
Using email bots for Natural Language Processing and Machine LearningUsing Natural Language Processing and Machine Learning to optimize email bots
Mobile

There are no design patterns for the capabilities

Reporting

There are no design patterns for the capabilities