<< Click to Display Table of Contents >> Organizer > Administration > Project, task and workflow > Activities |
Activities can be inserted in the Workflow of an existing task or in a task template.
Activity types are defined in the code list DSG - ACTIVITY_TYPE_CL. Here, the names of the activity types to be used in the different workflows, are defined. The activity types are only placeholders. The same activity type can be re-used in different workflows. For example, it is possible to use an activity type Field work in workflows for both service tasks as well as tasks for building new networks. In some cases, it is however desirable to have a more specific naming, to be able to distinguish different types of fieldwork (in the above example), when listing the activities in reports or when working with them in WorkPlanner.
The code list for activity types is shared across all applications that uses Organizer. In a multi-application environment, an administrator can decide for which applications an activity type should be available, see section Decide which applications an item type should be available in.
For information on codelists, see section Codelists and its subsections. |
The checklist is part of the information that can (but does not have to) be linked to an activity.
The checklist for a particular activity can be configured directly in the task or in a task template. The different types of checklist points you can choose to build a checklist are defined in the code list DSG - CHECKLIST_CL.
The code list for checklist types is shared across all applications that uses Organizer. In a multi-application environment, an administrator can decide for which applications a checklist type should be available, see section Decide which applications an item type should be available in.
When working with large checklists with many checkpoints, it can be useful to structure the checklists into categories and groups per category. The checkpoints are presented in a tree structure that you can easily navigate. It also gives an overview of what has been done and what remains.
Categories and groups are also defined in the code list DSG - CHECKLIST_CL.
Here, four checklist items have been divided into two different categories: Work request and Measurement work. For the Work request category, the items have also been divided into the two different groups New network and Rebuilt network. The result in the Activity User Interface is displayed. The dots are now divided into a tree structure where you can show and hide rows as needed.
A general possibility in codelists is to link documents to the various codes. This is also very useful for the checklist items and makes it possible to store, for example, instructions or templates for use in specific parts of a task. The configuration is done in the codelist by adding documents to the various checklist items.
When a user is to tick off the checklist item, this document can be used as support and provide a more detailed instruction for what to report or as a report template. To open a checklist document from the user interface, right-click on the checklist item in the Item column and select Show codelist document. The Codelist documents dialog box opens and displays the available documents. By selecting the document and pressing the Show button, the document is displayed in the application of the document type. The document can be read and saved to disk for reuse.
The document cannot be changed and updated as a codelist document in this way. It can only be saved to disk for reuse. To change a codelist document, you open the codelist manager and delete the existing document and store the new one, as described above. |