Create default workflow on installation

[sminnee]

When you install the module, it would be helpful to create a simple 2-step workflow to show how the system works.

The most straightforward way to do this would be a requireDefaultRecords() method that creates the workflow if no workflows exist. That way you could delete the default workflow and it wouldn't come back as long as your had created at least one other workflow.

[sminnee]

Note that this should dramatically lower the barrier to entry for the module.

[nyeholt]

There's been some thought around developer defined workflow templates - at present my thinking is along the lines of

• Define a WorkflowTemplate subclass, eg TwoStepTemplate
• Implement TwoStepTemplate::getCreateFields() which returns a list of fields needed for the initial population of the workflow
• Implement createWorkflow($data) that creates the relevant actions + transitions, using the information input in the createFields to set up the bits and pieces

The main problem I see with putting together the workflow definition in requireDefaultRecords is that it still requires some additional configuration around assignees - though it may be a quicker solution in the short term.

[sminnee]

Aha - you'll see my other comment around assignees. ;-)

[sminnee]

The template idea sounds nice, although it doesn't seem critical if #18 was implemented, as it begs the question "what would the parameters be?" I guess the email content could be parameterised.

[nyeholt]

There's a start on things at https://github.com/nyeholt/advancedworkflow/tree/workflow_templates

The ideas is that you provide a structure via config for the template, which is then interpreted and converted into steps + actions. See https://github.com/nyeholt/advancedworkflow/blob/workflow_templates/_config/workflows.yml as an example structure for defining a workflow template

I haven't got to changing a template -> updating existing workflows, but it's a reasonably straightforward process; not going to spend any time just yet if this isn't overall approach isn't considered worthwhile pursuing

[nyeholt]

Anyone have further input on my previous commit? I'm tweaking things now to add in updates of template versions; we've got a client who's wanting to use this feature so would like to get things merged across if you think it's a reasonable approach for now.

[phptek]

@sminnee @nyeholt can this issue be closed now? There has been a default template for some time now.

[smagnusson]

The issue here is that there is still some set up to do, from memory the
contents of an email template and the recipients of emails and other such
items still don't work, and for example, could be set up to go to the
default user or some other practical default. This was being looked at in
terms of the NZ Govt Common Web Platform but not sure of when or how it
might be addressed. Could be best to solve it here, upstream, at the source.

So, no, in my opinion, we should not close this just yet.

Sig

[phptek]

OK, thanks for that - good feedback.