Proposal add api_params & api_entity to scheduled_reminder table
Problem The scheduled reminders system lacks nuance on criteria. Fixing this requires both a UI change and a schema change but the combined effort of this is a prohibitive lift so my proposal is that we do the schema change with a future intent to expose in the UI but without action to do so as yet.
Schema change I think we are fairly clear we want this to be a variant of an api call and we have already worked through that for the saved search table adding 2 columns
- api_params
- api_entity
I'd like to propose making the same changes to the scheduled reminders table as the saved_search table OR possibly adding saved_search_id and using saved searches from there.
I'm expecting the initial implementation would work in a similar way to the saved search - ie if the new parameter storage is loading the old code path would be ignored. Potentially we can migrate the old stuff over in time