One of the exciting new features of Joomla 4 is Workflows. The Joomla 4 workflow is designed for adjusting the publishing sequence for articles to include more aspects like publishing steps (think draft > editing > published) or access control for transitions (think author, editor, publisher).
During the Virtual JUG, Tim will take it one step further and combine with the power of custom fields to build a simple practical application using only core Joomla 4, with workflow to show how the new feature can be implemented for something different to a blog.
Create Override for article form in your template
Customise as required
/yourtemplate/html/com_content/form/edit.php and customise look for this category
Note this is the geeking coding bit
that a regular Joomla user
wouldn’t be able to do. Maybe in
future there will be an easier way.
Create a My Support Requests view
Note: You can adjust what columns you see on the List Layouts tab.
My Leave Applications view
You could take this even further with an override and customise to include columns such as
Override the view form with alternate layout
/yourtemplate/html/com_content/article/default.php and rename as supportapp.php
Edit as required, then assign that layout to your menu item
Another geeking coding bit that
a regular Joomla user may not
be able to do.
You can also use Access Levels (optional)
• If you want to further restrict access, use
access levels which you can apply to menu
item and category
Set up some test users
Create at least one person for each role to test it out
Now let’s see it in action
Customer creates a Support Request. It goes to
Level 1 Helpdesk for review
Only transition (in this case status) is to send to
Level 1 Helpdesk
Level 1 Helpdesk step
When sent to helpdesk, they can reject, escalate,
complete, or request more information
Note if customer logs in, they don’t
see the helpdesk transition states
Or if Level 2 Support logs in, they
can’t reject, ask for more info or
complete, they can only escalate.
Level 2 support step
• Level 2 support can now resolve the issue and
transition the next state
Customer confirm step
• Customer can now reopen if issue is not
resolved, or mark as complete.
Support Request Complete
• No further action required, but record could be
deleted or archived later if needed
• Can’t send transition emails to author, only groups or specific people
• Need coding skills to override form and view
• All the records are saved in com_content (Joomla articles)
• Users can see all records in My Support Requests view, not just their
own (can be fixed with layout override)
• Records can get stuck “checked out” to user