Workflow Management | Top Previous Next

This module allows setting up various workflow events as well as measures of its enforcement: notifications and escalations. Let’s start with the Allowed Status Transitions. QueWeb Open Source Edition allows maintaining dynamic transitions only for KB Solutions, even though you will see Tickets objects here as well. The system will ignore all records created for Tickets inside the Workflow. Please set the Object to Solutions when creating new Allowed Transitions records. Below you can select the From and To Statuses as well as indicate which Workgroups are allowed to make such Transitions. For example, you can create the following Workgroups in order to manage Solutions publishing process for the Knowledge Base: Solution Authors, Reviewers, and Publishers. For each of these Workgroups, you can allow certain Status Changes; i.e. For Solution Authors you can allow only putting Solution in the Draft Status. So you would create a new record and while leaving the From Status Blank, you would fill in Draft as the To Status and fill in the Solution Authors Workgroup as allowed Workgroup for this transition. Similarly, you would enable Solution Reviewers to move Solutions from Draft to Reviewed Status only. Using the QTask module, you can create a Task to move Expired Solutions into Retired Status, and correspondingly allow no Workgroups to do so manually. Furthermore, only Solution Authors can Move the Solution from Retired into Draft mode again. If you need to allow multiple Workgroups to be able to change the same Statuses – you create one such record and then while it is filled in the Form, click New and change the Allowed Workgroup, click Save. This works in any Form in QueWeb, where you can use existing record as a template for new record. Note though, that in some Forms certain fields will be reset when using this method as appropriate.