PENGIN PI! A CRM with the back bone of a feature light ERP system. Utilitarian in design, easy to extend, customize, and deploy. Made by a community, supported by Tobu Pengin.
GNU General Public License v3.0
9
stars
1
forks
source link
[TASK] deletion shouldn't "delete" but "reject" and not load rejected #424
Description
The admin view shouldn't just delete. In fact, deletion should only be used for admin. There should also be a role based function to reject. Rejection should mark the status for the application to be rejected. If the application is rejected, then it should not view, by default.
Details
Please consult our tickets code. The tickets are structured in a manner where they can be viewed as opened, closed, etc. I would like the applications to be the same. We should borrow that code and view the candidates in status codes, like, accepted, maybe, rejected, or deleted.
Deleting should not "delete" the S3 files or the fact someone applied, rather, it should have a deleted code in the status and a date when it was deleted. This will require ORM changes:
[x] status codes for application
[x] status code date change for application
[x] Routes will need to be updated to render the statuses and return tuples of the correct codes. Consult tickets.
View changes:
[ ] borrow ticket view code to render open, accepted, maybe, and rejected only. Delete will be reserved for admin and removed from view in case of griefers or spammers, but the records will remain on file in the event of legal hold action.
Description The admin view shouldn't just delete. In fact, deletion should only be used for admin. There should also be a role based function to reject. Rejection should mark the status for the application to be rejected. If the application is rejected, then it should not view, by default.
Details Please consult our tickets code. The tickets are structured in a manner where they can be viewed as opened, closed, etc. I would like the applications to be the same. We should borrow that code and view the candidates in status codes, like, accepted, maybe, rejected, or deleted.
Deleting should not "delete" the S3 files or the fact someone applied, rather, it should have a deleted code in the status and a date when it was deleted. This will require ORM changes:
[x] status codes for application
[x] status code date change for application
[x] Routes will need to be updated to render the statuses and return tuples of the correct codes. Consult tickets.
View changes: