Predefined workflows

[tim-pearce]

I haven't figured out how this might work or even what it might look like.

For each ministry for which one records information there is a certain flow of functions you use and a sub-set of 'definitions' you use.

A 'flow' would define :-

• a set of 'functions' to use
• what definitions (groups, categories} are visible in each function

So for instance a person tasked with maintaining attendance information for a ministry would have a set of 'flows' to select from to perform the tasks required.

Like I said at the start, I don't know how this would work - it's just something to think over at present.

[tim-pearce]

Maybe a start is to create a concept of a 'task mode' (for want of a better description).

For example I might have 'Playgroup attendance mode'. When I turn this mode on :-

• I only see the groups related to the children and their parents (In my case that is 'Playgroup_2023)
• I only see the statuses related to them (In my case 'Current', 'Registered', 'Unregistered' and 'Inactive')
• I would only see reports and document templates that are relevant

When I am working on the rosters for the Playgroup helpers I would have another set of filters defined.

This sounds quite doable as it's basically just a collection of lists that just a few functions need to refer to before populating lists the user sees.

[jefft]

It might be useful to describe a real scenario / unmet need first (a User Story in Agile-speak), before outlining potential solutions.

[tim-pearce]

In my scenario above when I am assigning people to playgroup (or changing their status) I am presented with unrelated classes, statuses, reports etc. So a 'use case' (similar idea to 'story')

• Select 'Playgroup attendance mode'
• Attendance record Playgroup_2023 (the only choice) with status of 'Registered' (only 4 to choose from)
• Mark attendance
• Add new children/families only group shown id Playgroup_2023, only 4 statuses shown
• Attendance display
• Document merge only a limited number of choices
• Reports only 'Playgroup_weekly_worksheet' is shown
• Document merge 'Playgroup_weekly_worksheet'
• Return to 'normal mode'

[tbar0970]

I get the general principle - trimming out irrelevant stuff to smooth the way for common tasks.

One existing feature that relates here is the ability to turn certain features off altogether - see system config. (if a church doesn't use rosters or service planning, they can be hidden). Another current feature is to restrict access to features and to groups/congregations for each user account. This goes some way towards removing clutter for the actual tasks people need to do. But I can see there is scope for more of this.