Blocks: Workflow block
he Workflow system is used at the OU to manage the production of courses and some activities. It comprises a block and a related admin report.
A workflow (for our purposes) is a linear sequence of steps. A step has
- a name
- some instructions;
- a check-list of actions;
- a list of roles who are responsible for performing this step;
- a list of actions that are taken automatically when the step is started/finished, for example assigning roles or changing activity settings.
The system allows the definition of different workflows. Each workflow has
- a name
- a description
- an indication of the type of thing it relates to (e.g. ‘course’, ‘mod_quiz’)
Under Admin -> Plugins -> Blocks -> Workflow, there is an interface for Administrators to define and edit workflows, and to import and export workflow definitions as XML.
To use a workflow to manage the production of, say, a course, you go to the course, and add a workflow block to it. Initially, the block will display a message “There is currently no workflow associated with this course.” with an Add workflow button. Clicking the button allows you to select from any of the workflows that are appropriate for ‘course’.
When the workflow is added to the course, the first step in the workflow becomes active. The workflow block now displays the step instructions for the currently active step; the checklist items as a list of check-boxes; a comments area; a Finish step button; and a link to the workflow overview.
When a step becomes active, all the people responsible for completing the step are sent an email informing them that they should do the step. These people may also get an additional role assigned to them in the context the workflow applies to.
The comments area in the workflow block is a simple editable text area where people working on the step can leave notes for each other.
The Finish step button leads to a confirmation page. If the action is confirmed, then the workflow advances to the next step. When the last step of the workflow is finished, the workflow either stops, or loops back to one of the other steps.
The workflow overview gives an overview of all the steps in this workflow, and the progress through it. The system tracks the timestamp, and the user, each time a step is finished or made active.
The overview page also allows workflow administrators (those with an appropriate capability) to jump the workflow to any particular step.
There is also an admin reports that summarise the workflow across a selection of courses or activities.
I recently created a Workflow and made it accessible to a new role, Workflow administrator based on the Teaching Role.
I've then assigned this Workflow to a GRID formatted course, and assigned one Tutor in the Course as a Workflow Administrator.
Almost everything works - The Workflow administrator is the only person who can see and action the Workflow, Students can select Grid Items and they open normally.
However, when teachers select Grid items they do not open in either the normal view or the editing view.
Can anyone shed any light on this ?
I need some urgent help here. Can someone please send me a example of this workflow ? I want to create one for one of my course but unable to do so due to lack in knowledge of coding.
I have gone through the full documentation and understand that there are some Commands for on step and completion step.
I tried the test xml mentioned above by Tim , but still unable to get hang of this one.
PLEASE HELP
Regards
Manish Kumar
Getting the above error while being logged as Manager
Unexpected end of input
Getting the above error while being logged as Admin
When I click on FINISH STEP
I have used Atto as well as Tiny to carry above steps but no change
Coding error detected, it must be fixed by a programmer: $course passed to moodle_page::set_course does not look like a proper course object.
More information about this error
I have installed Workflow Report as well on My Moodle which is 2.9 version
1) exmple workflow: It is not a great example, but look at the file tests/fixtures/testworkflow.workflow.xml inside the block folder. Try importing that.
2) Are you sure that you are using the latest version of this block? The latest version certainly works with Atto.
3) Where have you added the block? It should be added to a particular course. I have not seen this errors or our system.
Just a thought - this page would look nicer if you could add a screenshot or two.
a release for Moodle 3.2 is planned?
In current release (2016080200) "email" command in step scripts doesn't play. I obtain many error messages like "eventdata as \stdClass is deprecated. Please use core\message\message instead." or similar.
Thank you!
Roberto
Thank you Tim
Roberto
I would say that the system was not designed with that in mind.
On the other hand, the system is quite well designed. The block is just a view, and most of the view is generated by a renderer, that would be quite easy to reuse. So, it would be quite easy to re-use the back-end code, and some of the bits of view, in another development. You would just need to work it out.