Posted: 15 May 2019 10:33 EDT 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.
Yes, what you said is happening through the Post upgrade activities.
Creating new versions for a case, we have 2 ways for doing that
1.Create a new version of a case using Create Case from search i.e. Create Benefit, Create Plan etc., and give an existing alias name to the case.
In this scenario Base Name is set as Name of the current version in the post action of first screen(When Base Name is Null). Since Base Name is null by default this step always gets executed. So different versions of same case have different base names and as search shows cases with distinct Base Name it will fetch more than one version of a case.
2.Create a new version using Save as New version in the review screen.
In this scenario Base Name for the new version is set as the previous version on click of the Button Save as New version. In the post action of first screen Base Name will not be updated to the Name of the current version as condition "Is Null" fails. Thus, all the versions of a case will have same Base Name as the first version. This agrees with the logic in the post upgrade utilities and with 7.2 search.
We have an issue with scenario 1. we usually use the scenario 1 in creating new versions for a case.
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.
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.