Can propositions be sorted by multiple properites in a Decision Strategy
Hi
In a pega Decision strategy is it possible to prioritise propositions by multiple properties? Similar to the way we can specify multiple columns in a sql order by clause.
Also, is there a way to dynamically specify the number of proposition to select in a prioritise component? Rather than 'all' or a hardcoded number.
Thank you
Accepted Solution
Updated: 2 Oct 2020 16:30 EDT
Pegasystems Inc.
NL
To dynamically select the # of returned SRs have a prioritization component rank them and output all, then filter on pxRank.
Pegasystems Inc.
NL
Hello.
To learn more about decision strategies and prioritize component I recommend you to take the https://academy.pega.com/library/8/pega-certified-decisioning-consultant course. Specifically the Selecting the most profitable proposition module.
Let me know if that helps.
Regards,
Miki
Accepted Solution
Updated: 2 Oct 2020 16:30 EDT
Pegasystems Inc.
NL
To dynamically select the # of returned SRs have a prioritization component rank them and output all, then filter on pxRank.
Pegasystems Inc.
NL
Re sort on multiple properties.
The prioritization component accepts an expression as the prioritization. You could concatenate the properties and sort alphabetical. But that may be suboptimal for numeric results. Alternatively you can probably get this done with a combination of filter and group-by shapes but I don't think there is an easy generic way. However I have not seen this request before - so why do you want to sort this way? Do you have an example?
Tech Mahindra
IN
Hi @Otto_Perdeck,
I too have a similar kind of requirement to implement. I have a pagelist and need to sort it based on 3 columns. PFB for the sample results. Here I should sort first on the earliest date if we get any same dates records then go for highest amount if we get equal amount records with same date then go for least certificate number. Can you please suggest some approach in strategy.
| Date | Amount | Certificate Number |
| 10/11/2020 | 100 | 7 |
| 8/11/2020 | 500 | 2 |
| 18/11/2020 | 10000 | 5 |
| 18/11/2020 | 9000 | 4 |
| 20/11/2020 | 1000 | 3 |
Thanks,
Vikas Kagana.
Updated: 18 Nov 2020 7:06 EST
Pegasystems Inc.
NL
Hi Vikas,
Unfortunately the prioritization (sort) component does not take multiple conditions. So as I mentioned before, a workaround could be to turn the properties into fixed width strings, then sort on the concatenation of these strings. Not pretty but it may do the job. So by padding the numbers with zeros you get e.g.
"20201110T120000.000 GMT" + "0000100" + "00007"
And then just use this in your prioritization expression
To pad a numeric value to a string of 5 characters you can use an expression like
@substring( "0000" + .InitialCount, length("0000" + .InitialCount)-5)
So your prioritization expression becomes something like
This gives the order 5-3-4-1-2 which I believe is what you're looking for.
Admittedly, this would only work with integer values. For doubles you would need to do some more tricks to make them fixed width while keeping their numerical order.
An alternative solution might be possible using a cascade of group by components, then concatenating the original ranks in groups. I haven't been able to make that work however - not yet ;).
-Otto