As we discussed earlier, we will allow the user to delete the template, but instead of actually removing it, we will treat it similarly to the process of deleting an event type. The template will disappear from the user's view but will remain in the database with an inactive status. Certificates can still be generated for activities that rely on the deleted template. This approach prevents errors that would occur if a template were permanently deleted while still associated with an activity, as generating a certificate for that activity would fail due to the missing template image and name.
As we discussed earlier, we will allow the user to delete the template, but instead of actually removing it, we will treat it similarly to the process of deleting an event type. The template will disappear from the user's view but will remain in the database with an inactive status. Certificates can still be generated for activities that rely on the deleted template. This approach prevents errors that would occur if a template were permanently deleted while still associated with an activity, as generating a certificate for that activity would fail due to the missing template image and name.