Commit Graph

9 Commits

Author SHA1 Message Date
692fececc7 case 4716 - unit pick-list customer variant parsed as a number
UnitPickList.GetVariantCriteria put the value of a "customerid:<value>"
variant from the request into the query unparsed, reachable by any login
(security review F43, found during case 4712). The value is now parsed as a
long; anything else means no restriction, as 0 already did. The client's
format ("customerid: 5") still works.

Checked: new test fails on the old code, passes now; pick-list tests 10/10.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-24 14:08:01 -07:00
0a9d1fcbef case 3999 2021-10-14 23:19:12 +00:00
e22db77e5a 2021-07-19 23:18:02 +00:00
dde1b8bb8c rename all variants of naming that hold an AyaType value to "aType" (parameter) / "AType" (not parameter) everywhere front and back; "ayType", "objectType", "oType" all are used in various areas 2021-03-23 17:06:05 +00:00
b52d4546bd 2021-01-07 17:46:40 +00:00
72c5762c7f 2021-01-07 15:58:59 +00:00
c1ea5f6398 2021-01-02 01:40:32 +00:00
74db405e62 2021-01-02 00:30:15 +00:00
ed270e7997 2020-12-31 19:27:30 +00:00