Question
Accenture
IN
Last activity: 21 May 2019 8:15 EDT
PCS 7.3 Search functionality : Issue with Base Name
PCS 7.2 In Development portal we had search for cases based on Alias Name. When you search for a case highest version of all the cases, with same Alias Name appears.
In PCS 7.3 this filter for cases is moved from Alias name to Base Name which is a new property introduced in 7.3. Through the post upgrade Activities they have set base name and it serves the purpose just as it did in 7.2. But for any new Cases created with same name the logic in the screen flow to set Base Name is not consistent with that in Post upgrade activities and different versions of same case appear in the search.
I wanted to know the logic behind the Base Name and if anyone faced this issue before.
Pegasystems Inc.
IN
Looks like the query is more related to framework. Can you please tag it to appropriate topic?
Pegasystems Inc.
IN
Hi Sai,
BaseName is newly introduced in PCS 7.3, this property holds the Name property(Ben-XXX-1234526) of the first version of benefit i.e 01-01.
for ex: Consider the Versions of a Benefit Ben1 and the corresponding Name property for each version
Ben1(01-01) : Ben-101-1234567
Ben1(02-01) : Ben-110-1234657
Ben1(02-02) : Ben-119-1234657
When upgraded to PCS 7.3, All the three version of Ben1 Should have the Same BaseName. In this case all three would have BaseName as "Ben-101-1234567".
BaseName property is introduced to bind different versions of a Benefit Together. As in PCS 7.3, User is allowed to update the AliasName across the versions and reiteration of the entity.
So expected behaviour is that all the versions of the Benefits should have same BaseName. Please try to verify if the same is happening in your case.
Accenture solutions Pvt Ltd
IN
Hi,
This is Nikhil, On behalf of Kiran.
Thanks for the reply.
Yes, what you said is happening through the Post upgrade activities.
Hi,
This is Nikhil, On behalf of Kiran.
Thanks for the reply.
Yes, what you said is happening through the Post upgrade activities.
Pegasystems Inc.
IN
Hi,
Scenario-1 should never happen from OOTB PCS. I mean when user try to create a new entity(for ex Benefit) then if the user try to enter the aliasname that is already existing in the system for that entity type then user should be stopped with an error message(XXXYYYZZZ is already existing in the system please choose a unique name.) and doesn't allow user to proceed. From OOTB PCS creating a version is only allowed from save as new version feature from the search screen. I can see that the only way user can run into this scenario-1 (i.e allowed to create a new entity from the create screen with a name already in the system for that entity type) is if the validation is overridden at implementation layer.
Could you please verify that once.
Accenture solutions Pvt Ltd
IN
Yes, what you said is correct. I just found that Scenario 1 is working for us as our Work Classes(In Implementation layer) are different from the OOTB PCS. This validation is checking for the cases in OOTB class but our work objects are stored in different class. so the validation never got fired.
Thanks for the reply.
Accenture solutions Pvt Ltd
IN
In PCS 7.3 If User is allowed to update the Alias Name across the versions, Won't the Major and Minor version get updated based on the Alias Name and this would disturb the order of versions.
Pegasystems Inc.
IN
No. version will be only be based on BaseName not AliasName from PCS 7.3
Accenture solutions Pvt Ltd
IN
Yes, Thanks.