Override sort function not working on v8.8.1
When i update v8.2.2 ➔ v8.8.1
At v8.2.2, the sort by pyId working correctly with function compareWorkIDs by order:
I-1, I-2, I-10, I-11
But when i update to v8.8.1, the sort by pyId working not correctly, that order by String:
I-1, I-10, I-11, I-2
I see pyId property, that hasn't changed, on Override sort function still has compareWorkIDs. The function compareWorkIDs seem not working.
I want to sort by pyId working on v8.8.1 correctly, So how can i fix this?
***Edited by Moderator: Pooja Gadige to add support case created tag***
Accepted Solution
Pegasystems Inc.
GB
The support ticket was resolved with the following information:
Root cause description:
The sort order that was present in 8.2.2 is not replicable in 8.8.1. Though the mechanism was not determined, the default sort order was not changed between 8.2.2 and 8.8.1, and the reported 8.2.2 sort order was not replicable in an out of the box environment.
The behaviour seen in 8.8.1 is the intended behaviour in both 8.8.1 and 8.2.2, as .pyID is sorted as a text value, so the numerical order is not handled the same way as it would be if sorted purely on a numerical basis.
If it were the case that the OOTB behaviour in 8.2.2 was that pyID was sorted as seen in 8.2.2, and that was not the case in 8.8.1, even if the 8.2.2 sort order was not the intended behaviour, we would have been able to raise this as a regression bug.
Solution type: Explanation
The default sort order was not changed between the 2 listed versions, nor was the described behaviour reproducible. As the sort order seen in 8.8.1 is the intended and expected behaviour, it was determined that this will be handled via customization.
Pegasystems Inc.
GB
@NguyenV16767218 could you take a look at the following suggestion: Inconsistency in the sorting functionality of Work Objects by ID
You can try to use custom sort or try to change column value to integer instead of string. If the table is optimized you can uncheck the optimized table option. However for further steps you can check our community
https://community.pega.com/support/support-articles/inconsistency-sorting-functionality-work-objects-id https://support.pega.com/question/how-let-pega-sort-alphanumeric-text-correctly https://support.pega.com/question/sorting-case-ids-numerically-instead-alphanumeric-way
CompareWorkID sort override function is used to perform sorting of work IDs.
See the following article Functions supported for optimization
CompareWorkID sort override function works fine when it is optimized. Could you check in "Optimize code" - Allow Check box in the Section - Table - Layout Properties?
fpt
JP
CompareWorkID sort override function works fine when it is optimized. Could you check in "Optimize code" - Allow Check box in the Section - Table - Layout Properties?
this work but layout has changed. at v8.2.2, i don't need "use custom sort or try to change column value to integer instead of string", that still work. So on v8.8.1 if i do that, it take pretty much efforts. Is there any other way?
Updated: 1 Mar 2023 8:49 EST
Pegasystems Inc.
GB
@NguyenV16767218
The functionality did not change between versions. Are you sure that you were not already using sort customization in 8.2.2?
if you believe that it is not working as documented could I ask that you log this as a support incident on the MSP?
Please provide the INC reference here to help us track it.
fpt
JP
Accepted Solution
Pegasystems Inc.
GB
The support ticket was resolved with the following information:
Root cause description:
The sort order that was present in 8.2.2 is not replicable in 8.8.1. Though the mechanism was not determined, the default sort order was not changed between 8.2.2 and 8.8.1, and the reported 8.2.2 sort order was not replicable in an out of the box environment.
The behaviour seen in 8.8.1 is the intended behaviour in both 8.8.1 and 8.2.2, as .pyID is sorted as a text value, so the numerical order is not handled the same way as it would be if sorted purely on a numerical basis.
If it were the case that the OOTB behaviour in 8.2.2 was that pyID was sorted as seen in 8.2.2, and that was not the case in 8.8.1, even if the 8.2.2 sort order was not the intended behaviour, we would have been able to raise this as a regression bug.
Solution type: Explanation
The default sort order was not changed between the 2 listed versions, nor was the described behaviour reproducible. As the sort order seen in 8.8.1 is the intended and expected behaviour, it was determined that this will be handled via customization.