| 2020-08-11 20:07:20 |
Blake GH |
description |
EG 3.4
OpenSRF 3.2
PG 9.6
Evergreen suffers from a bug when cloning an action trigger definition. The interface asks the user if they would like to also clone the environment. When staff chose "yes", Evergreen doesn't always* clone the environment. It's unclear when/where/why it doesn't work because it does work sometimes. It seems that it fails more often than not though.
This bug was reported int 2011: bug 728055 with basically the same issue.
I propose that we clone the environment and parameters as a matter of course without the added choice. It's more clicking and I would venture that everyone generally wants to clone that stuff with the template (because it's probably broken without it).
There is a database function already written that does this. Not sure how long this link will work but here it is: https://pastebin.com/2hcK8Xjj
Code attached as well ( clone_action_trigger_event_def_for_org.sql ) |
EG 3.4
OpenSRF 3.2
PG 9.6
Evergreen suffers from a bug when cloning an action trigger definition. The interface asks the user if they would like to also clone the environment. When staff chose "yes", Evergreen doesn't always* clone the environment. It's unclear when/where/why it doesn't work because it does work sometimes. It seems that it fails more often than not though.
This bug was reported in 2011: bug 728055 with basically the same issue.
I propose that we clone the environment and parameters as a matter of course without the added choice. It's more clicking and I would venture that everyone generally wants to clone that stuff with the template (because it's probably broken without it).
There is a database function already written that does this. Not sure how long this link will work but here it is: https://pastebin.com/2hcK8Xjj
Code attached as well ( clone_action_trigger_event_def_for_org.sql ) |
|
