View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009609 | Taler | exchange | public | 2025-03-11 14:22 | 2025-03-20 12:50 |
| Reporter | Florian Dold | Assigned To | Christian Grothoff | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | resolved | Resolution | no change required | ||
| Target Version | 1.0 | Fixed in Version | 1.0 | ||
| Summary | 0009609: new rules in AML decision should be optional | ||||
| Description | It should be entirely valid to make a decision without changing the current rules. That is especially important for submitting multiple forms/attributes, where we almost always want the rules to stay the same. | ||||
| Tags | No tags attached. | ||||
|
|
I'm not sure I agree here. NULL rules should be allowed, yes, but that means "use default rules", not "preserve rules". IMO the AML SPA should make it easy (and default to!) "preserve rules" (which is what I told Sebastian: fill in the AML SPA with the current rules initially, and maybe also have a button to reset to 'current' rules). Anyway, that means this is a SPA-issue, not a protocol/exchange issue. |
|
|
Also okay for me to go back to default rules with NULL. But IMO then we should also allow the AML SPA to *show* those rules. Right now there's no way to do that! |
|
|
And also: What happens if the current rule set is expired? I *guess* the answer is: The new AML decision overrides whatever the successor_measure would do, the successor_measure is never run if the old decision expires without a new decision being present (as expiration is handled lazily). |
|
|
AML officer decision always overrides everything else, including (not yet finished/pending) successor measures. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-03-11 14:22 | Florian Dold | New Issue | |
| 2025-03-11 14:22 | Florian Dold | Status | new => assigned |
| 2025-03-11 14:22 | Florian Dold | Assigned To | => Florian Dold |
| 2025-03-11 14:41 | Christian Grothoff | Note Added: 0024176 | |
| 2025-03-19 16:15 | Florian Dold | Note Added: 0024245 | |
| 2025-03-19 16:39 | Florian Dold | Note Added: 0024247 | |
| 2025-03-19 16:39 | Florian Dold | Assigned To | Florian Dold => Christian Grothoff |
| 2025-03-20 12:49 | Christian Grothoff | Note Added: 0024255 | |
| 2025-03-20 12:50 | Christian Grothoff | Status | assigned => resolved |
| 2025-03-20 12:50 | Christian Grothoff | Resolution | open => no change required |
| 2025-03-20 12:50 | Christian Grothoff | Fixed in Version | => 1.0 |
