Question
ING Belgium SA NV
BE
Last activity: 18 Sep 2023 6:13 EDT
Add declare index condition on a property in the same occurence
I have a declare index on a property in a pagelist in my main page. Let's say. CustomerID in CustomerList. I only want to store this index in case the CustomerType = "Some Type".
When creating a When Rule on "CustomerList" class, the declare index rule won't take it as it is not of the main page class.
How can you make sure only the ones I want to save are taken into account?
Example: CustomerList(1)
.CustomerID : 1
.CustomerType : "Some Type" ==> should be stored
CustomerList(2)
.CustomerID: 2
.CustomerType : "Another Type" ==> should not be stored in the declare index table.
P3Fusion
IN
@Joris Claus whatever be the pagelist data class defined in the declare index rule created, make sure the when rule used in the declareindex should be in the class of the rule created.
make sure inside the when of Declareindexrule designed as per the screenshot (img1).
As best practice keep the pagelist property to get accessed by the class where the index rule get created.
let me know for any questions.
ING Belgium SA NV
BE
@MatheswaranRavi , this can't be the solution as your when condition will in this case always say true, even though it should be only valid for the seconde occurence of .CustomerList.
You should be able to check whether the CURRENT occurence of .CustomerList has a value "Some Type" in .CustomerType.
Pegasystems Inc.
CA
Hi Joris, Can you please let me know the reason behind storing specific values in the Index table? Is this due to Database storage space? or some other reason?
ING Belgium SA NV
BE
It has another reason. In case the customer team finds out there is a duplicate in customer data, they merge two clientnumbers into one remaining. All this happens in another application (non-Pega) and is broadcasted using a Kafka topic.
In order to keep our data clean, we need to replace the old customerid with the remaining one in all our inflight cases. In order to be able to find all the cases where the old customerid is used, we need to find them. This I do by running a report. For customerid's stored in a single page, I can simply expose them and filter on them. For the ones stored in a pagelist, I need a declare index. In some cases, the pagelist has a property that can hold several types of id's. And another property telling me what kind of id is stored. So I only need to add thoses id's to my declare index where the id type is of a specific type.
Hope it's more clear now...