View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0009810 | Taler | exchange AML backoffice (SPA) | public | 2025-04-29 11:11 | 2025-04-30 19:56 |
Reporter | Christian Grothoff | Assigned To | sebasjm | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | assigned | Resolution | open | ||
Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
Product Version | git (master) | ||||
Target Version | 1.0 stretch goals | ||||
Summary | 0009810: wild form for custom measure | ||||
Description | When creating a custom measure and selecting "form-info-investigation", I'm still required to specify an AML program, even though IIRC INFO forms never have AML programs associated (they only SHOW information!). Furthermore, I couldn't add the INFO form directly from the 'standard' list of measures, even though that's a very common use-case, that I should just pick as a measure some information to be shown to the user. So I think the default selection of "Active measures" to have under "Measures" should simply include *all* INFO forms (maybe not if they require some context / templating, but I think for now none of them do, and I don't recall if we have a mechanism to signal that...). | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
|
I will investigate this further, but from the spec I saw that the program is required https://docs.taler.net/core/api-exchange.html#tsref-type-AmlDecisionRequest DecisionRequest -> leg_rules -> custom measure type is MeasureInformation where program is not optional. Meanwhile, I will add INFO type of measure (which is missing) |
|
there is one program called `freeze investigate` which doesn't do anything that just putting all limits to zero. if the decision is already settings the limits i wonder that if the offer wants to set an active measure of INFO and it is already freezing the account then it doesn't make sense to require a program to do something like that. I think the correct solution to this is to allow program as null/undefined (or maybe a NO-OP program) which doesn't do anything useful by definition for + INFO measure: when the officer want to communicate. + FORM measure: when the officer want to get information but no further actions. |
|
freeze investigate is really intended not as an instant measure to be used by the AML officer, but as something to be triggered primarily if we had an error and want to halt all processing until we could investigate. And yes, the correct solution is to allow programs to be null/undefined, and I think that MUST be the case for INFO measures (no AML program, ever). For forms, that's different: if the officer wants to get information, the typical measure is "preserve-investigate" -- the AML officer would setup the KYC form and then *clear* the investigation flag (until the customer submitted the form), as there is no work for the AML officer while waiting for the customer to do the form. At least that's the idea here. So on normal form submission, a common AML program would be preserve-investigate. |
Date Modified | Username | Field | Change |
---|---|---|---|
2025-04-29 11:11 | Christian Grothoff | New Issue | |
2025-04-29 11:11 | Christian Grothoff | Status | new => assigned |
2025-04-29 11:11 | Christian Grothoff | Assigned To | => sebasjm |
2025-04-29 11:11 | Christian Grothoff | File Added: custom.png | |
2025-04-30 16:20 | sebasjm | Note Added: 0024713 | |
2025-04-30 18:42 | sebasjm | Note Added: 0024717 | |
2025-04-30 19:56 | Christian Grothoff | Note Added: 0024722 |