Difference between revisions of "Creating a new implementation application on Pega Customer Service"

From PegaWiki
Jump to navigation Jump to search
(Very initial draft)
Tag: Visual edit
 
(Draft 1.1)
Tag: Visual edit
Line 7: Line 7:
 
|Applications=Customer Service
 
|Applications=Customer Service
 
|Capability Area=All industries
 
|Capability Area=All industries
|Version=8.4
+
|Version=8.5
  
 
}}
 
}}
Line 21: Line 21:
 
Pega Customer Service provides a guided and streamlined series of steps to help implementers build their custom application with ease while recognizing the various options presented in the process ranging from selection of existing cases, data objects, channels to determining the application structure. In this article, we will understand these options to help make informed decisions while building a new custom implementation application to avoid rework or refactor at a later point. We shall also understand the artefacts created in the new application as a result of these choices that would help speed up the implementation and hence reduce costs.
 
Pega Customer Service provides a guided and streamlined series of steps to help implementers build their custom application with ease while recognizing the various options presented in the process ranging from selection of existing cases, data objects, channels to determining the application structure. In this article, we will understand these options to help make informed decisions while building a new custom implementation application to avoid rework or refactor at a later point. We shall also understand the artefacts created in the new application as a result of these choices that would help speed up the implementation and hence reduce costs.
  
== Use case examples ==
+
== Applicability ==
Provide a business example to help users understand the objective.
+
The steps detailed below shall apply for any Pega Customer Service application irrespective of the business vertical. The screenshots used below are for illustration purpose only. The actuals may vary across different Pega Customer Service applications.
  
== Before you begin ==
+
== Prerequisites ==
Is it necessary to plan anything in advance, or are external steps using other tools required to achieve the goal? If any specific configuration procedures (how-tos) exist on Pega Community pages, you can link to those assets here by providing the URL.
+
# Make a business decision on whether you want to create a new framework application and then build an implementation application on top of it, or you want to build a new implementation application. Below should help you make that decision:
 +
## Build a new framework application if you have multiple companies, line of business or entities that may a share a common set of assets. Then build a new implementation application for each such entity on top of this new framework application.
 +
## Build a new implementation application of top of Pega Customer Service, if you have a single line of business or entity; and do not anticipate to build multiple applications representing each entity.
 +
# Ensure you have an operator that points to access group - CustomerService:AppSetup - if you wish to build an application on top of Pega Customer Service. For the Pega Customer Service vertical applications, your operator should point to either of these access groups based off business vertical - CustomerServiceComms:AppSetup (Communications); CustomerServiceForFS:AppSetup (Financial Services); CustomerServiceHC:AppSetup (Healthcare); CustomerServiceForIns"AppSetup (Insurance). This operator will enable us land us in the new application wizard with the corresponding application template already pre-selected.
  
== Process/Steps to achieve objective ==
+
== Understanding various options presented in new application wizard ==
What do individuals need to know to achieve the outcome? What do individuals need to know to achieve the outcome? Enter the precise steps to guide the user to achieving the desired outcome. Remember to always state where in the software the user must perform an action, before giving the action.  
+
Once we login with requisite operator, we would see the new application wizard with the appropriate Pega Customer Service application already pre-selected.  
 
+
[[File:App wizard on login.png|left|frameless|500x500px|New Application wizard on login with application template pre-selected]]
If “How To…” documents exist for specific configuration procedures please link (using the url) to those assets on the community **
 
  
 
== Results ==
 
== Results ==
 
What do you expect the user to see or be able to do after they complete this design pattern?
 
What do you expect the user to see or be able to do after they complete this design pattern?

Revision as of 10:43, 15 October 2020


Curator Assigned
Request to Publish
Description Understand the options presented while running the new application wizard to make informed choices while building a new implementation application
Version as of 8.5
Application Customer Service
Capability/Industry Area All industries

↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓ Please Read Below ↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓

Enter your content below. Use the basic wiki template that is provided to organize your content. After making your edits, add a summary comment that briefly describes your work, and then click "SAVE". To edit your content later, select the page from your "Watchlist" summary. If you can not find your article, search the design pattern title.

When your content is ready for publishing, next to the "Request to Publish" field above, type "Yes". A Curator then reviews and publishes the content, which might take up to 48 hours.

↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓ The above text will be removed prior to being published ↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓

Guided steps to building a new Pega Customer Service implementation application[edit]

Pega Customer Service provides a guided and streamlined series of steps to help implementers build their custom application with ease while recognizing the various options presented in the process ranging from selection of existing cases, data objects, channels to determining the application structure. In this article, we will understand these options to help make informed decisions while building a new custom implementation application to avoid rework or refactor at a later point. We shall also understand the artefacts created in the new application as a result of these choices that would help speed up the implementation and hence reduce costs.

Applicability[edit]

The steps detailed below shall apply for any Pega Customer Service application irrespective of the business vertical. The screenshots used below are for illustration purpose only. The actuals may vary across different Pega Customer Service applications.

Prerequisites[edit]

  1. Make a business decision on whether you want to create a new framework application and then build an implementation application on top of it, or you want to build a new implementation application. Below should help you make that decision:
    1. Build a new framework application if you have multiple companies, line of business or entities that may a share a common set of assets. Then build a new implementation application for each such entity on top of this new framework application.
    2. Build a new implementation application of top of Pega Customer Service, if you have a single line of business or entity; and do not anticipate to build multiple applications representing each entity.
  2. Ensure you have an operator that points to access group - CustomerService:AppSetup - if you wish to build an application on top of Pega Customer Service. For the Pega Customer Service vertical applications, your operator should point to either of these access groups based off business vertical - CustomerServiceComms:AppSetup (Communications); CustomerServiceForFS:AppSetup (Financial Services); CustomerServiceHC:AppSetup (Healthcare); CustomerServiceForIns"AppSetup (Insurance). This operator will enable us land us in the new application wizard with the corresponding application template already pre-selected.

Understanding various options presented in new application wizard[edit]

Once we login with requisite operator, we would see the new application wizard with the appropriate Pega Customer Service application already pre-selected.

New Application wizard on login with application template pre-selected

Results[edit]

What do you expect the user to see or be able to do after they complete this design pattern?