]po[ Workflow Tables

The following tables are part of the Petri-Net Workflow used in ]po[ to control the live-cycle of many business objects. Please see the package documentation for more information on the tables.

 


Table

Cols

Rows

Description

[wf_arcs]

7

90

The arcs of the workflow petri net. Arcs always go between a transition and a place. The direction is relative to the transition here, i.e. in means it goes into the transition, out means it goes away from the transition.

[wf_attribute_value_audit]

4

17

This table holds all the attribute values that has been set, so we can track changes over the lifetime of a case.

[wf_case_assignments]

4

2

Manual per-case assignments of roles to parties.

[wf_case_deadlines]

4

0

Manual deadlines for the individual transitions (tasks) on a per-case basis.

[wf_cases]

5

31

The instance of a process, e.g. the case of publishing one article, the case of handling one insurance claim, the case of handling one ecommerce order, of fixing one ticket-tracker ticket.

[wf_context_assignments]

4

3

Static (default) per-context assignments of roles to parties.

[wf_context_role_info]

5

0

This table holds context-dependent info for roles, currently only the assignment callback

[wf_context_task_panels]

9

15

Holds information about the panels to be displayed on the task page.

[wf_context_transition_info]

21

40

This table holds information that pertains to a transition in a specific context. It will specifically hold

[wf_context_workflow_info]

3

0

Holds context-dependent information about the workflow, specifically the
principal user.

[wf_contexts]

2

1

The context of a workflow holds everything that's not directly part of the Petri Net structure, the stuff that's likely to be changed as the workflow is applied in a real business, and that you will want to customize across different departments of the same business. It includes assignments of transitions to parties, the call-backs, etc.

[wf_places]

4

48

The circles of the petri net. These hold the tokens representing the overall state of the workflow.

[wf_roles]

4

39

A process has certain roles associated with it, such as "submitter","reviewer", "editor", "claimant", etc. For each transition, then, you specify what role is to perform that task. Thus, two or more tasks can be performed by one and the same role, so that when the role is reassigned, it reflects assignments of both tasks. Users and parties are then assigned to roles instead of directly to tasks.

[wf_task_assignments]

2

73

 

[wf_tasks]

15

85

The tasks that need to be done, who can do it, and what state it's in. A task is the instance of a transition.

[wf_tokens]

14

99

Where the tokens currently are, and what task is laying hands on it, if any. A token is sort of the instance of a place, except there'll be one row here per token, and there can be more than one token per place.

[wf_transition_attribute_map]

4

10

The workflow attributes that should be set when the given transition is fired.

[wf_transition_role_assign_map]

3

0

When part of the output of one task is to assign users to a role, specify that this is the case by inserting a row here.

[wf_transitions]

6

40

The squares in the petri net. The things that somebody (or something) actually does.

[wf_workflows]

3

8

Parent table for the workflow definition.

  Contact Us
  Project Open Business Solutions S.L.

Calle Aprestadora 19, 12o-2a

E-08907 Hospitalet de Llobregat (Barcelona)

 Tel Europe: +34 932 202 088
 Tel US: +1 415 429 5995
 Mail: info@project-open.com