View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009076 | Taler | exchange | public | 2024-08-14 15:25 | 2024-08-28 23:30 |
| Reporter | Florian Dold | Assigned To | Christian Grothoff | ||
| Priority | normal | Severity | feature | Reproducibility | have not tried |
| Status | closed | Resolution | won't fix | ||
| Target Version | 0.13 | Fixed in Version | 0.13 | ||
| Summary | 0009076: consider allowing new_measures as an array when making an AML decision | ||||
| Description | It doesn't make much sense to restrict it to a single measure, especially if multiple pieces of data need to be requested. | ||||
| Tags | No tags attached. | ||||
|
|
I have no idea what you are talking about, there is no "new_measures". We have "new_rules" (which is a set), and "next_measures", which is already an array. There are no "new_measures" in the code or specification. |
|
|
I'm talking about this: https://docs.taler.net/core/api-exchange.html#post--aml-$OFFICER_PUB-decision interface AmlDecisionRequest { // ... new_measure?: string; // ... } Is there any reason why the AML officer would only be able to activate one measure? In practice, I'd expect this to be multiple measures, to allow collecting multiple documents. |
|
|
Created b9076 for this. Incomplete SQL, would require major schema changes, not sure if measure(s) or check(s) are what you intend here, this will be a major mess. Not sure why you want this. |
|
|
Discussed offline: We don't necessarily need to have this, can be emulated my a meta-measure where the program activates multiple measures. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-08-14 15:25 | Florian Dold | New Issue | |
| 2024-08-14 15:25 | Florian Dold | Status | new => assigned |
| 2024-08-14 15:25 | Florian Dold | Assigned To | => Christian Grothoff |
| 2024-08-19 08:58 | Christian Grothoff | Note Added: 0023001 | |
| 2024-08-19 08:58 | Christian Grothoff | Assigned To | Christian Grothoff => Florian Dold |
| 2024-08-19 08:58 | Christian Grothoff | Status | assigned => feedback |
| 2024-08-19 16:04 | Florian Dold | Note Added: 0023002 | |
| 2024-08-19 16:04 | Florian Dold | Assigned To | Florian Dold => Christian Grothoff |
| 2024-08-20 09:26 | Christian Grothoff | Note Added: 0023007 | |
| 2024-08-20 13:42 | Florian Dold | Status | feedback => resolved |
| 2024-08-20 13:42 | Florian Dold | Resolution | open => won't fix |
| 2024-08-20 13:42 | Florian Dold | Note Added: 0023014 | |
| 2024-08-26 22:29 | Christian Grothoff | Fixed in Version | => 0.13 |
| 2024-08-28 23:30 | Christian Grothoff | Status | resolved => closed |
