Deduct from unshared EcoAccount #114

New Issue

mpeltriaux · 2022-02-14T08:41:49+01:00

mpeltriaux commented

2022-02-14 08:41:49 +01:00

Status Quo

A user needs to have shared access to an EcoAccount to be able to create a deduction in favor of an Intervention.

Problem

This might result in extremely large lists of shared users for EcoAccounts in the future, since unsharing a user from an Account after the successfull deduction creation might not be done by the users themselves. Furthermore it's an extra step, that required the need to know what 'sharing' does in detail.

Predecessor

The predecessor system followed another approach than we did with the model EcoAccountDeduction. However, the workflow in there proposed a simple verification of the EcoAccount by the conservation office users. This equals our recording of the EcoAccount. After this verification the EcoAccount could be used by everyone on the system, which was no problem because another last verification on the Intervention data (before publishing) would detect problems regarding these pre-deduction relations to an EcoAccount.

Solution

We might follow the same workflow, since there is a human-validation in the end, and return back to KISS on this.

Therefore:

Remove the need for having unshared access on the EcoAccount for creating Deductions
Make recorded EcoAccounts findable using the autocomplete on NewDeductionForm

# Status Quo A user needs to have shared access to an EcoAccount to be able to create a deduction in favor of an Intervention. # Problem This *might* result in extremely large lists of shared users for EcoAccounts in the future, since unsharing a user from an Account after the successfull deduction creation might not be done by the users themselves. Furthermore it's an extra step, that required the need to know what 'sharing' does in detail. # Predecessor The predecessor system followed another approach than we did with the model `EcoAccountDeduction`. However, the workflow in there proposed a simple verification of the EcoAccount by the conservation office users. This equals our `recording` of the EcoAccount. After this verification the EcoAccount could be used by everyone on the system, which was no problem because another last verification on the Intervention data (before publishing) would detect problems regarding these pre-deduction relations to an EcoAccount. # Solution We might follow the same workflow, since there is a human-validation in the end, and return back to KISS on this. Therefore: 1. Remove the need for having unshared access on the EcoAccount for creating Deductions 1. Make recorded EcoAccounts findable using the autocomplete on NewDeductionForm

mpeltriaux added the

enhancement

label 2022-02-14 08:41:49 +01:00

mpeltriaux self-assigned this 2022-02-14 08:41:49 +01:00

mpeltriaux referenced this issue from a commit

2022-02-16 12:35:24 +01:00

#114 Unshared Account Deductions

mpeltriaux referenced this issue

2022-02-16 12:35:39 +01:00

#114 Unshared Account Deductions #120

mpeltriaux commented

2022-02-16 12:36:00 +01:00