Difference between revisions of "Welcome to PegaWiki"

From PegaWiki
Welcome to PegaWiki
Jump to navigation Jump to search
(updated verbiage)
Tag: Visual edit
 
(34 intermediate revisions by 7 users not shown)
Line 1: Line 1:
 +
{{DISPLAYTITLE:Welcome to Pega Community Wiki!}}
 +
 +
{| class="wikitable" style="width:100%;"
 +
|+
 +
! style="background: #127a80;color:white;font-size:large;" |Pega Community Wiki
 +
|-
 +
 +
| style=" border-width: 0px; background: #f8f9fa;" |
 +
{| class="wikitable" style="width:100%;"
 +
|+
 +
! style="background:white;border-top-color: #127a80;;border-top-style:solid;border-top-width:10px;font-size:large;color:#00457c;" | Getting started
 +
|- style="vertical-align: top;background:white;"
 +
|
 +
We are glad you are here! Wikis are community-driven and designed to help people create and collaborate in real time.
 
<br>
 
<br>
To get started search for a Design Pattern or review content by selecting Design Patterns or Glossary terms.<br>
 
 
<br>
 
<br>
'''What is a Design Pattern?'''<br>
+
The design patterns provided here are knowledge assets that explain how to address common implementation patterns using out-of-the-box Platform and Application capabilities.
A Design pattern document:<br>
 
 
<br>
 
<br>
* should share a specific opinion on what a user should do, look for or understand when they are trying to implement something in Pega.<br>
+
We encourage you to browse the current <noglossary>collection</noglossary>.  
* should share the best practices<br>
+
<br>
* should provide at least one real-life example<br>
+
<br>
* should provide real numbers/metrics (for example: we suggest x number of case stages or if this indicator is higher than x, you should do this)<br>
+
<p>'''Sign in''' to Wiki so that you can perform the following actions:</p>
* should be straightforward and easy to read (aka not too long!)<br>
+
*Add a design pattern to your Watchlist to receive an email update if something changes
* should link/reference other documents (especially those in Community) that have implementation details that are relevant to the usage pattern.<br>
+
*Share a suggestion to improve the design pattern using the Suggestion tab
* should not go into specific step by step implementation details or definitions (this content should be in other areas and linked to)<br>
+
<br>
 +
<p style="background:#eaecf0; padding-top:10px;padding-bottom:10px;padding-right:10px;padding-left:10px;">''' Note:''' New design patterns are regularly added by Pega experts, bookmark this page and be sure to check out what’s new!</p>
 +
|-
 +
|'''Need support or have questions?'''
 +
Contact [https://community.pega.com/pega-community-feedback?action=report_an_issue_with_pega_community_wiki us]
 +
|}
 +
{| class="wikitable" style="width:100%;"
 +
|+
 +
! style="background:white;border-top-color: #127a80;;border-top-style:solid;border-top-width:10px;font-size:large;color:#00457c;" | Coming soon
 +
|- style="vertical-align: top;background:white;"
 +
|
 +
*Ability for you to suggest your own design patterns
 +
|}
 +
|}

Latest revision as of 10:25, 11 May 2021


Pega Community Wiki
Getting started

We are glad you are here! Wikis are community-driven and designed to help people create and collaborate in real time.

The design patterns provided here are knowledge assets that explain how to address common implementation patterns using out-of-the-box Platform and Application capabilities.
We encourage you to browse the current collection.

Sign in to Wiki so that you can perform the following actions:

  • Add a design pattern to your Watchlist to receive an email update if something changes
  • Share a suggestion to improve the design pattern using the Suggestion tab


Note: New design patterns are regularly added by Pega experts, bookmark this page and be sure to check out what’s new!

Need support or have questions?

Contact us

Coming soon
  • Ability for you to suggest your own design patterns