Problem/Motivation

Templates behave quite similarly to quick forms - in some ways they are a simple "form builder" that you can then use as a form to create records in an easier fashion. A small challenge we will have is making it easier for users to navigate to a page/form and start using any given template.

A simple solution to this might be to just create instances of quick forms for templates that users would like to have easy access to. We could also allow a quick form configuration to override/provide default values for the specified template, similar to how plans can be configured to use a template but set further defaults. As an example, a generic harvest template could be made, and 3 quick forms could be configured to use this template, but each setting a different harvest unit to use depending on the crop.

The other idea I have had is to create a "Use template" button on the "Record" listing pages. This is basically an alternative to the generic asset/log forms... the idea being "I have a template for creating standard activity logs", I would rather start with this template than use the full entity form. We could also make the suggestion to use this template when a user begins the full entity form. Maybe this could be configured on each template as "Promote this template" ??

Steps to reproduce

N/A

Proposed resolution

At minimum use quick forms
Consider adding additional template links

Remaining tasks

Implement
Decide next steps

User interface changes

Quick form templates!
Maybe more buttons

API changes

None

Data model changes

None

Comments

paul121 created an issue. See original summary.

paul121’s picture

Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.