content XXL WorkflowTasks content XXL WorkflowTasks 1 Overview

  • Slides: 19
Download presentation
content. XXL – Workflow/Tasks

content. XXL – Workflow/Tasks

content. XXL Workflow/Tasks 1. Overview 2. Workflow 3. Tasks 4. How to create a

content. XXL Workflow/Tasks 1. Overview 2. Workflow 3. Tasks 4. How to create a customized workflow

1. Overview § Workflow handles publishing and approval of objects § Tasks are job

1. Overview § Workflow handles publishing and approval of objects § Tasks are job oriented, flexible workflows which may be assigned to objects or without an object context § Workflow may be assigned to an user or a role. § Tasks may be assigned to one or more users or roles. If it is assigned to several users, every user must finish this task. If it is assigned to a role, any member of this role can accept the task. The task then is invisible for the other rolemembers.

2. Workflow there are 3 types of workflows § trivial no action § trivial

2. Workflow there are 3 types of workflows § trivial no action § trivial with notify notification, no approval required § basic notification, approval required i

2. Workflow Concept: § workflow is modelled as a state machine § it consists

2. Workflow Concept: § workflow is modelled as a state machine § it consists of states and state transitions Transition: start State: Waiting for approval Transition: reject State: Rejected Transition: approve State: Approved

2. Workflow here the state machines (workflow types) are defined currently 3 workflow types

2. Workflow here the state machines (workflow types) are defined currently 3 workflow types are implemented: § trivial (= default) § trivial with notify § basic Assembly. Name: possibility to implement custom workflows

2. Workflow defines workflow state types: 3 states are currently available § start §

2. Workflow defines workflow state types: 3 states are currently available § start § in progress § finished basic: § is in workflow (type 'start') § accepted (type 'finished') § rejected (type 'finished') for workflows 'trivial' and 'trivial with notify' only the state accepted is possible

2. Workflow defines possible transitions for a workflow between states (fields State. From and

2. Workflow defines possible transitions for a workflow between states (fields State. From and State. To from table Work. Flow. State) basic: § start (State. From: 0) § accepted § rejected trivial and trivial with notify: § accepted (State. From: 0) Class. Name: Content. XXL. Work. Flow. Basic. Primitive. Transition (basic and trivial) Content. XXL. Work. Flow. Basic. Primitive. Transition. With. Mail. Notification

2. Workflow not used

2. Workflow not used

2. Workflow binds workflow to object (Object. Version. Control. ID) if versioning is disabled

2. Workflow binds workflow to object (Object. Version. Control. ID) if versioning is disabled the workflow is connected with version 0 Version: Latest. Version from table Object. Version. Conrol Work. Flow. State. ID: ID from table Work. Flow. State Initiator. User. ID: user which requests this workflow Action: save, checkin, publish Target. Global. ID: if action is 'publish', the Publish. Info. Request. ID from table Publish. Info. Request (publishing information) is stored here

2. Workflow saves workflow history, not reflected in user interface not used

2. Workflow saves workflow history, not reflected in user interface not used

2. Workflow binds workflow type (Work. Flow. Definition. ID) to object and responsible persons

2. Workflow binds workflow type (Work. Flow. Definition. ID) to object and responsible persons Global. ID: defines scope for this workflow (module or portal) Responsible. Person: globalid from table roles or users Language. ID: workflows can be defined language dependant Action: not used

2. Workflow Namespace Content. XXL. Work. Flow. Basic

2. Workflow Namespace Content. XXL. Work. Flow. Basic

3. Tasks there are standard tasks and workflowtasks have a workflowinstanceid > 0 responsiblecache:

3. Tasks there are standard tasks and workflowtasks have a workflowinstanceid > 0 responsiblecache: users or roles to which the task is assigned to as comma separated string if more than one user or role (redundant information from Publish. Info table for fast access) relatedobject: globalid of object when the task was created in an object context 'None' if it is a general task Empty string in case of a workflow task status: current state of the task

3. Tasks assignment of tasks to users or roles are made in the Publish.

3. Tasks assignment of tasks to users or roles are made in the Publish. Info table: Global. Item. ID: task globalid Global. Target. ID: user or role globalid if a task is assigned to a role and one member of this role accepts the task, it will be reassigned to this member

3. Tasks

3. Tasks

3. Tasks represented by the field 'status' in the Tasks table

3. Tasks represented by the field 'status' in the Tasks table

4. How to create a customized workflow database: create a new entry in table

4. How to create a customized workflow database: create a new entry in table Work. Flow. Definition (Assembly. Name is the name of your assembly) create a corresponding new entry in table Work. Flow. State create a corresponding new entry in table Work. Flow. Transition (Class. Name is your class which implements the interface IWork. Flow. Transition)

content. XXL Thank you!

content. XXL Thank you!