Saturday, 14 March 2020

Linked Property in Pega

Linked Property in Pega

Reference:

PDN help url

We have video about linked property on Pega course  PRPC: USER EXPERIENCE SPECIALIST .


In this Post we will see how to Use Linked property.

Why we have to use linked property?

Assume we have 2 Cases One is to get Customer Information and another one is to process purchase request.

When processing get Customer Information case we will get all the information about Customer like Personal Information about customer, Card Information, etc.


When Processing Purchase Request case we will get Information about What he is going to Purchase like Product Name, Quantity, etc.

Our requirement is to display Customer Information in Purchase request case. So what we will do to achieve this?
We will open Customer Information Case in Purchase request case using Activity then we will display the information.
Declare page we can use.

These may affect application performance because we are using activity to open the Customer Case .Pega provides Liked Property to reduce these complexity.


How Linked Property works:

We have two Case: Customer and Purchase. We can access customer class instance using a purchase class property that property is Linked Property( I.e, CustomerID).

Created a flow in Customer Class to get customer Information.





And its section.


Similarly created a flow in Purchase class

When we select CustomerID(Linked Property) in Purchase request case, we are refreshing the whole section . In below dynamic layout we are showing Customer Case firstname, lastname, cardnumber, cvv using Linked property.

Linked Property Configuration : CustomerID Property in Purchase request class is mapped to Customer class for that class key is pyID of Purchase Request.

Mapped Customer class LastName property in Purchase request class using CustomerID Linked Property. 

Similarly mapped Customer class FirstName property in Purchase request class using CustomerID Linked Property.

When we provide CustomerID(pyID) which is available in Customer class the corresponding Customer class instance will be opened and we can able to access whole instance using this CustomerID Property.

Assume we are providing a CustomerID in Purchase Request case, If the provided CustomerID is available in Customer class table then it is a Linked Page Hit, or else it is a Linked Page Miss.

Run the flow and check it.

Created a customer case (C-171)



Created a Purchase Case. Our expectation is on Selecting the CaseID corresponding Customer FirstName, LastName , CardNumber and CVV should populate

Tracing while changing the value.



C-171 is available in customer class so Liked Page hit


We are displaying C-171.FirstName, C-171.LastName, C-171. CardNumber, C-171.Cvv in below section.


We can see the Successful hit pages in Linked Property Pages in Clipboard.

Linked Property clipboard Page will remove on Commit.

Please ask if you have any doubt in comment.😊

6 comments:

  1. Hi Brother
    This Post was awesome because of till now i don't have any idea of Linked property how to we use in pega, after having this post i am very clear on Linked property it's really helpful to all the people who are not have knowledge on this scenario

    I am really appreciate Please keep on post continually on good topic

    ReplyDelete
  2. can you share the drop down configuration

    ReplyDelete
    Replies
    1. Hi,

      For this post I Used Local list for drop down. And I hard Coded the CaseID in the local list.

      Thanks

      Delete
  3. This information is really awesome thanks for sharing most valuable information.
    Pega Online Training Hyderabad
    Pega Online Training India

    ReplyDelete